Retrospective templates for engineering teams

Engineering Team Retrospective
Look back at how your engineers build and ship software.
Technical Debt Retrospective
Find, rank and plan the paydown of your tech debt
- development
Code Review Retrospective
Make your team's code reviews faster and more useful
- development
DevOps Retrospective
Review deployments, incidents and handoffs between dev and ops.
- development
- operations
Bug Fixing Retrospective
Find out why bugs happen and stop them recurring
- development
Definition of Done
Agree as a team on what finished actually means.
Kanban Flow Retrospective
Optimize workflow and eliminate bottlenecks in your Kanban process.
Incident Response Retrospective
Learn from each incident before the next one
- operations
- management
AI Evolution Retrospective
Take stock of how AI is changing your team's work.

Frequently asked questions

How often should an engineering team run retrospectives?

Most teams run a retro at the end of every sprint or every one to two weeks. Frequent, focused retros catch small process issues before they compound into bigger ones.

How do you keep engineering retrospectives action-oriented?

End every retro with a short list of specific, owned actions, review the previous retro's actions at the start, and track technical-debt and process items somewhere the team actually revisits.