The Retrospective

A regular meeting to take stock of the teams's delivery performance and make changes to improve working practises.


Improve the Agile Delivery Process through critical self-examination of the completed iteration.

Participants and Responsibilities

  • Sprint Team Lead
    • Schedule the meeting and invite participants.
    • Host the meeting and run the agenda.
  • Sprint Team Members
    • Contribute helps, hinderances, and identify any unplanned work that impacted the sprint velocity.


Sprint retrospectives should take place either on the last day of a sprint or as the first activity on the first day of the new sprint. Allocate 30-60 minutes.

Example Agenda

  1. 10 minutes - Review committed stories in the sprint.
  2. 10 minutes - Complete “Rose/Thorn/Bud” feedback.
  3. 10 minutes - Review feedback as a team and create actions to address the issues identified.

After the session, the team lead should:

  • Log any “technical debt” as stories (or features!) in the Architecture epic.
  • Move any incomplete stories to the next sprint.

All stories in the previous sprint should be marked as complete. If they aren’t, they should be moved to the current sprint.

The team should aim to have zero stories carried over to the next sprint. Any stories that are carried over should be reviewed and measures taken to prevent incomplete work for subsequent sprints.


Try not to overthink the category definitions too much, but this is overview might be helpful:

Category You feel It is Loose definition Action
Rose Pleased, fulfilled Positive Something that is working well or effectively Celebrate and encourage
Thorn Disappointed, frustrated Negative Something which is not working well or decreases productivity. Address root causes
Bud Energised, inspired Opportunity Something that needs to be explored for growth or improvement. Plan them

After collecting feedback, use Affinity Clustering to identify themes in the items. Identifying related topics in this way will make it easier to find ways to address the feedback and improve delivery processes for the next sprint.

Alternate schemes for gathering feedback include:

  • “Mad, sad, glad”
Edit this page on GitHub

The content on this page is published under Open Source licenses via GitHub. To submit issues or provide feedback please visit the repository.