Sprint Report: What All Metrics Should be There in Sprint Report?

How Sprint Report plays an important role in giving clear picture to stake holders on Team’s progress

At the end of each sprint, it is important to publish sprint report to stake holders and management. This is to showcase and appraise about the progress team made. Sprint report can have various metrics. I will talk about sprint report used in my last organization. May be it will help others to have idea about how a good sprint report look like.

|| Team Temperature

It is a small survey which will run at the time of sprint retrospective. Survey link is shared with team prior to retro. Team can discuss the survey results in retro. It gives an idea to SM and management on how team felt about the sprint. This survey usually contains two questions. First one is how team felt about the sprint on the scale of 1 to 10. Second question, a free text field where team expresses their feelings in one word like Awesome, great, busy, stuck etc.

Sprint Report

|| Customer Engagement

It is a small survey which run post sprint review. The Survey link shared with PO and stake holders to get their feedback in same fashion. This survey contains two questions. First one is how stake holders felt about the sprint on the scale of 1 to 10. Second question, a free text field where they would express their feelings in one word like Awesome, bad, exciting etc.

|| Sprint Burndown Chart

This chart usually come from the tool like Jira, VersionOne etc. It is configurable in confluence and can 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 if team was delivering stories throughout the sprint or moved to done at the end of sprint. Similarly a flat line on burndown chart shows a blocker due to some impediments.

|| Velocity Chart

This chart would display how the team has been delivering in terms of Velocity. Planned story points vs actual completed story points shown here. It shows previous sprint velocities to compare with current sprint velocity. Any scope change happened in between the sprint also shown here. It is configurable in confluence and can pull data from Jira directly. With other tools, it is ok to place screenshot 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 depicts scope changes, if any item added or removed from the backlog. It would represent current estimated timeline to complete the committed work. Management gets idea whether team would be able to complete the committed work or not. Is team looking for some help to handle any challenges or impediments ?

|| Sprint Achievements

This will talk about what was team’s sprint goal and what team could achieve in this sprint. Scrum Master or Leads would manually capture this information. This contains high level updates about team’s achievement in form of a small bullet pointed list. Team mentions major releases and milestones.

|| 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

Tracking action items is also important. Therefore retro action items should have owner along with time line to close each action items.

 || Risk & Impediments

Team mentions what all open risks and impediments are there. Team talks about how these risks and impediments impacts current and upcoming work. Also, if team have any mitigation plan, they can mention that also.

Hope this information would help you. Thanks.

Refer Scrum Guide for more information on all events, roles and artifacts.