How Do You Handle Planning and Estimation?
David Starr had a good post this week on planning future work cycles. Do you use a team's commitment to the next iteration or the team's historical performance?
Read MoreWhere you’re going or where you’ve been?
J. B. Rainsberger has a great blog entry titled Should We Measure Velocity on the importance of knowing where your team spends their time. He says knowing your history is more important than estimating new features.
It’s difficult to know where your development team is headed. Even with a perfect knowledge of how the team members work and how long it takes them to complete a feature, the specification often changes in the middle of a project. I’ve never finished a project with the original set of requirements.
