Sprint reporting

As the name suggests, this is a quick wrap-up of what came out of the Daily Scrum — covering ticket progress, early blockers, and how the team is feeling about the Sprint goal.

While it's not a status report for managers, it’s a brilliant way to keep stakeholders in the loop on where the team stands and where it's heading next.

• Every day

The Retrospective is a vital ceremony for team inspection and continuous improvement—providing a dedicated space to celebrate successes and highlight issues that impacted progress toward the Sprint goal.

All proposed improvement actions are clearly documented and shared with the team, ensuring relevant items are prioritised and given dedicated time for implementation during upcoming Sprints.

• Once per Sprint

The Sprint Report provides a comprehensive overview of completed work, carried-over items and their impact on subsequent Sprints, team velocity and burndown trends, and a summary of backlog adjustments. We also highlight upcoming milestones, potential risks, and any changes to team capacity for the next Sprint.

• Once per Sprint

While the Sprint report provides a granular breakdown of team performance and delivery mechanics, the stakeholder report offers a high-level executive summary — highlighting released features, current roadmap position, and upcoming milestones for the next phase.

• Once per Sprint

• Once per Sprint

• Once per Release