A Done Checklist defines shared quality standards for moving flight items between columns, evolving as the team learns.
"Done" means different things to different people. Until it doesn't.
An explicit checklist that defines when a flight item may move to the next column — creating shared quality standards that evolve as the team learns.
The Problem
One person considers a feature done when the code is merged. Another when it's tested. Another when it's deployed. Another when documentation is written. Without explicit agreement, "Done" is subjective — and quality is whatever someone happens to check on a given day.
How It Works
For each transition between columns, a Done Checklist is created. An item may only move to the next column when all criteria are met. Each column transition can have its own checklist with different criteria. Crucially, the checklists are not fixed rules — they evolve as the team learns. The best checklists get shorter over time as teams improve, because fewer things need to be checked explicitly.
When to Use It
- A shared understanding of quality is missing
- "Done" triggers frequent disagreements or implicit rework
- You want to create standards that remain open to improvement
Related Patterns
- Swimlanes for Flight Items — done criteria may differ per swimlane depending on the flight item type
Your play!
Get the cards and maps — all 18 FL2 Flow Patterns plus the new "Identify your Flow" companion map (A3 + A2 in EN, A3 in DE), ready to use in your next FL2 workshop or board design session.