Velocity is a measurement of how much the team gets done in a given sprint. Velocity is what actually got done in the last iteration not what is planned. Typically, it is measured in story points. Each feature in scrum is a story. A story has points. Points can be anything you come up with.
ScrumEdge, like most scrum teams, doesn’t use story points for stories. Product Owner’s create stories and assign priority and the scrum team selects stories, breaks them down into tasks and assigns estimates to each task, mostly in terms of hours.
We added a new feature called “Project Velocity” which gives team members, Stakeholders and ScrumMasters the ability to view the actual budget burnt by individual team member as well as the whole team for a project. While this information was available for each sprint on the Projects Dashboard, we felt there was a genuine need for a chart showing budget burn for all sprints in a project. This data is mapped on a linear graph so as to see budget burn trends over the course of a project and be accessed by clicking the “Project Velocity” link on the dashboard.
The Velocity Chart below is based on sample data. It shows each sprint in the project on the x-axis and budget used by the sprint team on the y-axis.
This particular chart shows that the budget burn over the course of the project is fairly inconsistent (see the sudden dips in Sprint 3 and Sprint 8). As a ScrumMaster I would should take immediate notice of these inconsistencies and investigate why my team’s budget burn varies so much from sprint to sprint.
Did you see any particular trends on your Project Velocity chart? If so, did you figure out the reasons behind the trends?
Tell us what you think about this feature using our feedback page.
