<?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: Grooming the product backlog: agile requirements management for improved sprint planning</title>
	<atom:link href="http://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/</link>
	<description>Advance Your Business Analysis Career</description>
	<lastBuildDate>Thu, 09 Feb 2012 00:08:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Can the Agile Approach Work for a Non-System Process Change?</title>
		<link>http://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-11294</link>
		<dc:creator>Can the Agile Approach Work for a Non-System Process Change?</dc:creator>
		<pubDate>Thu, 17 Nov 2011 09:18:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.bridging-the-gap.com/?p=1893#comment-11294</guid>
		<description>[...] Grooming the product backlog: agile requirements management for improved sprint planning [...]</description>
		<content:encoded><![CDATA[<p>[...] Grooming the product backlog: agile requirements management for improved sprint planning [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: An Agile Functional Specification &#124; Business, Technology and the Future</title>
		<link>http://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-9539</link>
		<dc:creator>An Agile Functional Specification &#124; Business, Technology and the Future</dc:creator>
		<pubDate>Sun, 03 Jul 2011 19:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.bridging-the-gap.com/?p=1893#comment-9539</guid>
		<description>[...] Grooming the product backlog: agile requirements management for improved sprint planning When I first started working on an agile team, one&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Grooming the product backlog: agile requirements management for improved sprint planning When I first started working on an agile team, one&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura Brandenburg</title>
		<link>http://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-8010</link>
		<dc:creator>Laura Brandenburg</dc:creator>
		<pubDate>Tue, 01 Feb 2011 00:34:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.bridging-the-gap.com/?p=1893#comment-8010</guid>
		<description>Hi lovneet,

Yes, I think adding new stories will also work. What I find when I do that, however, is that the discrete stories start to lose their value, so the value statements we put on them at the beginning that led to the initial priority might not be quite as correct once that story gets split up. This can also lead to a bunch of unfinished features because we did the primary stories but not the extra ones added. Do you run into this situation too? And, if so, how do you deal with it?</description>
		<content:encoded><![CDATA[<p>Hi lovneet,</p>
<p>Yes, I think adding new stories will also work. What I find when I do that, however, is that the discrete stories start to lose their value, so the value statements we put on them at the beginning that led to the initial priority might not be quite as correct once that story gets split up. This can also lead to a bunch of unfinished features because we did the primary stories but not the extra ones added. Do you run into this situation too? And, if so, how do you deal with it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lovneet</title>
		<link>http://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-8005</link>
		<dc:creator>lovneet</dc:creator>
		<pubDate>Mon, 31 Jan 2011 14:14:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.bridging-the-gap.com/?p=1893#comment-8005</guid>
		<description>I usually start with defining what different modules are to be developed. This is because, in realistic conditions, a final list of features is never there. There are always &quot;some last minute changes&quot;. So I begin with the entry and exit points and group the modules which have similar functionality. e.g. when u select or click something a list comes up. So now no matter what a user will select there will be a list. So i define the stories based on this and later add more stories specific to the item in question.</description>
		<content:encoded><![CDATA[<p>I usually start with defining what different modules are to be developed. This is because, in realistic conditions, a final list of features is never there. There are always &#8220;some last minute changes&#8221;. So I begin with the entry and exit points and group the modules which have similar functionality. e.g. when u select or click something a list comes up. So now no matter what a user will select there will be a list. So i define the stories based on this and later add more stories specific to the item in question.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Best Links of the Week &#8211; Christmas 2009 Version : Agile PM Scrum</title>
		<link>http://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-4283</link>
		<dc:creator>Best Links of the Week &#8211; Christmas 2009 Version : Agile PM Scrum</dc:creator>
		<pubDate>Sat, 26 Dec 2009 01:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.bridging-the-gap.com/?p=1893#comment-4283</guid>
		<description>[...] Grooming the Product Backlog &#8211; Laura Brandenburg talks about the role of requirements management through the Scrum Product Backlog. [...]</description>
		<content:encoded><![CDATA[<p>[...] Grooming the Product Backlog &#8211; Laura Brandenburg talks about the role of requirements management through the Scrum Product Backlog. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

