This article discusses estimation techniques for teams that are adopting Scrum. The authors recommend to use story points during the release planning phase, but initially to switch to hours to estimate tasks during the sprint planning. Then the team will gradually move to using story points to estimate complete stories that members will commit for in next sprint.

Thom Roach shares with us in this blog post the metrics that he includes in iteration summary reports. The three main statistics he uses are Iteration Statistics summary, Iteration Cumulative Flow and Team Velocity Chart.

This short presentation explains why software metrics are not the panacea that we thought they might be 20 years ago. This is why moving from a predictive model to a reactive approach is the only rational course.

How do you know if you are developing and maturing as a team? How do you know you are getting good at this agile stuff? Typically agile talks about the soft side of things with a focus on the less tangible aspects such as individuals and interactions. Are there things that teams can tangibly work towards and measure their progress against? This video presents metrics that will help you assess the agile maturity of your team.

To what extent are the implications of agility in software really understood? What does it mean to deliver quality in today’s software systems, and how does that need to be reflected in the development and delivery of software today? In this podcast, Walker Royce describes the core measurements that software delivery teams should focus on in moving to agility

Keith Cerny presents in this blog post, metrics that could be used to measure agile teams performance.