15883Re: [scrumdevelopment] How to get from Use-Cases to a Product Backlog?
- Aug 31, 2006(responding to Stefan)
anybody an advice what a good way to integrate> We're going to use Scrum for Software-Development. By> now we used no clear model - it was more a "build&fix-> cycle" way of developing software. But what we do is, that> we use use-cases for gathering the user-requirements -> with which we made good experience. My question:
> Has> use-cases in to the product backlog. any idea is welcome!Some ideas you may want to consider...First, don't treat the Use Cases as the "requirements", treatthem as something that gives structure to the realrequirements that will be uncovered during the iterationand captured ideally as tests. Coming into the iteration,you want to have the use cases good enough to identifythe scope of what you're doing; good enough to supporta conversation that will allow the estimation of the workto be done in the iteration. Anything more is prematureand probably wasted effort.Second, split the use cases by flow, and do the high-valueflows in earlier iterations.Third, if you need even smaller granularity then there arepossible ways forward, but either of the two I will mentionhas some problems. You could split the use case intoflow steps - but this doesn't always deliver value at the endof the itaeration. You could split a flow into scenarios -but this doesn't often remove much work.Hope this helps,Paul Oldfield
- << Previous post in topic Next post in topic >>