<?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>Agile101 - Agile Project Management and Digital Publishing &#187; Agile Estimation</title>
	<atom:link href="http://agile101.net/tag/agile-estimation/feed/" rel="self" type="application/rss+xml" />
	<link>http://agile101.net</link>
	<description>Agile Project Management, Programme Management and Digital Publishing</description>
	<lastBuildDate>Thu, 17 Nov 2011 05:58:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Sprint Planning: Hours or Story Points (?) &#8211; that is the question!</title>
		<link>http://agile101.net/2009/08/24/sprint-planning-hours-or-story-points-that-is-the-question/</link>
		<comments>http://agile101.net/2009/08/24/sprint-planning-hours-or-story-points-that-is-the-question/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 10:24:50 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Agile Estimation]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Software Project Management]]></category>
		<category><![CDATA[Sprint Planning]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=1286</guid>
		<description><![CDATA[There is a lot of debate about whether to estimate sprint requirements in hours or to leave them in Story Points. Personally, I see pros and cons of both approaches but would use Story Points over hours where/whenever possible.]]></description>
		<wfw:commentRss>http://agile101.net/2009/08/24/sprint-planning-hours-or-story-points-that-is-the-question/feed/</wfw:commentRss>
		<slash:comments>13</slash:comments>
		</item>
		<item>
		<title>Agile Estimation and the Cone of Uncertainty</title>
		<link>http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/</link>
		<comments>http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/#comments</comments>
		<pubDate>Tue, 18 Aug 2009 07:20:35 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Agile Estimation]]></category>
		<category><![CDATA[Themes, Stories, Epics]]></category>
		<category><![CDATA[Cone of Uncertainty]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Software Project Management]]></category>
		<category><![CDATA[Story points]]></category>
		<category><![CDATA[T-shirt Sizing]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=1070</guid>
		<description><![CDATA[The Cone of Uncertainty is a Project Management term used to describe the level of uncertainty existing at different stages of a project.

In short, we become more certain of our estimates as we learn more about what we’re estimating.
]]></description>
		<wfw:commentRss>http://agile101.net/2009/08/18/agile-estimation-and-the-cone-of-uncertainty/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Value Points &#8211; Estimating the relative value of a User Story</title>
		<link>http://agile101.net/2009/07/22/value-points-estimating-the-relative-value-of-a-user-story/</link>
		<comments>http://agile101.net/2009/07/22/value-points-estimating-the-relative-value-of-a-user-story/#comments</comments>
		<pubDate>Wed, 22 Jul 2009 01:22:09 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Agile Estimation]]></category>
		<category><![CDATA[Financial Planning]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Software Project Management]]></category>
		<category><![CDATA[Value Points]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=322</guid>
		<description><![CDATA[Value Points can be used to measure the relative value of stories using a Fibonnaci Sequence. Although not appropriate or particularly necessary in all cases e.g. primarily when you have an omni-present Product Manager, these can be a useful way to prioritise and convey relative importance to a team. This approach becomes increasingly useful as teams scale to cover multiple projects combined with Business As Usual activities.]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/22/value-points-estimating-the-relative-value-of-a-user-story/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Using Velocity to measure the Productivity of an Agile Development Team</title>
		<link>http://agile101.net/2009/07/18/using-velocity-to-measure-team-productivity-and-effectiveness/</link>
		<comments>http://agile101.net/2009/07/18/using-velocity-to-measure-team-productivity-and-effectiveness/#comments</comments>
		<pubDate>Sat, 18 Jul 2009 00:52:32 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Agile Estimation]]></category>
		<category><![CDATA[Performance & KPIs]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Software Project Management]]></category>
		<category><![CDATA[Velocity]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=255</guid>
		<description><![CDATA[Although you can not use Velocity to measure the productivity of one team compared to another, you can use velocity to help track the relative productivity of the same team from one sprint to another assuming the value of a point stays the same over time.]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/18/using-velocity-to-measure-team-productivity-and-effectiveness/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Software Estimation &#8211; the more precise you are, the less accurate you will be!</title>
		<link>http://agile101.net/2009/07/17/software-estimation-the-more-precise-you-are-the-less-accurate-you-will-be/</link>
		<comments>http://agile101.net/2009/07/17/software-estimation-the-more-precise-you-are-the-less-accurate-you-will-be/#comments</comments>
		<pubDate>Fri, 17 Jul 2009 01:12:53 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Agile Estimation]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Software Project Management]]></category>
		<category><![CDATA[Story points]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=226</guid>
		<description><![CDATA[We often confuse 'accurate' (mean difference) with 'precise (variance)'. It would be accurate to say that I was less than six foot tall, it would be precise to say that I was...]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/17/software-estimation-the-more-precise-you-are-the-less-accurate-you-will-be/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Velocity can be used to measure the output of any team&#8230;</title>
		<link>http://agile101.net/2009/07/10/velocity-can-be-used-to-measure-the-output-of-any-team/</link>
		<comments>http://agile101.net/2009/07/10/velocity-can-be-used-to-measure-the-output-of-any-team/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 17:15:50 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Agile Estimation]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.wordpress.com/?p=93</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://agile101.net/2009/07/10/velocity-can-be-used-to-measure-the-output-of-any-team/";</script>var dzone_style="2";Velocity is a measure of how much work a team can complete in a set period of time.  It is measured in Story Points and although it was originally created for use in Software Development scenarios, it can be used in just about every type of team scenario. Velocity can be measured assuming you have&#8230; : 1 [...]]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/10/velocity-can-be-used-to-measure-the-output-of-any-team/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What&#8217;s my team velocity?</title>
		<link>http://agile101.net/2009/07/10/whats-my-team-velocity/</link>
		<comments>http://agile101.net/2009/07/10/whats-my-team-velocity/#comments</comments>
		<pubDate>Fri, 10 Jul 2009 16:56:33 +0000</pubDate>
		<dc:creator>Tara L Hamilton-Whitaker</dc:creator>
				<category><![CDATA[Agile Estimation]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.wordpress.com/?p=87</guid>
		<description><![CDATA[I often get asked how an existing team would go about determining their Velocity (the average amount of work a team can complete in a set period of time), so I thought I'd write a post about how we've done it in the past...]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/10/whats-my-team-velocity/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

