The text of this article is not in this database — only its details are. Read it on the old site: Software Project Estimation: Part 3
1 Comment
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
The text of this article is not in this database — only its details are. Read it on the old site: Software Project Estimation: Part 3
Join the conversation! Your thoughts help the community grow.
Sign in to leave a comment.
David CorbinPosted May 11, 2011, 3:55 PM
This approach is classic Waterfall [such as CMMI]. BRUF [Big Requirements Up Front] is the antithesis of an Agile approach. At the start of the project, the ONLY thing that should be done is the creation of High Level (broad in scope) User Stories (Epic's). As the development processeds these are factored down to smaller user stories, and eventually into Tasks which are placed on the Product Backlog. At the start of a sprint a certain number (typically based on Story Points) is moved to the Iteraction Backlog. Agile is all about defering every decision until the point where delaying it one minute longer would cause Harm.