iteration planning

Articles

Building Highly Productive Teams: Work Committed vs. Done
This article explains methods to build a team that will embrace "required work" and deliver robust software in a predictable fashion. It proposes a measure that helps calculate the throughput of an agile team by comparing work committed to work actually done.
We're Agile

I always recommend to teams newly transitioning to agile that they keep every iteration the same length. This helps them learn to manage their time, and after a few iterations they'll start to get a rhythm. Hopefully, they'll learn to work incrementally, doing testing and coding concurrently as part of one development effort, so that user stories are finished throughout the iteration, and testing isn't pushed to the last day.

Visit Our Other Communities

The home for software testing and QA professionals—practical advice on test automation, test management, test techniques, and more.
Where configuration management and development professionals go for answers on SCM, ALM, change management, DevOps, tools and more.