Exercise:: Definition of Done

This content is syndicated from Agile Complexification Inverter by David Koontz. To view the original post in full, click here.

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?

Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, then you have a great point to have a team discussion. Better at the beginning of the project, rather than right before the boss says 'ship it'. If you are having this dialogue (more than a debate/discussion - everyone is explaining their assumptions and exposing their values underlying their position in dialogue) then your team has entered the 2nd stage of team formation (Forming, Storming, Norming, Preforming) - congratulations! Now there is the second reason to create a definition of done - it moves the team along the continuum of strangers to team-mates.

One team's Definition of Done. 
Note the items on the border between
Now and Next - tacit information.
So rather than using someone else's list you want to create your own. Yes, sometimes you need a little water to prime the pump. Or you could get the energy flowing in the meeting with an exercise to get people out of their seats (you increase blood flow to the brain by 20% just by standing up) at the white board and interacting with each other. Try drawing a target (very large) - 3 concentric circles (or rectangles) on the board, label the inner most 'Now', the outer 'Later' and the middle 'Next'. That is a form of prioritization (now - > next - > later) that you want your team to become very familiar with (we use it in backlog ordering - right?). Then place stickies or index cards on the table and have someone write just one aspect of the definition of done on a card/sticky, then place it on the board in the proper location. Take turns, the next person may either - move the card to a 'better' location (now, next, later) or create a new card and post it. Play continues until we exhaust the fun in the game, or get good enough. You might want to dialogue on the aspect of growing your definition of done over time. One could easily imagine that done means something different in sprint one than it does for sprint 73 after four releases and lots of customer feedback, now that you have continuous deployment working.

If you want some cheater index cards then use mine - they are no better than anyone else's answer to a team question, but these might get a reluctant team up and interacting in the game of collaboration.

  Definition of Done Exercise.pdf
  Definition of Ready Exercise.pdf
  Facilitator's Guide to Exercises.pdf
    by David Koontz

Not obvious in the example above is that the team used the items in the Next category to affinity group them by type, this was a spontaneous behavior of one of the team members.  It was a natural thing to do with visible information - it organized the display - and then we dot-voted to decide which items were the most important to work toward moving into the Now category of the Definition of Done.  Those items were then moved to the top area and circled to draw attention to them.  Then they worked on their understanding of the Definition of Ready - what do they believe the story must have to be ready for sprint planning.

Comparing these two charts - what would you say about this team's ability to plan?  What team member needs help?

See Also:

What is the Definition of Done in Agile? - by Dhaval Panchal

What are the Principles?

What do we do to truly support those 12 Agile Principles?  We mapped our engineering practices to see if we were Agile.

Leave a Reply

What is 1 + 3 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”