iteration planning
Articles
 |
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. |
Better Software Magazine Articles
 |
Building Highly Productive Teams Using a Commitment-to-Progress Ratio: 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. |
Recommended Web Seminars
| On Demand | Building Confidence in Your Automation |
| On Demand | Leveraging Open Source Tools for DevSecOps |
| On Demand | Five Reasons Why Agile Isn't Working |
| On Demand | Building a Stellar Team |
| On Demand | Agile Transformation Best Practices |
Featured Resources
Visit Our Other Communities
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.