And thanks again for the book recommendations. I'll check them out.
On Nov 25, 5:25 am, Robrecht <
robrecht.da...@ae.be> wrote:
> Crow
>
> My suggestion:
> - use Volere to add discipline to your requirements engineering.
> - use a lean approach (scrum) to decide when you will write your
> requirements.
>
> Scrum puts all work to be done in a product backlog. A list of stories
> that deliver value (a slice of functionality) to the user. Volere
> tells us to look for the business use cases first and then decide on
> the scope and calling these product use cases. Put these (product use
> cases) as stories on your product backlog.
> Then describe the requirements associated with these stories, put
> effort only on those things that are really required (required: => it
> must be so, it cant be any other way).
> Your backlog items are then the starting point for your conversation
> with the development team. They can suggest any other solution as long
> as the solution complies with the requirements.
>
> Agile and Iterative Development by Craig Larman
> Agile Estimating and Planning by Mike Cohn
> Agile Project Management with Scrum by Ken Schwaber
>
> Hope this helps
>
> Robrecht DAVID