<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Neil Crookes &#187; Methodologies</title>
	<atom:link href="http://www.neilcrookes.com/category/development/methodologies/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.neilcrookes.com</link>
	<description>Learnings and Teachings on Web Application Development &#38; CakePHP</description>
	<lastBuildDate>Tue, 22 Jun 2010 20:10:01 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Creating the product backlog</title>
		<link>http://www.neilcrookes.com/2008/11/28/creating-the-product-backlog/</link>
		<comments>http://www.neilcrookes.com/2008/11/28/creating-the-product-backlog/#comments</comments>
		<pubDate>Fri, 28 Nov 2008 11:44:27 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Estimating]]></category>
		<category><![CDATA[Stories]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=115</guid>
		<description><![CDATA[Previously I blogged about what <a href="http://www.neilcrookes.com/2008/11/17/whats-the-story/">user stories in scrum</a> should look like, providing an overview of their format and principles, but not really covering a how you come up with them all or how you decide what order to do them in.

This post covers who needs to be involved and recommends a practical 10 step approach for creating the Product Backlog.]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/11/28/creating-the-product-backlog/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Quick and accurate high-level estimates in Scrum</title>
		<link>http://www.neilcrookes.com/2008/11/25/quick-and-accurate-high-level-estimates-in-scrum/</link>
		<comments>http://www.neilcrookes.com/2008/11/25/quick-and-accurate-high-level-estimates-in-scrum/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 14:50:42 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Estimating]]></category>
		<category><![CDATA[Planning]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=111</guid>
		<description><![CDATA[So Agile is all about working software over comprehensive documentation right? But if I don't know the detailed requirements up front, how can I estimate for a task? And if I can't estimate for a task, how can we figure out how long the project will take and how much it will cost?

This post covers techniques for quickly and easily creating reasonably accurate, high-level estimates in the project kickoff meeting that are sufficient for resource planning and scheduling.]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/11/25/quick-and-accurate-high-level-estimates-in-scrum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What&#8217;s the Story?</title>
		<link>http://www.neilcrookes.com/2008/11/17/whats-the-story/</link>
		<comments>http://www.neilcrookes.com/2008/11/17/whats-the-story/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 11:30:52 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Stories]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=108</guid>
		<description><![CDATA[The who, what, when, where and why of user stories for Scrum.]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/11/17/whats-the-story/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Introduction to Scrum</title>
		<link>http://www.neilcrookes.com/2008/11/14/introduction-to-scrum/</link>
		<comments>http://www.neilcrookes.com/2008/11/14/introduction-to-scrum/#comments</comments>
		<pubDate>Fri, 14 Nov 2008 16:54:43 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Iterative]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Processes]]></category>
		<category><![CDATA[Software Development]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=106</guid>
		<description><![CDATA[An introduction to Scrum, one of the flavours of Agile, covering the team structure, processes and terminology in a brief handy overview.]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/11/14/introduction-to-scrum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Which flavour of Agile tastes best?</title>
		<link>http://www.neilcrookes.com/2008/10/18/which-flavour-of-agile-tastes-best/</link>
		<comments>http://www.neilcrookes.com/2008/10/18/which-flavour-of-agile-tastes-best/#comments</comments>
		<pubDate>Sat, 18 Oct 2008 22:09:41 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Software Development]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=63</guid>
		<description><![CDATA[Agile is an umbrella term for several software development methodologies that share a common philosophy defined in the Agile Manifesto, but have their own ideas on its implementation. This post takes a brief look at a few of those flavours.]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/10/18/which-flavour-of-agile-tastes-best/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Selling Agile to clients</title>
		<link>http://www.neilcrookes.com/2008/07/26/selling-agile-to-clients/</link>
		<comments>http://www.neilcrookes.com/2008/07/26/selling-agile-to-clients/#comments</comments>
		<pubDate>Sat, 26 Jul 2008 13:15:45 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Clients]]></category>
		<category><![CDATA[Selling]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=23</guid>
		<description><![CDATA[The world of software development has changed. The world of web development is catching up. Agile is the future, waterfall is past - but persuading clients can be tricky.

This post is all about how to persuade a client that Agile is not only right for them, its the only sensible choice, with a few facts and sample answers to their inevitable questions.]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/07/26/selling-agile-to-clients/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Introduction to Agile Practices</title>
		<link>http://www.neilcrookes.com/2008/07/09/introduction-to-agile-practices/</link>
		<comments>http://www.neilcrookes.com/2008/07/09/introduction-to-agile-practices/#comments</comments>
		<pubDate>Wed, 09 Jul 2008 20:16:32 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Iterative]]></category>
		<category><![CDATA[Methodology]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Processes]]></category>
		<category><![CDATA[Software Development]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=22</guid>
		<description><![CDATA[Heard a lot about this Agile melarkey? Wondered what it involves? This post explains the processes and practices in running a project using an Agile approach.

It covers the concepts of the approach, explains the processes involved. Describes the meetings (or ceremonies) you should have, what to discuss and what their outcomes should be. It also explains who should do what, and when.]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/07/09/introduction-to-agile-practices/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>When specs don&#8217;t work</title>
		<link>http://www.neilcrookes.com/2008/06/30/when-specs-dont-work/</link>
		<comments>http://www.neilcrookes.com/2008/06/30/when-specs-dont-work/#comments</comments>
		<pubDate>Mon, 30 Jun 2008 22:38:18 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Estimating]]></category>
		<category><![CDATA[Functionality]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Processes]]></category>
		<category><![CDATA[Specification]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=19</guid>
		<description><![CDATA[When estimating for a project that you're not sure you're going to be awarded, you don't want to spend too much time analysing the minutiae in the spec. So what do you do when you've won it, you're half way through building it, and you stumble across a small, but fundamental problem?]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/06/30/when-specs-dont-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tolerant Project Estimates</title>
		<link>http://www.neilcrookes.com/2008/05/20/tolerant-project-estimates/</link>
		<comments>http://www.neilcrookes.com/2008/05/20/tolerant-project-estimates/#comments</comments>
		<pubDate>Mon, 19 May 2008 23:39:41 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Estimating]]></category>
		<category><![CDATA[Planning]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=17</guid>
		<description><![CDATA[Software developers will always be asked to estimate for work, so that project costs, timescales and resource requirements can be planned. Much as you’d like to just get on and build a web application, this, unfortunately, is a fact of life.

If your estimates are wildly under actual times, there can be repercussions. If you work for yourself you'll most likely take a hit on the profit you'll make on a project. If you work for someone else, your boss might not be too happy as the company has taken that hit.

This post talks about how to estimate, types of estimate (with a section on ballparks) and how you can manage the use and interpretation of estimates you provide.]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/05/20/tolerant-project-estimates/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Functional Specs for Web Applications</title>
		<link>http://www.neilcrookes.com/2008/04/14/functional-specs-for-web-applications/</link>
		<comments>http://www.neilcrookes.com/2008/04/14/functional-specs-for-web-applications/#comments</comments>
		<pubDate>Sun, 13 Apr 2008 23:18:24 +0000</pubDate>
		<dc:creator>Neil Crookes</dc:creator>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Functionality]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[Processes]]></category>
		<category><![CDATA[Specification]]></category>

		<guid isPermaLink="false">http://www.neilcrookes.com/?p=4</guid>
		<description><![CDATA[Answers to questions such as "What is a functional spec?", "Why is it important?", "How do you write a functional spec?", "What does it contain?", "What does it not contain?"]]></description>
		<wfw:commentRss>http://www.neilcrookes.com/2008/04/14/functional-specs-for-web-applications/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
