Retro Script Template

Structure for retros: went well, didn't go well, suggestions.

Quick answers

How do I contribute in a retro?
Share wins, challenges, and concrete improvement ideas.

Key takeaways

  • Share concrete examples.
  • Suggest improvements.
  • Focus on process, not people.

Instead of → Say

Instead ofSay
Communication was badWe could improve handoff from dev to DevOps. A pre-deploy checklist might help.
X did greatThe pairing sessions unblocked the frontend work. We should do more of that.

Example dialogue

Went well: pairing on the migration. Didn't go well: deploy delays. Suggestion: 15-min pre-deploy sync.

Common mistakes

  • Blaming.
  • No suggestions.

Frequently asked questions

What do you say in a retro?
What went well, what didn't, and suggestions for next sprint.

Related

Ready to practice?

Try a scenario with AI and get feedback on your communication.

Start practicing