8 Important Metrics for Sprint Report to provide better visibility about Team
At the end of each sprint, it is important to publish to sprint report to stake holders and management to showcase and appraise about the progress team made. There are various metrics/data can be included in the sprint report. Here I will share with my experience what has been included in Sprint report in my organization. May be it will others to have idea about how a good sprint report look like.
|| Team Temperature
This is a small survey which will be run at the time of sprint retrospective. The Survey link can be shared with team before coming to retro and at the time of retro team can discuss the survey results. It will give an idea to SM and management also that how team felt about the sprint. This survey usually contains two questions, 1 stone would be about how team felt about the sprint on the scale of 1 to 10. 2 ndquestion would be a free text field where team would express their feeling in one word like Awesome, great, busy, stuck etc.
This is also a small survey which will be run post sprint review. The Survey link can be shared with PO and stake holders and ask them to provide their feedback in same fashion. This survey would also contains two questions, 1 stone would be about how stake holders felt about the sprint on the scale of 1 to 10. 2 ndquestion would be a free text field where they would express their feeling in one word like Awesome, bad, exciting etc.
|| Sprint Burndown Chart
This chart is usually come from the tool like Jira, VersionOne etc. If using Jira and confluence, then it can be configured in confluence and it would pull burndown chart directly from Jira. This would give idea about how team completed stories in the sprint. There are few interpretations with Burndown chart like whether team was delivering stories throughout the sprint or moved to done at the end of sprint and whether team got stuck as there was a flat line for few days on burndown chart.
|| Velocity Chart
This chart would display how the team has been delivering in terms of Velocity. It would show planned story points vs actual completed story points. Also it would show previous sprint velocities to compare with current sprint velocity. It will also show if there is any scope change happen in between the sprint. Again this also can be configured in confluence and data can be pulled from Jira directly. With other tools, a screenshot can be placed in the report directly.
|| Release Burnup Chart
This chart would show release level progress made by the team. How team is moving towards release commitment. It will show scope change i.e. if there are new items added or removed from the backlog. It would represent current estimated timeline to complete the committed work. It would give an idea to management also that whether team would be able to complete the committed work or they are looking for some help or there are some challenges or impediments which need to be addressed.
This will talk about what was team’s sprint goal and what team could achieve in this sprint. This information would be manually entered by SM/Leads. This would be high level updates about team’s achievement, may be in form of a small bullet pointed list. Team can mention major releases/milestones also.
|| Next Sprint Plan
This will talk about what is team’s goal for upcoming sprint and what team planning to achieve in next sprint. This would be also high level plan only.
|| Retro Actions
Here retro action items can be mentioned, who own which action items and what is time line decided to close each of the action items.
|| Risk & Impediments
Team would mention what all open risks and impediments are there. Team would also talk about how these risks and impediments are impacting current and upcoming work and if there is any mitigation plan, they may mention that also.
Hope this information would help you. Thanks.
Originally published at https://bandanwar.com on October 18, 2021.