Skip to main content

Definition of Done - An example

Done?

To call a story 'Done-Done' we should refer to two things:
the acceptance criteria for each story
the team’s Definition of Done

The DoD is defined by the team and should be updated whenever it seems appropriate e.g if there's a big change in the team or the work; or the team simply sees the need for a change.

If you have project based teams, it's something to agree before timebox 1 kicks off. If you're more product based and continuously working through an ever growing backlog, slot it into a timebox kick-off, a retro (if that's where it was discussed) or just grab 10 minutes after the daily stand-up.

An Example:

Here's a basic example created by a team I was working with:

----------------------------------------------------------
A. Dev done
---- Code review done
---- Unit Tests written and passing
---- Integration tests written and passing
B. Test complete
---- Manual Testing complete – Acceptance Met
---- Automation Tests written and passing
C. Business Signed off
---- Business/Product owner confirm Acceptance met
D. Passed at least one regression test
E. Documented
----------------------------------------------------------
This DoD worked for this team, but wouldn't work everywhere.
Some teams may not be able to have their integration and acceptance testing in the DoD due to the way their platform is set up or issues with their environment configuration.

So:

DoD is a proven technique that drives quality for relatively little effort, but how you implement it should not be matter of dogma.
Be pragmatic and find what works for you.
And when it's done get it up on the wall in plain sight - DO NOT allow it to languish unloved on a shared drive.
Labels:

Comments

Post a Comment

Popular posts from this blog

Continuous (Self) Improvement

“Everyone thinks of changing the world, but no one thinks of changing himself.” - Leo Tolstoy Introduction: Most people talk a great game about continuous improvement.  And as a group, most of us truly agree with and see the benefits of, the concept as applied to our projects and teams. Sprint Retrospectives, Post Implementation Reviews, 5S, DMAIC, PDSA (not the dog people) and so on. But... Do you practice it personally ?  I don't mean training courses, formal development plans and all the other bureaucracy that people step through stoically every year in a bid to get a pay rise.  I'm referring to the small (but meaningful) improvements we can make every day. Or to work in an Agile principle: "At regular intervals, the team (of one in this case) reflects on how  to become more effective, then tunes and adjusts  its behavior accordingly." Step 1: Feedback (aka input to the CI process): Of course, all improvements need to be identified i...
Post a Comment
Read more

"We are Agile!"

A phrase Project Managers hear a lot, and one that occasionally proves to be at least partly true. As it's most often spoken rather than written, it is hard to know whether the speaker means 'agile' or 'Agile'.  I find that asking the question ('big A' Agile or 'small a' agile?) can reveal a lot about that person's knowledge of the 'Agile' world.  If you find yourself asking the people around you this question and you receive blank faces or confused responses you can be fairly certain you haven't landed in a particularly Agile organisation, rather you're somewhere that has rolled out a buzzword in the hope of improving speed of delivery. Organisations tend to fall into one of the following categories: - Comfortably Waterfall - Fine . This organisation knows how it wants to work and perhaps has reasons why they prefer to keep projects waterfall. - Waterfall but concerned they need to get on the Agile bandwagon - Confused ....
Post a Comment
Read more