Welcome to Scrum Dynamics episode 17, sponsored by Maplytics from Inogic.

In this episode, 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.
  • How to handle story point inflation that sometimes happens during long running projects.
  • 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.
  • Why you shouldn’t use velocity to compare the performance of different teams.
  • Is velocity a measure of value delivered by the development team? Or should product owners assign ‘value points’ to stories to track value separately from effort.
  • Story completion – the number of stories completed in the sprint as a percentage of the total number of stories
  • Epic completion – the percentage completion of each epic to track the progress of a release
  • Burn down charts and burn up charts to track the amount of work completed and the amount of work remaining over time for a sprint or release. 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.
  • Why writing holiday cards one at a time is a better idea than batching the tasks, and developing features is the same.
  • 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.

You can find out more about how to apply Scrum to your Dynamics 365 projects with the Introduction to Scrum for Dynamics 365 video course. Click here to claim your CRM Audio subscriber discount.