Agile

Sprint Retrospective Template

A structured 60-minute framework for engineering and product teams to analyze the previous sprint and commit to concrete process improvements.

When to use this template

•At the conclusion of a two-week development cycle to evaluate team velocity and collaboration.
•When recurring process blockers are causing missed deadlines or reduced code quality.
•To reset team dynamics after a major product release or a significant shift in project scope.

How to fill it in

1.Open the template and set the 60-minute agenda to keep the discussion focused on outcomes rather than venting.
2.Allow 10 minutes of silent brainstorming where team members list specific observations in the Start, Stop, and Continue columns.
3.Group similar sticky notes and use dot-voting (3 votes per person) to identify the top 3 items requiring action.
4.Document every action item with a clear owner, a hard deadline, and a mid-sprint checkpoint date.

Template preview

60-Minute Agenda

·Set the Stage: Review sprint goals (5m)
·Gather Data: Silent brainstorming (10m)
·Generate Insights: Group discussion (20m)
·Decide What to Do: Dot-voting (10m)
·Close: Action item assignment (15m)

Continue (What went well)

·Daily standups concluding in under 12 minutes
·High quality of documentation for the new API endpoints
·Quick turnaround on PR reviews from senior devs

Stop (What didn't work)

·Scope creep mid-sprint without updating the sprint goal
·Manual deployments causing downtime in staging
·Over-reliance on Slack for complex architectural decisions

Action Items

·Owner: @engineering_lead | Due: [Date] | Item: Automate staging deploys
·Owner: @product_manager | Due: [Date] | Item: Formalize scope change policy
·Owner: @scrum_master | Due: [Date] | Item: Schedule weekly deep-work blocks

Copy as Markdown

# Sprint Retrospective: [Sprint Name/Number]

**Date:** [Date]  
**Participants:** [Team Members]  
**Sprint Goal Status:** [Achieved/Partial/Missed]

---

## 1. Meeting Agenda (60 Minutes)
- **00-05m:** Intro & Previous Action Item Review
- **05-15m:** Silent Brainstorming (Filling the columns below)
- **15-35m:** Discussion & Theme Grouping
- **35-45m:** Dot-Voting on Top Priorities
- **45-60m:** Action Item Definition & Assignment

---

## 2. Retrospective Columns

### Continue
*Things that are working well and we should keep doing.*
- [Item 1]
- [Item 2]
- [Item 3]

### Stop
*Blockers, inefficiencies, or habits that are hurting the team.*
- [Item 1]
- [Item 2]
- [Item 3]

### Start
*New ideas or experiments we want to try in the next sprint.*
- [Item 1]
- [Item 2]
- [Item 3]

---

## 3. Dot-Voting Rules
1. Every participant gets **3 votes** (represented by a +1 or emoji next to an item).
2. You can put all 3 votes on one item or spread them out.
3. The **top 3 items** by vote count must result in an Action Item.

---

## 4. Action Items
| Priority | Action Item Description | Owner | Due Date | Checkpoint Date |
| :--- | :--- | :--- | :--- | :--- |
| 1 | [Clear, measurable task] | [Name] | [YYYY-MM-DD] | [Mid-Sprint Date] |
| 2 | [Clear, measurable task] | [Name] | [YYYY-MM-DD] | [Mid-Sprint Date] |
| 3 | [Clear, measurable task] | [Name] | [YYYY-MM-DD] | [Mid-Sprint Date] |

---

## 5. Follow-up Cadence
- **Mid-Sprint:** Owners provide a status update in the [Team Channel].
- **Next Retro:** Review completion of these items before starting the next session.

> **Tip:** Keep action items small. If an item can't be finished in one sprint, break it down.

Template provided by Planet Roadmap.

Use Planet Roadmap's built-in Sprint views to track your retrospective action items alongside your main product backlog.

Skip copy-paste. Set up this template inside a Planet Roadmap project in one click.

Try Planet Roadmap Free

FAQ

Who should facilitate the Sprint Retrospective?

Typically the Scrum Master or a Project Manager facilitates. However, for high-trust teams, rotating the facilitator role each sprint can increase engagement and provide different perspectives on the process.

What if the team identifies more than three major issues?

Focus is key. Trying to change too much at once usually results in nothing changing. Use dot-voting to pick the three most impactful items and save the others for a future retrospective if they persist.

How do we handle 'Start' items that require budget or external approval?

Assign an action item to the Product Manager or Lead to investigate the feasibility. The action item isn't 'implement the tool,' but rather 'get a decision on the tool' by a specific date.

Should we share the results of the retrospective with stakeholders?

While the discussion should be a safe space for the team, sharing the 'Action Items' or 'Continue' list can be helpful for transparency. Avoid sharing specific individual criticisms outside the team.

Related templates