Skip to content

Instantly share code, notes, and snippets.

@dhruvagarwal
Last active August 3, 2023 18:55
Show Gist options
  • Save dhruvagarwal/ab7d3bccb36f784d7e0dccfe804b2dfb to your computer and use it in GitHub Desktop.
Save dhruvagarwal/ab7d3bccb36f784d7e0dccfe804b2dfb to your computer and use it in GitHub Desktop.
Sprint Retrospective Template

[Meeting Title]

Dates: [Start Date] to [End Date]

Structure of the meeting

[x] Set common goal for the meeting [x] Feedback on the last solutions [x] Set a structure for thinking around the whole sprint [x] Everyone adds their points [x] Everyone discusses what the common problems/wins are [x] Everyone concludes on what can be done better in the next sprint

Goal

Why retrospective?

To understand how we can improve as a group and be more productive in each sprint. It is a feedback loop which we'll do after every sprint, to understand gaps, friction and areas of growth.

What should be the outcome?

Concrete action items for us to help be better as a team in the next sprint.

How will we decide?

We will use the following format to categorise our tasks. We will discuss every task that was picked in the sprint.

Retrospective Format Image

Planned tasks: The tasks which we had committed to deliver to the business before starting development Unintended tasks: The tasks which we picked because of any reason - adhoc, surprises, free bandwidth Successful: Features/Bug fixes which can be used by the user and derive the value we promised. Failed: Features/Bug fixes which cannot be used by the user/derive the value we promised.

Review of the last retrospective

These are the items which were discussed to be resolved after the last retrospective. While all of them could not be resolved, we should acknowledge how many of them became better in this sprint:

Solutions

[Insert solutions here]

Suggestions

Current Sprint Retrospective

Questions

Tasks

  1. [Task 1 Title](Task 1 Link) @[Assignee 1]
  2. [Task 2 Title](Task 2 Link) @[Assignee 2]

Planned, Successful

Tasks What went good What went bad
[Task 1 Title](Task 1 Link) @[Assignee 1] [Insert good points] [Insert bad points]
[Task 2 Title](Task 2 Link) @[Assignee 2] [Insert good points] [Insert bad points]

Planned, Failed

Tasks What went good What went bad
[Task 1 Title](Task 1 Link) @[Assignee 1] [Insert good points] [Insert bad points]
[Task 2 Title](Task 2 Link) @[Assignee 2] [Insert good points] [Insert bad points]

Unintended, Successful

Tasks What went good What went bad
[Task 1 Title](Task 1 Link) @[Assignee 1] [Insert good points] [Insert bad points]
[Task 2 Title](Task 2 Link) @[Assignee 2] [Insert good points] [Insert bad points]

Unplanned, Failed

Tasks What went good What went bad
[Task 1 Title](Task 1 Link) @[Assignee 1] [Insert good points] [Insert bad points]
[Task 2 Title](Task 2 Link) @[Assignee 2] [Insert good points] [Insert bad points]

Problems in the current sprint

Person1 [Done]

  • [Insert their points]

Person2

  • [Insert their points]
  • ...

Common problems

Problems People
[Problem 1 description] @[Person affected/reporter]
[Problem 2 description] @[Person affected/reporter]
... ...

Good things that happened in the current sprint

Person1 [Done]

  • [Insert their points]

Person2

  • [Insert their points]
  • ...

Sprint Velocity 🏎

[Insert sprint velocity details]

Learnings from the current sprint

Person1 [Done]

  • [Insert their points]

Person2

  • [Insert their points]
  • ...

Suggestions for next sprint

Person1 [Done]

  • [Insert their points]

Person2

  • [Insert their points]
  • ...

Team conclusions

Solutions

[Insert team solutions]

Improvements

[Insert areas of improvement]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment