Retrospective: learn from every sprint

When to use it

• At the end of each sprint or project phase.
• The same irritants come back from one cycle to the next.
• The team wants to work better together.

How to do it, step by step

1. Set the frame: talk about facts and processes, not people.
2. Everyone writes what went well, what went less well, and their ideas.
3. Group the notes and vote on the priority topics.
4. Look together for concrete actions, in limited number.
5. Assign an owner and a deadline to each action, and review them at the next retrospective.

Example

Observation: “reviews come too late”. Action: reserve a review slot every Tuesday, owner: Lea, to re-check in two weeks.

In FluidOps

In FluidOps' “Other tools” tab, fill in the board with your team, save it and export it as PNG or PDF.

Try it in FluidOps →

Going further

• The Scrum method: roles, events and artifacts
• Agile project management: principles and implementation

Same family

• Lean Coffee
• Pecha Kucha
• All methods
• Start from your problem: which tool for which problem?