Sprint Summary

Generate AI-powered sprint reviews that automatically summarize completed work, organize issues by theme, and create ready-to-use sprint demo agendas.

Sprint Summary provides AI-generated reviews of completed sprint work, automatically analyzing closed issues and organizing them into thematic groups. This transforms manual sprint review preparation into instant, comprehensive summaries for demos and stakeholder updates.

Understanding Sprint Summary

Sprint Summary uses AI to analyze completed sprint work and create structured summaries. For sprints with closed issues, you'll see a banner prompting Get your Sprint Review summary now! with a Generate your Sprint Review button. For sprints without closed issues, the report displays a message that no issues were found.

Accessing the report

Navigate to Reports in the left sidebar and select Sprint Summary. Use the Sprint dropdown at the top to select different sprints for analysis.

Generating and managing summaries

Click Generate your Sprint Review to create an AI summary. After generation, the interface displays a velocity link to the Team Velocity report, a Regenerate button, and a scheduled update dropdown showing when the next automatic generation will occur. Summaries are generated 3 times per sprint automatically: a few days in, before end of sprint, and at sprint end.

Editing summaries
Click the generated summary text to access editing mode with refinement options: Rephrase, Make it shorter, Make it longer, More technical, and Less technical. A rich text toolbar is also available for manual formatting.

Reading the summary

The AI creates a high-level summary paragraph describing sprint accomplishments, followed by issues organized into thematic groups like API Development and Other issues. Issues are categorized with collapsible sections for easy navigation.

Issues closed outside the sprint's official timeframe appear with a Completed after sprint ended marker. These indicators help teams identify scope creep, work that carried past the sprint deadline, and issues added retroactively — useful context for retrospectives about sprint planning accuracy.

Troubleshooting

If Sprint Summary isn't generating, verify that your sprint contains completed issues within the sprint timeframe and has proper start and end dates configured. For poor issue categorization, ensure issues have descriptive titles and appropriate labels — the AI relies on this metadata to create meaningful groupings.

FAQ

Q: How often are Sprint Summaries generated automatically?
A: Sprint Summaries are generated 3 times per sprint: a few days in, before the end, and at sprint end. You can also manually regenerate once per day if needed.

Q: Can I edit the AI-generated sprint summary?
A: Yes. You can edit both the summary text and issue organization. Manual editing disables automatic scheduled generation for that sprint.

Q: Why don't I see a summary for my completed sprint?
A: Sprint Summary requires completed issues within the sprint timeframe. Ensure your sprint has closed issues and proper start and end dates configured.

Q: Can I use Sprint Summary for sprints without story point estimates?
A: Yes. Sprint Summary works with any sprint containing completed issues, regardless of whether those issues have story point estimates.

Q: How long are Sprint Summary reports retained?
A: Sprint Summary reports are retained for historical reference and can be accessed for both open and closed sprints through the sprint selection dropdown.