A good working definition of “Done”

Posted on by Mike Burrows

Ever got into one of those discussions about what constitutes “done”, “done done”, or even “done DONE done done”? It’s done when it’s code complete? Tested? Deployed?

What you’re really discussing there is not the actual work, but the process and its policies. That’s not a bad thing to discuss (quite the contrary), but still it risks missing the point.

How about a definition of done that’s not about roles or activities (“code complete”, “tested”, etc)? Try this one for size:

How (if at all) does your process confirm to you that someone’s need was indeed met?

Update: How do you identify the need in the first place?

Agendashift-cover-thumb
Blog: Monthly roundups | Classic posts
Links: Home | Partner programme | Resources | Contact | Mike
Community: Slack | LinkedIn group | Twitter

One thought on “A good working definition of “Done””

  1. Pingback: Experiences on Building Empathy and Trust w/ Metrics – Lean Experiments

Leave a Reply

Fill in your details below or click an icon to log in:

Gravatar
WordPress.com Logo

You are commenting using your WordPress.com account. ( Log Out /  Change )

Google photo

You are commenting using your Google account. ( Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. ( Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. ( Log Out /  Change )

Cancel

Connecting to %s