A retrospective asks what the team should keep, stop and change after a sprint or a project. Collecting answers in a form beforehand means the meeting starts with everyone's view, not only the loudest. Keep the answers anonymous if trust is still being built.
We've ticked a short starter set. Change it to suit you.
What went well
What didn't go well
What we learned
How we worked
What to change
6 questions selected
Tips for a better retrospective
Agree on one or two changes only, and give each an owner.
Start the next retrospective by checking whether the last changes happened.
Talk about the process and the plan, never about who is to blame.