<?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; !</title>
	<atom:link href="http://agile101.net/category/featured/feed/" rel="self" type="application/rss+xml" />
	<link>http://agile101.net</link>
	<description>Agile Project Management, Programme Management and Digital Publishing</description>
	<lastBuildDate>Thu, 11 Feb 2010 21:43:54 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>The Difference Between Waterfall, Iterative Waterfall, Scrum and Lean Software Development (In Pictures!)</title>
		<link>http://agile101.net/2009/09/08/the-difference-between-waterfall-iterative-waterfall-scrum-and-lean-in-pictures/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=the-difference-between-waterfall-iterative-waterfall-scrum-and-lean-in-pictures</link>
		<comments>http://agile101.net/2009/09/08/the-difference-between-waterfall-iterative-waterfall-scrum-and-lean-in-pictures/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 10:57:28 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Agile Software Development]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Software Project Management]]></category>
		<category><![CDATA[Waterfall Development]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=1660</guid>
		<description><![CDATA[Here's a VERY simple overview of the main differences between Waterfall Development, Iterative Waterfall Development, Scrum/Agile Development and Lean.]]></description>
		<wfw:commentRss>http://agile101.net/2009/09/08/the-difference-between-waterfall-iterative-waterfall-scrum-and-lean-in-pictures/feed/</wfw:commentRss>
		<slash:comments>28</slash:comments>
		</item>
		<item>
		<title>What does &#8216;Done&#8217; mean in Agile Software Development?</title>
		<link>http://agile101.net/2009/09/04/what-does-done-mean-in-agile-software-development/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=what-does-done-mean-in-agile-software-development</link>
		<comments>http://agile101.net/2009/09/04/what-does-done-mean-in-agile-software-development/#comments</comments>
		<pubDate>Fri, 04 Sep 2009 09:36:58 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=1493</guid>
		<description><![CDATA[In Agile Software Development environments, we aim to deliver '[potentially] shippable code' at the end of each iteration.]]></description>
		<wfw:commentRss>http://agile101.net/2009/09/04/what-does-done-mean-in-agile-software-development/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<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/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=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>taraleewhitaker</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>11</slash:comments>
		</item>
		<item>
		<title>The Product Manager &#8211; Role and Responsibilities</title>
		<link>http://agile101.net/2009/08/07/the-product-manager-role-responsibilities/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=the-product-manager-role-responsibilities</link>
		<comments>http://agile101.net/2009/08/07/the-product-manager-role-responsibilities/#comments</comments>
		<pubDate>Fri, 07 Aug 2009 17:21:37 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Scrum Roles]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=788</guid>
		<description><![CDATA[The Product Manager represents the Product Owner and the End-User/Customer - they are responsible for defining and scheduling the delivery of high quality output in line with business requirements and priorities.]]></description>
		<wfw:commentRss>http://agile101.net/2009/08/07/the-product-manager-role-responsibilities/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>How Agile Are You? (The Survey!)</title>
		<link>http://agile101.net/2009/08/01/how-agile-are-you/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=how-agile-are-you</link>
		<comments>http://agile101.net/2009/08/01/how-agile-are-you/#comments</comments>
		<pubDate>Sat, 01 Aug 2009 00:18:32 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Templates]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Retrospective]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=543</guid>
		<description><![CDATA[How Agile Are You? A question originally posed by Nokia, shortly followed by Kelly Waters of All About Agile. This post contains a downloadable template you can use to measure yourself against a list of 42 criteria. See how you measure up!]]></description>
		<wfw:commentRss>http://agile101.net/2009/08/01/how-agile-are-you/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Agile Risk Management for Projects and Programmes</title>
		<link>http://agile101.net/2009/07/27/agile-risk-management-for-projects-and-programmes/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=agile-risk-management-for-projects-and-programmes</link>
		<comments>http://agile101.net/2009/07/27/agile-risk-management-for-projects-and-programmes/#comments</comments>
		<pubDate>Mon, 27 Jul 2009 00:38:43 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Software Development]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=429</guid>
		<description><![CDATA[Risks are traditionally identified, assessed, responded to and monitored by a Project Manager. In Agile working environments the responsibility for risk management is shared by all involved. There don’t seem to be any official guidelines on how to manage risks within an Agile environment, so I’ll combine my personal views/learning with notes/ideas I’ve found scattered around the web.]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/27/agile-risk-management-for-projects-and-programmes/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Agile Risk Management &#8211; The difference between Risks and Issues</title>
		<link>http://agile101.net/2009/07/26/agile-risk-management-the-difference-between-risks-and-issues/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=agile-risk-management-the-difference-between-risks-and-issues</link>
		<comments>http://agile101.net/2009/07/26/agile-risk-management-the-difference-between-risks-and-issues/#comments</comments>
		<pubDate>Sun, 26 Jul 2009 21:58:10 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Project Planning]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=426</guid>
		<description><![CDATA[A Risk is an uncertain event that could impact your chosen path should it be realised. Risks are events that are not currently affecting you - they haven't happened yet.  Once a risk is realised, it has the potential to become an Issue.]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/26/agile-risk-management-the-difference-between-risks-and-issues/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Agile Issue Management for Projects and Programmes</title>
		<link>http://agile101.net/2009/07/26/agile-issue-management-for-projects-and-programmes/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=agile-issue-management-for-projects-and-programmes</link>
		<comments>http://agile101.net/2009/07/26/agile-issue-management-for-projects-and-programmes/#comments</comments>
		<pubDate>Sun, 26 Jul 2009 01:34:15 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Risks and Issues]]></category>
		<category><![CDATA[Agile Issue Management]]></category>
		<category><![CDATA[Agile Project Management]]></category>
		<category><![CDATA[Product Management]]></category>
		<category><![CDATA[Software Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=406</guid>
		<description><![CDATA[Scrum is great at handling immediate issues or in this case, they're more commonly referred to as 'Impediments'... ]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/26/agile-issue-management-for-projects-and-programmes/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>The Epic Board &#8211; An Essential Agile Project Management Tool</title>
		<link>http://agile101.net/2009/07/25/the-epic-board-an-essential-agile-project-management-tool/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=the-epic-board-an-essential-agile-project-management-tool</link>
		<comments>http://agile101.net/2009/07/25/the-epic-board-an-essential-agile-project-management-tool/#comments</comments>
		<pubDate>Sun, 26 Jul 2009 06:02:38 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Agile Epic Board]]></category>
		<category><![CDATA[Agile Programme Management]]></category>
		<category><![CDATA[Agile Project Management]]></category>

		<guid isPermaLink="false">http://agile101.net/?p=400</guid>
		<description><![CDATA[I introduced the Epic Board as a programme management tool - a tangible release plan that can help you to plan software development programmes comprising multiple separate projects combined with Business As Usual Activities.  ]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/25/the-epic-board-an-essential-agile-project-management-tool/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Lean, Scrum, Scrum of Scrums and Epic Boards!</title>
		<link>http://agile101.net/2009/07/08/when-to-use-scrum-lean-and-epic-boards/?utm_source=rss&amp;utm_medium=rss&amp;utm_campaign=when-to-use-scrum-lean-and-epic-boards</link>
		<comments>http://agile101.net/2009/07/08/when-to-use-scrum-lean-and-epic-boards/#comments</comments>
		<pubDate>Thu, 09 Jul 2009 02:56:50 +0000</pubDate>
		<dc:creator>taraleewhitaker</dc:creator>
				<category><![CDATA[!]]></category>
		<category><![CDATA[Agile Epic Board]]></category>
		<category><![CDATA[Programme Management]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Lean]]></category>
		<category><![CDATA[Scrum]]></category>

		<guid isPermaLink="false">http://agile101.wordpress.com/?p=46</guid>
		<description><![CDATA[So, when do you use Scrum practices, when should you consider Lean practices and when should you consider using Epic Boards?]]></description>
		<wfw:commentRss>http://agile101.net/2009/07/08/when-to-use-scrum-lean-and-epic-boards/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
