In Scrum, the velocity is defined as amount of work that the team can handle in one sprint. This is an important measure as it is used to plan the future iterations and to verify that the team is progressing at a constant and comfortable pace. In this blog post, Agile coach Rachel Davies presents a FAQ on how to calculate velocity.
“You cannot manage what you cannot measure” is an old adage in the project management world. Is this still valid in the Agile and Scrum world where people are preferred over processes and tools? In fact Scrum is disciplined and uses a lot of metrics, so you might like this newly proposed Scrum Adherence Index.
Velocity can be defined as a measurement of how much the Scrum team can get done in a Sprint, based on past results. In this article, Beth Macy discusses how reliable is velocity and how you can use it.
Metrics are an important tool when you want to manage something. It is very important to define what you want to measure as this will also impact your project team activity. In this blog post, Bob Boyd proposes 9 metrics for Scrum.
An old project management quote says “You can’t control what you can’t measure”. This is not different when you use Scrum. In this blog post, David Koontz proposes a list of metrics that can be used to assess the activity of Scrum teams.
Klaus Bucka-Lassen discusses the estimation with story points in Scrum. Story points are a different way to estimate features in Scrum. Story points are a measurement of a feature’s size relative to other features and not a measure of the time needed to complete a feature.
One of the important point in the Scrum Agile project management approach is the fact that user stories are estimated using a relative size and not the “exact” man/days measure used to size effort by traditional approaches. In his blog post, Ilan Goldstein discusses how to explain the relative estimation concept in Scrum.