M
Backlog refinement

Done. Done done. And then… 𝗗𝗢𝗡𝗘 done done.

Author

Bo

Date Published

kanbanboard

✅ Done. Done done. And then… 𝗗𝗢𝗡𝗘 done done.

Just because a user story is done, doesn’t mean it actually solved anything.

Some teams go a step further and say “done done” – meaning it’s been reviewed or demoed.
Cool. But is that enough?

What about DONE DONE DONE – when real users have used it and we know it made a difference?

Because done means:
😇 Code is written
😇 Tests are green
😇 It’s deployed

Done done means:
👏 Stakeholders clapped during the demo

But done done done?
That’s when a user actually used it… and we learned it solved their problem 🤩

Outcome > Output. Every time.

Maybe it’s time we extend our boards:
TO DO → DOING → DONE → DONE DONE → DONE DONE DONE

How do you know when you’re really done?