In certain situations it may become necessary to vary the length of a sprint cycle. Because velocity is defined as work done per sprint, any variation of the sprint length during a project will skew the team's velocity measurement. Some reasons for changing sprint length are as follows:
- Team decides that shorted (or longer) sprints work better after project is underway.
- Not all sprint items are completed at the end of a sprint and there are not enough items in the release to fill an additional sprint of the same length.
I would like to see a report that calculates velocity per unit time. This would present a clearer picture of the rate at which work was being performed. It would also potentially increase the accuracy of the release forecasting tool.
by: Mike C. | over a year ago | Reporting & Analytics
Comments
there are many organizations that do variable length sprints... I think handling this situation would be a good thing to consider if a large enough portion of your customer base is asking for it.
The Fall 2010 release introduced a Velocity By Date range report to the Dashboards in Analytics.