Comments on: How to Groom the Product Backlog for Improved Sprint Planning https://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/ We'll Help You Start Your Business Analyst Career Sun, 27 Sep 2015 16:37:20 +0000 hourly 1 https://wordpress.org/?v=6.6.2 By: How to Define Scope in an Epic | VaughnPaul.com https://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-429258 Sun, 27 Sep 2015 16:37:20 +0000 http://www.bridging-the-gap.com/?p=1893#comment-429258 […] and “user stories.” In most cases epics are just really large stories that sit far down on your product backlog until the team is ready to flesh them out into more detail.  The logical question is how to scope […]

]]> By: Can the Agile Approach Work for a Non-System Process Change? https://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-429257 Thu, 17 Nov 2011 09:18:11 +0000 http://www.bridging-the-gap.com/?p=1893#comment-429257 […] Grooming the product backlog: agile requirements management for improved sprint planning […]

]]> By: An Agile Functional Specification | Business, Technology and the Future https://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-429256 Sun, 03 Jul 2011 19:12:12 +0000 http://www.bridging-the-gap.com/?p=1893#comment-429256 […] Grooming the product backlog: agile requirements management for improved sprint planning When I first started working on an agile team, one… […]

]]> By: Laura Brandenburg https://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-429255 Tue, 01 Feb 2011 00:34:06 +0000 http://www.bridging-the-gap.com/?p=1893#comment-429255 In reply to lovneet.

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?

]]> By: lovneet https://www.bridging-the-gap.com/grooming-the-product-backlog-agile-requirements-management-for-improved-sprint-planning/comment-page-1/#comment-429254 Mon, 31 Jan 2011 14:14:57 +0000 http://www.bridging-the-gap.com/?p=1893#comment-429254 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 “some last minute changes”. 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.

]]>