<?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"
	>
<channel>
	<title>Comments on: A blog post developed using Agile Methodology</title>
	<atom:link href="http://pellacor.com/2008/05/05/a-blog-post-developed-using-agile-methodology/feed/" rel="self" type="application/rss+xml" />
	<link>http://pellacor.com/2008/05/05/a-blog-post-developed-using-agile-methodology/</link>
	<description>Thoughts about things</description>
	<pubDate>Thu, 11 Mar 2010 11:16:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Sam</title>
		<link>http://pellacor.com/2008/05/05/a-blog-post-developed-using-agile-methodology/#comment-234</link>
		<dc:creator>Sam</dc:creator>
		<pubDate>Tue, 06 May 2008 21:12:37 +0000</pubDate>
		<guid isPermaLink="false">http://pellacor.com/2008/05/05/a-blog-post-developed-using-agile-methodology/#comment-234</guid>
		<description>Thanks Simon.  I am mindful of pushing this metaphor too far, hence the lack of detail and to be clear, here: users and readers are the same thing.  

One of the major themes of this exercise for me is to try to gain insight into the importance of process over product in an online world.  There have recently been big changes to the software development paradigm of permanent beta and &lt;a href="http://en.wikipedia.org/wiki/Software_as_a_Service" title="Wiki article on Software as a Service" rel="nofollow"&gt;SaaS&lt;/a&gt; – but writing is still haunted by legacy issues of printing and publishing in print.  The clear example of how writing it still stuck in the paper age is the fact that the WordPress engine powering pellacor still has a “publish” button. 

We need to free writing, stories and content in general up from a “publishing” mentality and I hope that exploring some of these ideas using and iterative approach to creative writing may help.  

It is a bit of fun anyway. 

I like your idea of having some kind of SEO voice on the team and they will be included in the next iteration, due tomorrow. 

Thanks again for your input Simon because the conversation is the crucial bit.</description>
		<content:encoded><![CDATA[<p>Thanks Simon.  I am mindful of pushing this metaphor too far, hence the lack of detail and to be clear, here: users and readers are the same thing.  </p>
<p>One of the major themes of this exercise for me is to try to gain insight into the importance of process over product in an online world.  There have recently been big changes to the software development paradigm of permanent beta and <a href="http://en.wikipedia.org/wiki/Software_as_a_Service" title="Wiki article on Software as a Service" rel="nofollow">SaaS</a> – but writing is still haunted by legacy issues of printing and publishing in print.  The clear example of how writing it still stuck in the paper age is the fact that the WordPress engine powering pellacor still has a “publish” button. </p>
<p>We need to free writing, stories and content in general up from a “publishing” mentality and I hope that exploring some of these ideas using and iterative approach to creative writing may help.  </p>
<p>It is a bit of fun anyway. </p>
<p>I like your idea of having some kind of SEO voice on the team and they will be included in the next iteration, due tomorrow. </p>
<p>Thanks again for your input Simon because the conversation is the crucial bit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Young</title>
		<link>http://pellacor.com/2008/05/05/a-blog-post-developed-using-agile-methodology/#comment-233</link>
		<dc:creator>Simon Young</dc:creator>
		<pubDate>Tue, 06 May 2008 08:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://pellacor.com/2008/05/05/a-blog-post-developed-using-agile-methodology/#comment-233</guid>
		<description>Have we successfully articulated what the final blog post will look like? Or is that too prescriptive? What about the user stories for the users of this blog post? The readers, the writers, the commenters and of course the non-human critters that index and aggregate the content...</description>
		<content:encoded><![CDATA[<p>Have we successfully articulated what the final blog post will look like? Or is that too prescriptive? What about the user stories for the users of this blog post? The readers, the writers, the commenters and of course the non-human critters that index and aggregate the content&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
