<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Requirements docs: Goodbye word processor, hello wiki</title>
	<atom:link href="http://productvision.org/blog/bye-wp/feed/" rel="self" type="application/rss+xml" />
	<link>http://productvision.org/blog/bye-wp/</link>
	<description>Articles about Product Vision and Strategy by D. Philip Haine</description>
	<lastBuildDate>Mon, 05 Apr 2010 20:04:04 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: admin</title>
		<link>http://productvision.org/blog/bye-wp/comment-page-1/#comment-4845</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 13 Aug 2009 17:07:05 +0000</pubDate>
		<guid isPermaLink="false">http://productvision.org/blog/?p=394#comment-4845</guid>
		<description>Thanks, Ken,

Those are great points.

I wonder whether/how Google Wave is going to deal with  problem #1.

Phil</description>
		<content:encoded><![CDATA[<p>Thanks, Ken,</p>
<p>Those are great points.</p>
<p>I wonder whether/how Google Wave is going to deal with  problem #1.</p>
<p>Phil</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Krugler</title>
		<link>http://productvision.org/blog/bye-wp/comment-page-1/#comment-4844</link>
		<dc:creator>Ken Krugler</dc:creator>
		<pubDate>Thu, 13 Aug 2009 16:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://productvision.org/blog/?p=394#comment-4844</guid>
		<description>Hi Philip,

I&#039;ve used Confluence for a few years, and like it. The integration with Jira (issue tracking) makes it easier to move from a spec to specific actions.

Two problems I&#039;ve run into with wiki-based specs:

1. Discussions get awkward. With a spec doc, people send you their input and you merge it in (or not). But on the wiki you wind up with huge, threaded discussions that eventually need to get deleted (can raise hackles), or they&#039;ll continue to persist and thus distract/confuse readers when the issues they raise have been addressed.

2. Old specs never die. It&#039;s hard to know when a page is active, or done, or so far out of date it&#039;s useless. People stumble across fusty specs and assume they&#039;re gospel. It takes a lot of discipline to properly archive/flag older stuff.

-- Ken</description>
		<content:encoded><![CDATA[<p>Hi Philip,</p>
<p>I&#8217;ve used Confluence for a few years, and like it. The integration with Jira (issue tracking) makes it easier to move from a spec to specific actions.</p>
<p>Two problems I&#8217;ve run into with wiki-based specs:</p>
<p>1. Discussions get awkward. With a spec doc, people send you their input and you merge it in (or not). But on the wiki you wind up with huge, threaded discussions that eventually need to get deleted (can raise hackles), or they&#8217;ll continue to persist and thus distract/confuse readers when the issues they raise have been addressed.</p>
<p>2. Old specs never die. It&#8217;s hard to know when a page is active, or done, or so far out of date it&#8217;s useless. People stumble across fusty specs and assume they&#8217;re gospel. It takes a lot of discipline to properly archive/flag older stuff.</p>
<p>&#8211; Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://productvision.org/blog/bye-wp/comment-page-1/#comment-4602</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 29 Jul 2009 17:54:16 +0000</pubDate>
		<guid isPermaLink="false">http://productvision.org/blog/?p=394#comment-4602</guid>
		<description>Tab, I&#039;m glad to hear it was useful.

And thanks for the pointers to alternate wikis!

- Philip</description>
		<content:encoded><![CDATA[<p>Tab, I&#8217;m glad to hear it was useful.</p>
<p>And thanks for the pointers to alternate wikis!</p>
<p>- Philip</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tab Hockamier</title>
		<link>http://productvision.org/blog/bye-wp/comment-page-1/#comment-4598</link>
		<dc:creator>Tab Hockamier</dc:creator>
		<pubDate>Wed, 29 Jul 2009 15:40:14 +0000</pubDate>
		<guid isPermaLink="false">http://productvision.org/blog/?p=394#comment-4598</guid>
		<description>I have recently installed MediaWiki on a local site and it works very well.  I have also found MoinMoin to be an excellent choice as I have used that for years.  DokuWiki is very nice as well.

Thanks for the article - it has help me to push the MediaWiki solution in-house to gain acceptance.</description>
		<content:encoded><![CDATA[<p>I have recently installed MediaWiki on a local site and it works very well.  I have also found MoinMoin to be an excellent choice as I have used that for years.  DokuWiki is very nice as well.</p>
<p>Thanks for the article &#8211; it has help me to push the MediaWiki solution in-house to gain acceptance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Benji York</title>
		<link>http://productvision.org/blog/bye-wp/comment-page-1/#comment-3640</link>
		<dc:creator>Benji York</dc:creator>
		<pubDate>Tue, 23 Jun 2009 14:01:36 +0000</pubDate>
		<guid isPermaLink="false">http://productvision.org/blog/?p=394#comment-3640</guid>
		<description>MoinMoin is a pretty good choice.  It includes a WYSIWYG editor for non-technical types and reStructured Text (http://docutils.sourceforge.net/rst.html) support for those that need a bit more sophistication.</description>
		<content:encoded><![CDATA[<p>MoinMoin is a pretty good choice.  It includes a WYSIWYG editor for non-technical types and reStructured Text (<a href="http://docutils.sourceforge.net/rst.html" rel="nofollow">http://docutils.sourceforge.net/rst.html</a>) support for those that need a bit more sophistication.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
