Tracking Scrum Metrics

Tracking Scrum Metrics

#17. Dermot and Neil discuss what to measure in your Dynamics 365 projects when you're using Scrum.

Tracking velocity is the basic measure of progress. Velocity is the total number of story points of 'done' stories in each sprint and should be averaged over several sprints (usually 3 to 5 sprints).

Using velocity within the team to plan the capacity for the next sprint, and by the product owner for forecasting the release.

There's no velocity credit for partially done stories at the end of the sprint.

Velocity predictability is a measure of how close the actual velocity of each sprint is to the planned velocity to track the accuracy of estimating and capacity planning within the team.

Neil discusses using a sprint burn down chart for highlighting an issue with testing stories, and a release burn down chart for highlighting changes in project scope. What to include in an iteration report for managers and stakeholders. (Except for Dermot who doesn't do status reporting!)

Tracking effort spent on bug fixing and setting aside a buffer when planning your sprint capacity.

Tracking percentage of stories blocked within a sprint to highlight issues impeding the scrum team's progress.

Remember to surround your metrics with conversations to help your team improve their performance rather than report performance to stakeholders.

Support the show (