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.

Comments

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...

Agile Bert joins the world of blog.

My far more technical compadre and fellow Agile Yorkshire attendee 'Agile Bert' (aka John) has joined the blogging world. Will he become a prolific blogger? Will he become a (thought) leader amongst men? Why is he called Bert? That last one actually has an answer: here

Smash the echo chamber

Who doesn't enjoy the warm glow of validation that comes from having others strongly agree with their opinions? It's a great feeling; it's encouraging,  and a gentle massage to our self-confidence. Without this experience, all but the most arrogant of us would soon be wracked with self-doubt, so it's certainly not a bad thing. But... everything in moderation! At time-of-writing I'm in the position of having a team who are incredibly comfortable in voicing their opinion.  Whether they're just brutal or a little further along the spectrum than the average developer I can't be certain, but I do know I can rely on hearing their opinions. Not a great environment if you're sensitive, but it does force me to challenge my views, thoughts, and actions on a regular basis.  And on the assumption that I'm not always correct, which my wife assures me is the case, that's a great thing! Why? Because living inside your comfort zone 24/7 can only re...