Aha! Develop | Sprint retrospective report (Advanced plan)

Plan, implement, review. Your team has moved through an entire sprint cycle and you are ready for the last step: the retrospective.

We designed the sprint retrospective report to give you everything you need for an efficient and insightful analysis. Celebrate the team's accomplishments, uncover any workflow bottlenecks, and open individual records from one page, so that your next sprint will be even more successful.

This report pairs well with the collaborative sprint retrospective whiteboard and the Aha! Roadmaps release retrospective report.

Click any of the following links to skip ahead:

• Filter your report

• Burndown

• Overview statistics

• Record details

• Performance statistics

• Share your report

Filter your report

By default, your report looks at your team's most recently completed sprint, and filters the report panels by Minutes or Points completed. You can use the filters at the top of the report to adjust this.

• Sprint: Change the report to look at any of your team's sprints, including sprints still in progress.

• By: Change the report to any estimation unit your team uses:

  • Work completed (records): A count of all records in Completed status.

  • Work completed (time/points): The Detailed estimate of completed records.

  • Effort logged: The Actual effort (in time or story points) logged on records.

Your filters will apply to every panel in the retrospective report.

Top

Burndown

The top panel of your report is a burndown chart, looking at the time, points, or records your team completed through the duration of the sprint, against an idealized burndown line.

Want to see a personalized burndown for individual team members? Navigate to Reports Burndown to use the burndown chart.

Each data point on the burndown chart represents one day. Compare your Actual progress in purple with the Ideal burndown line, and note any Events that caused your team to diverge from that ideal.

Then, mine the burndown for insights.

• Hover over a data point to see any Events that took place on that day — adding records, removing records, logging progress, or adjusting a record's estimate in either direction.

• Click on any data point to drill into that Event. Once you do, a prebuilt list report will open in a new tab with all related Records, record Statuses, the Event type, and a timestamp. You can adjust this list report for further analysis, then close the tab when you are ready to return to the original report.

Top

Overview statistics

The next section of your sprint retrospective gives you three high-level health metrics for your team's completed sprint. Your filters will affect whether the first two statistics show estimates completed, work logged, or a count of completed records.

• Features: The percent of features or feature estimates completed during the sprint.

• Requirements: The percent of requirements or requirement estimates completed during the sprint.

• Time spent: Progress through the duration of the sprint.

Top

Record details

In the next four panels of your release retrospective you can dig into details about records that were part of your sprint:

• Completed records: All features or requirements that moved to a “Done”, “Shipped”, or “Will not implement” status category within the sprint.

• Added records: All epics and features added to the sprint after its start date.

• Incomplete records: All features and requirements that were not completed when the sprint shipped.

• Removed records: All features and requirements that were removed from the sprint after the sprint start date but before the sprint shipped.

These panels are ideal for sparking conversation and answering questions.

• If your team has a large list of Incompleted work at the end of a sprint, you might be over-committing yourselves (make sure to check each individual team member's capacity!).

• If a large amount of records were Added after the sprint started, then your sprint planning might be too casual — or your team might have trouble locking down the sprint.

• If your team has Completed everything they committed to — celebrate that win, and talk about whether you should commit to more in the future.

Click into any record to open its drawer view and review or change record details.

Top

Performance statistics

Finally, look at your team's performance, as individuals and over the last three sprints. Your filters will affect whether these statistics show estimates completed, work logged, or a count of completed records.

• Team performance: Look at what each team member Committed to, adjusted, Completed during the sprint, and left Incomplete. It includes all teams that participated in the sprint. “Committed” means the amount of work assigned to the team after the sprint start date.

  You can use many other reports in Aha! Develop to analyze individual team members' workload and output. For teams that plan in sprints, the velocity report and burndown chart are most useful.

• Last three sprints: Look at your teams' velocity over the last three completed sprints.

  If this panel piques your curiosity, navigate to Reports Velocity to explore the full velocity report further.

Top

Share your report

You might complete a classic sprint retrospective live, with the entire development team viewing this report together — and maybe in conjunction with a collaborative sprint retrospective whiteboard. But there are also times when you will want to share this report with stakeholders outside your team. To do that, click the Export button in the upper right of the report.

• Add a static image of your sprint retrospective report to a whiteboard as an image.

• Export your report as a static PNG image.

• Export your report as a PDF.

Top