Sprint retrospective notes template
Turn a retrospective into one useful change for the next sprint. Preserve observations, avoid blame, and make the experiment small enough to evaluate.
Free template + filled example. No account required. How to use the Skill
- Made for
- Engineering & product
- Suggested conversation
- 45–60 minutes
- Take it with you
- Markdown · Prismical Skill
See the finished note.
Use this after a sprint or delivery cycle. This fictional team is investigating a review bottleneck. The template keeps proposed explanations separate from observations and avoids turning an individual comment into a team-wide verdict.
Notes / worked exampleRetrospective · Review queue
Sprint context
The sprint goal was to ship the invitation flow. The team shipped it, but review work clustered near the end.
What helped
Pairing on the first implementation reduced uncertainty about permission checks.
What got in the way
Three changes waited for review until the final day. The reason for the queue has not been established.
Contributing factors to investigate
Hypothesis: reviewers did not know which changes were ready. Check when review requests were sent and acknowledged.
Next sprint experiment
Ari will try a daily review check-in next sprint. Track whether review requests wait more than one working day.
Review point
Evaluate the waiting-time notes at the next retrospective. No calendar date was stated.
Read the source dialogue for this example
- Ari: We shipped the invitation flow. Pairing on the first implementation helped with the permission checks.
- Bo: Three changes waited for review until the final day.
- Ari: Maybe we were not clear about which changes were ready. We should check the request timestamps.
- Bo: That is a hypothesis, not something we know yet.
- Ari: I will try a daily review check-in next sprint and track requests waiting more than one working day.
- Bo: Let’s evaluate those notes at the next retrospective.
Start with a blank page.
Keep the useful structure.
Each field earns its place. Use the prompts as reminders, then replace them with your own meeting evidence.
Sprint context
Name the sprint goal and the relevant result. Include a metric only when you have a source; avoid reconstructing a velocity chart from memory.
What helped
Capture a repeatable behavior that made work easier. Concrete practices are more useful than general praise.
What got in the way
Write observable events before explanations. Keep comments about process distinct from judgments about people.
Contributing factors to investigate
List plausible explanations and what evidence would distinguish them. Do not label a root cause without testing it.
Next sprint experiment
Choose a small process change with a named owner, a timebox, and an observable success signal. Avoid starting several unrelated initiatives.
Review point
Decide when and how to evaluate the experiment. A failed experiment can still teach something useful.
# Sprint retrospective notes template Date: [add date] Participants: [add names] Purpose: [add purpose] ## Sprint context [Name the sprint goal and the relevant result. Include a metric only when you have a source; avoid reconstructing a velocity chart from memory.] ## What helped [Capture a repeatable behavior that made work easier. Concrete practices are more useful than general praise.] ## What got in the way [Write observable events before explanations. Keep comments about process distinct from judgments about people.] ## Contributing factors to investigate [List plausible explanations and what evidence would distinguish them. Do not label a root cause without testing it.] ## Next sprint experiment [Choose a small process change with a named owner, a timebox, and an observable success signal. Avoid starting several unrelated initiatives.] ## Review point [Decide when and how to evaluate the experiment. A failed experiment can still teach something useful.]
Make it part of the meeting.
Before · collect observations
Bring concrete events and invite people to contribute privately if needed. Agree how comments will be recorded and avoid attributing sensitive feedback without consent.
During · separate causes from guesses
Group related observations, then ask what evidence explains them. Keep multiple explanations alive until the group has enough information to choose a useful experiment.
After · make the experiment visible
Place the accepted experiment where the team tracks work. At the next retrospective, review what changed rather than simply carrying the same action forward indefinitely.
What to watch for
- Recording a hypothesis as a proven root cause.
- Collecting ten actions and assigning none of them.
- Using retrospective notes to rank or blame teammates.
Turn the template
into a Prismical Skill.
Import the file
Download the Skill JSON above. In Prismical, open Settings → Skills → Import and select the file. This downloads a file; it does not install anything automatically.
Run it on a note
Open the note with your meeting transcript. Run the imported Skill from the note dock. It asks for this template’s sections and appends the result for review.
Check before sharing
Verify quotes, owners, dates, and missing context against the transcript. AI can make mistakes. Keep the original note and follow your team’s sharing policy.
A few useful answers.
Practical details before you use this resource.
Can I use start, stop, continue?
Yes. Use those headings to collect observations, then keep the experiment and review-point sections. Without an observable next step, the three lists can become the same discussion every sprint.
How many improvements should we choose?
Start with one or two changes the team can actually test. The right number depends on capacity, but every chosen change should have an owner and a way to evaluate whether it helped.
Keep the work moving.
Useful next steps for the conversation you are preparing for.
Sprint planning notes template
Document a sprint goal, capacity assumptions, selected work, dependencies, and scope trade-offs. Free planning notes template with a concrete example.
Explore resource TemplatesOne-on-one meeting notes template
A free one-on-one notes template for employee priorities, feedback, support, and agreed follow-ups. Includes a filled example and reusable Prismical Skill.
Explore resource Free toolsFree action items extractor
Find explicit action candidates in meeting text, with source lines and owner or timing hints. Review and copy the result. Free tool that runs in your browser.
Explore resource WorkflowsAI meeting notes for product managers
Connect customer interviews, design reviews, and sprint decisions with Prismical. Practical product-management note workflows and reusable templates.
Explore resourceBring your next conversation
into Prismical.
Capture the conversation, keep the transcript beside your notes, and reuse a Skill for the output you need. Review the result before you share it.