<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>

<channel>
	<title>Agile Cases &#187; &#187; Wiki</title>
	<atom:link href="http://www.agilecases.com/tag/wiki/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agilecases.com</link>
	<description>a web of sketches, resources and comments</description>
	<pubDate>Wed, 13 Aug 2008 02:13:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
	<language>en</language>
			<item>
		<title>Ontic Oren » SW Development tools - Wiki &#038; Bugs</title>
		<link>http://www.agilecases.com/2008/03/25/ontic-oren-%c2%bb-sw-development-tools-wiki-bugs/</link>
		<comments>http://www.agilecases.com/2008/03/25/ontic-oren-%c2%bb-sw-development-tools-wiki-bugs/#comments</comments>
		<pubDate>Tue, 25 Mar 2008 10:46:08 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
		
		<category><![CDATA[Agent]]></category>

		<category><![CDATA[Lesson]]></category>

		<category><![CDATA[Wiki]]></category>

		<guid isPermaLink="false">http://www.agilecases.com/2008/03/25/ontic-oren-%c2%bb-sw-development-tools-wiki-bugs/</guid>
		<description><![CDATA[Oren Teich did look into requirements management tools and realized that the MOST critical success factor has always been alignment. If engineering, product management, sales and the customer aren’t all aligned on what, when, how, and why, we create massive headaches for ourselves.
I second his conclusion and would like to add that the choices he [...]]]></description>
			<content:encoded><![CDATA[<p>Oren Teich did <a href="http://onticoren.com/2008/03/22/sw-development-tools-wiki-bugs/">look into requirements management tools</a> and realized that the MOST critical success factor has always been alignment. If engineering, product management, sales and the customer aren’t all aligned on what, when, how, and why, we create massive headaches for ourselves.</p>
<p>I second his conclusion and would like to add that the choices he made for small or middle-sized companies are also valid for most projects inside bigger companies.</p>]]></content:encoded>
			<wfw:commentRss>http://www.agilecases.com/2008/03/25/ontic-oren-%c2%bb-sw-development-tools-wiki-bugs/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Deki CMS - Agile Content Management with Deki Wiki</title>
		<link>http://www.agilecases.com/2008/03/18/deki-cms-agile-content-management-with-deki-wiki/</link>
		<comments>http://www.agilecases.com/2008/03/18/deki-cms-agile-content-management-with-deki-wiki/#comments</comments>
		<pubDate>Tue, 18 Mar 2008 09:38:58 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
		
		<category><![CDATA[Event]]></category>

		<category><![CDATA[Lesson]]></category>

		<category><![CDATA[Communities]]></category>

		<category><![CDATA[Wiki]]></category>

		<guid isPermaLink="false">http://www.agilecases.com/2008/03/18/deki-cms-agile-content-management-with-deki-wiki/</guid>
		<description><![CDATA[Deki CMS - Agile Content Management with Deki Wiki &#124; MindTouch Blog:
 Deki CMS has 100% of the functionality of Deki Wiki, but it’s only accessible to authorized users, contributors and administrators. Any public or non-authorized user can only see the content, but not edit it.]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.mindtouch.com/blog/2008/03/17/deki-cms-agile-content-management-with-deki-wiki/">Deki CMS - Agile Content Management with Deki Wiki | MindTouch Blog:</a></p>
<blockquote><p> Deki CMS has 100% of the functionality of Deki <a href="http://www.agilecases.com/tag/wiki/" class="st_tag internal_tag" rel="tag" title="Posts tagged with Wiki">Wiki</a>, but it’s only accessible to authorized users, contributors and administrators. Any public or non-authorized user can only see the content, but not edit it.</p></blockquote>]]></content:encoded>
			<wfw:commentRss>http://www.agilecases.com/2008/03/18/deki-cms-agile-content-management-with-deki-wiki/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The long-requested page ordering feature &#8230;</title>
		<link>http://www.agilecases.com/2008/03/11/the-long-requested-page-ordering-feature/</link>
		<comments>http://www.agilecases.com/2008/03/11/the-long-requested-page-ordering-feature/#comments</comments>
		<pubDate>Tue, 11 Mar 2008 07:35:48 +0000</pubDate>
		<dc:creator>Peter</dc:creator>
		
		<category><![CDATA[Evidence]]></category>

		<category><![CDATA[Confluence]]></category>

		<category><![CDATA[Wiki]]></category>

		<guid isPermaLink="false">http://www.agilecases.com/2008/03/11/the-long-requested-page-ordering-feature/</guid>
		<description><![CDATA[The long-requested page ordering feature for Confluence will be implemented in release 2.8 (now in development) according to Atlassian.]]></description>
			<content:encoded><![CDATA[<p>The <a href="http://jira.atlassian.com/browse/CONF-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" title="Page ordering feature request">long-requested page ordering feature for Confluence</a> will be implemented in <a href="http://www.atlassian.com/software/confluence/DevReleaseDownloads.jspa" title="Confluence Development Releases">release 2.8 (now in development)</a> according to <a href="http://www.atlassian.com/software/confluence/" title="Atlassian Confluence">Atlassian</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.agilecases.com/2008/03/11/the-long-requested-page-ordering-feature/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
