<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Definition of Ready</title>
	<atom:link href="http://www.romanpichler.com/blog/product-backlog/the-definition-of-ready/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.romanpichler.com/blog/product-backlog/the-definition-of-ready/</link>
	<description>Roman Pichler&#039;s Thoughts on Agile Product Management</description>
	<lastBuildDate>Sat, 18 May 2013 12:20:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
	<item>
		<title>By: New User Stories Article on Agile Atlas &#124; The Scrum Crazy Blog</title>
		<link>http://www.romanpichler.com/blog/product-backlog/the-definition-of-ready/#comment-8564</link>
		<dc:creator>New User Stories Article on Agile Atlas &#124; The Scrum Crazy Blog</dc:creator>
		<pubDate>Wed, 27 Mar 2013 16:01:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/?p=1172#comment-8564</guid>
		<description>[...] To see how to make sure your stories are &#8220;ready&#8221; for implementation, check out Roman Pichler&#8217;s article, The Definition of Ready [...]</description>
		<content:encoded><![CDATA[<p>[...] To see how to make sure your stories are &#8220;ready&#8221; for implementation, check out Roman Pichler&#8217;s article, The Definition of Ready [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dzień 6 Backlog Produktu — Fluid Circle</title>
		<link>http://www.romanpichler.com/blog/product-backlog/the-definition-of-ready/#comment-5153</link>
		<dc:creator>Dzień 6 Backlog Produktu — Fluid Circle</dc:creator>
		<pubDate>Tue, 15 Jan 2013 15:56:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/?p=1172#comment-5153</guid>
		<description>[...] to znaczy gotowe? Dobrze opisuje ten problem Roman Pichler w artykule “The Definition of READY”. Według Romana najważniejsze jest by GOTOWE elementy backlogu [...]</description>
		<content:encoded><![CDATA[<p>[...] to znaczy gotowe? Dobrze opisuje ten problem Roman Pichler w artykule “The Definition of READY”. Według Romana najważniejsze jest by GOTOWE elementy backlogu [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Epics and Ready Stories</title>
		<link>http://www.romanpichler.com/blog/product-backlog/the-definition-of-ready/#comment-3797</link>
		<dc:creator>Epics and Ready Stories</dc:creator>
		<pubDate>Wed, 07 Nov 2012 13:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/?p=1172#comment-3797</guid>
		<description>[...] These stories have to be clear, feasible, and testable [...]</description>
		<content:encoded><![CDATA[<p>[...] These stories have to be clear, feasible, and testable [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Product Canvas for Agile Product Management</title>
		<link>http://www.romanpichler.com/blog/product-backlog/the-definition-of-ready/#comment-2582</link>
		<dc:creator>A Product Canvas for Agile Product Management</dc:creator>
		<pubDate>Sun, 22 Jul 2012 11:14:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/?p=1172#comment-2582</guid>
		<description>[...] The ready stories have to be clear, feasible, and testable so that the development team can transform them into a product increment or minimal viable product (MVP). [...]</description>
		<content:encoded><![CDATA[<p>[...] The ready stories have to be clear, feasible, and testable so that the development team can transform them into a product increment or minimal viable product (MVP). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Handling Non Functional Requirements in User Stories and Scrum &#171; The Scrum Crazy Blog</title>
		<link>http://www.romanpichler.com/blog/product-backlog/the-definition-of-ready/#comment-2526</link>
		<dc:creator>Handling Non Functional Requirements in User Stories and Scrum &#171; The Scrum Crazy Blog</dc:creator>
		<pubDate>Thu, 28 Jun 2012 16:06:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/?p=1172#comment-2526</guid>
		<description>[...] To see how to make sure your stories are &#8220;ready&#8221; for implementation, check out Roman Pichler&#8217;s article, The Definition of Ready [...]</description>
		<content:encoded><![CDATA[<p>[...] To see how to make sure your stories are &#8220;ready&#8221; for implementation, check out Roman Pichler&#8217;s article, The Definition of Ready [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
