<?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: Making the Product Backlog DEEP</title>
	<atom:link href="http://www.romanpichler.com/blog/product-backlog/making-the-product-backlog-deep/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.romanpichler.com/blog/product-backlog/making-the-product-backlog-deep/</link>
	<description>Roman Pichler&#039;s Thoughts on Agile Product Management</description>
	<lastBuildDate>Tue, 31 Jan 2012 22:03:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Making the Product Backlog DEEP &#171; The IT Blog</title>
		<link>http://www.romanpichler.com/blog/product-backlog/making-the-product-backlog-deep/#comment-2230</link>
		<dc:creator>Making the Product Backlog DEEP &#171; The IT Blog</dc:creator>
		<pubDate>Tue, 24 Jan 2012 00:28:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/blog/?p=89#comment-2230</guid>
		<description>[...] Roman Pichler Rate this:  Like this:LikeBe the first to like this post.  Posted by PE in Agile, Requirements, [...]</description>
		<content:encoded><![CDATA[<p>[...] Roman Pichler Rate this:  Like this:LikeBe the first to like this post.  Posted by PE in Agile, Requirements, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: agile42 &#124; Tips and Tricks for the beginner Product Owner</title>
		<link>http://www.romanpichler.com/blog/product-backlog/making-the-product-backlog-deep/#comment-2142</link>
		<dc:creator>agile42 &#124; Tips and Tricks for the beginner Product Owner</dc:creator>
		<pubDate>Wed, 16 Nov 2011 08:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/blog/?p=89#comment-2142</guid>
		<description>[...] little pieces. It does mean to keep the Product Backlog &#8222;detailed appropriately&#8220; (see DEEP acronym). So keep your top requirements sliced into small pieces and wait with slicing the rest until it is [...]</description>
		<content:encoded><![CDATA[<p>[...] little pieces. It does mean to keep the Product Backlog &bdquo;detailed appropriately&ldquo; (see DEEP acronym). So keep your top requirements sliced into small pieces and wait with slicing the rest until it is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Product Owner and the start of a Backlog &#171; Inevitably Agile</title>
		<link>http://www.romanpichler.com/blog/product-backlog/making-the-product-backlog-deep/#comment-2026</link>
		<dc:creator>The Product Owner and the start of a Backlog &#171; Inevitably Agile</dc:creator>
		<pubDate>Wed, 20 Jul 2011 06:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/blog/?p=89#comment-2026</guid>
		<description>[...] backlog should be D.E.E.P (some more info on [...]</description>
		<content:encoded><![CDATA[<p>[...] backlog should be D.E.E.P (some more info on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Product Management in an Agile style &#171; The Cognidox Blog</title>
		<link>http://www.romanpichler.com/blog/product-backlog/making-the-product-backlog-deep/#comment-1963</link>
		<dc:creator>Product Management in an Agile style &#171; The Cognidox Blog</dc:creator>
		<pubDate>Mon, 02 May 2011 14:17:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/blog/?p=89#comment-1963</guid>
		<description>[...] Roman re-iterated an idea (from Mike Cohn) that the product backlog would ideally be DEEP: It should be detailed appropriately, estimated, emergent, and prioritized. More on that from his blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] Roman re-iterated an idea (from Mike Cohn) that the product backlog would ideally be DEEP: It should be detailed appropriately, estimated, emergent, and prioritized. More on that from his blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alternde Product Backlog Items – Vermeiden Sie Karteileichen &#62; Agile, Product Backlog, Scrum &#62; Startup, Start-Up, Internetunternehmen, Webunternehmen, Gründer, Website, Webplattform, Webshop, E-Commerce, Internetindustrie, Venturecapital</title>
		<link>http://www.romanpichler.com/blog/product-backlog/making-the-product-backlog-deep/#comment-1957</link>
		<dc:creator>Alternde Product Backlog Items – Vermeiden Sie Karteileichen &#62; Agile, Product Backlog, Scrum &#62; Startup, Start-Up, Internetunternehmen, Webunternehmen, Gründer, Website, Webplattform, Webshop, E-Commerce, Internetindustrie, Venturecapital</dc:creator>
		<pubDate>Tue, 12 Apr 2011 18:09:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.romanpichler.com/blog/?p=89#comment-1957</guid>
		<description>[...] allgemein zur aktuellen (Projekt-) Situation getätigt werden. Roman Pichler spricht vom &#8220;DEEP Backlog&#8221; und wie viele andere Scrum-Experten rät auch er zum regelmäßigen &#8220;grooming&#8221; [...]</description>
		<content:encoded><![CDATA[<p>[...] allgemein zur aktuellen (Projekt-) Situation getätigt werden. Roman Pichler spricht vom &#8220;DEEP Backlog&#8221; und wie viele andere Scrum-Experten rät auch er zum regelmäßigen &#8220;grooming&#8221; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

