DAKI Retrospective

• Reviewing the team's process or tools rather than one sprint's events.
• When the backlog of 'things we do' has grown and needs pruning.
• Setting up experiments for the next sprint.

Purpose: Improve the team's working practices and processes.

• 🗑️ Drop

  What should we eliminate?

• ➕ Add

  What should we introduce?

• 🔒 Keep

  What should we preserve?

• 🔧 Improve

  What should we change or optimise?

1. 1

   Define the scope · 2 min

   Name which practices are in scope (e.g. ceremonies, code review, release process).

2. 2

   Silent brainstorming · 6 min

   Keep the room quiet so everyone thinks on their own first. Remind people one idea per card.

3. 3

   Share & group observations · 7 min

   Ask each person to briefly read their cards. Clarify, don't debate. Move duplicates next to each other or into the right column.

4. 4

   Vote · 4 min

   Everyone spends their votes on what matters most. Totals stay hidden until you move on.

5. 5

   Evaluate the most important changes · 8 min

   For each top card: what's the smallest version of this change we could try?

6. 6

   Agree on experiments & owners · 5 min

   Frame changes as experiments with an owner and a review date.

Notes a software team might write:

Expected outcome: One or two manageable process improvements.

• Keep is easy to skip — protecting what works matters.
• Treat changes as experiments you can roll back.

Each prompt is a column on a shared board. Everyone writes silently, then the team groups notes, votes with hidden totals, discusses the top cards and turns them into actions with owners.

Each stage comes with instructions for the facilitator and the participants and a suggested timer you can adjust. Teammates join with a link and their name; no account needed.