Chapter 8. Agile Estimating and Velocity
Though this be madness, yet there is method in’t.
—Hamlet, Act 2, scene 2, Shakespeare
One of the misperceptions about agile development is that it is a Dilbert-esque practice of software teams coding away without requirements, little or no planning, no intra-team coordination, and no documentation. Indeed, the myths of agile often prevent agile to be applied in circumstances where the benefits would otherwise be substantial. As we hope to illustrate throughout this book, nothing could be further from the truth because agile is the most ...
- Chapter 8. Agile Estimating and Velocity
- from Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise
- Publisher: Addison-Wesley Professional
- Released: December 2010
This lesson presents additional approaches for estimating cost and schedule and predicting velocity. By following these guidelines and techniques, you can help your team improve its ability to both make commitments and meet them.
Share this highlighthttp://www.safaribooksonline.com/a/agile-software-requirements/99222/