Sprint Retrospective: [Sprint name]

Dates: [Sprint start and end]
Facilitator: [Name]
Participants: [Team]
Sprint goal: [Expected outcome]

Working agreement

Focus on processes and conditions, not blame. Make space for every participant, and agree what can be shared outside the team.

Previous actions

Action from last retrospective	Owner	Result	Keep, change, or stop?
[Experiment]	[Name]	[Observed outcome]	[Decision]

Sprint outcomes

Goal or commitment	Outcome	Evidence or context
[Sprint goal]	[Met / partly met / not met]	[User outcome, demo, or release evidence]

Unexpected work: [Interruptions, incidents, dependencies, or scope changes.]

What went well

• [Observation and a concrete example]
• [Practice worth continuing]

What made work harder

• [Observation, impact, and example]
• [Handoff or workflow that caused friction]

What we learned

[New knowledge about the users, system, or team workflow.]

Explore the highest-impact issue

Observation: [What happened, without attributing motives.]

Impact: [Effect on users, quality, or the team.]

Contributing conditions: [Evidence-backed causes; distinguish assumptions from facts.]

Within our control: [What the team can change next sprint.]

Improvement experiments

Choose one or two actions the team can realistically complete.

Experiment	Owner	Due date	Success signal	Review date
[Specific change to try]	[One accountable person]	[Date]	[Observable improvement]	[Next retrospective]

Parking lot

Topic	Follow-up owner	Next step
[Topic requiring another discussion]	[Name]	[Action]

Closing check

• Action owners agree to the experiments.
• Follow-up work is visible in the team’s tracker.
• The next review date is set.