Skip to main content

Exercise:: Definition of Ready & Done

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 Ready Description.pdf
Definition of Ready Exercise Cards.pdf
Definition of Done Exercise Cards.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?



In Feb of 2018 I participated in the Scrum Alliance's Webinar:
Collaboration at Scale: Defining Done, Ready, and NO for Distributed Teams. Presentation PDF

In the process of getting ready for that presentation I created a version of this exercise on the Weave® platform.  You can play a slightly different version online with your distributed team -  in an instant with Weave - Definition of Done and Weave - Definition of Ready

Weave: Instant Play game of Defn of Done 

See Also:

An interesting article on DoD.  "The Definition of Done mismanages risks by delaying contact with end users." Redefining Done It list 7 problems with the typical definition of done:
The Definition of Done is more interested in:
  • Software creators (product owners, developers, etc.) rather than software users.
  • Gaining acceptance internally (e.g. from product owners) rather than from end users.
  • Demonstrating working software rather than producing user results in production.
  • Integrating into a build rather than releasing to production.
  • Tracking done work rather than discovering user needs.
  • Improving the process (e.g. increasing story throughput) rather than improving the product.
  • Doing rather than learning.

Definition of Done vs. User Stories vs. Acceptance Criteria by Mark Levison of Agile Pain Relief a consultant with lot's of wise content and great practices to teach.

What is the Definition of Done in Agile? by SolutionsIQ. A great overview of the purpose and need of the DoD
An AgileGames 2013 Winner: Designing a Definition of DONE & READY

Jeff Sutherland's blog:  Ready: The Dynamic Model of Scrum

DFW-Scrum user's group Meet-Up at Sabre ( May 2012) used this exercise to hold a discussion of the 'Definition of Ready'.  Note: we used a variant of the exercise described here, designed of a general group, not a team - it worked very well.

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

George Dinwiddie's Definiton of Ready blog and InfoQ video Three Amigos (Business, Programmers, and Testers)

A checklist for Definition of Done by Luis Goncalves

Agile Definition of Done Starter Kit by Mario Moreira

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.


Comments

Kym Phillpotts said…
Great write up David. Completely agree that DONE is one of those things the team needs to have absolute buy-in for. These is a really nicely structured exercise for achieving this.
Yes, Kym it is a wonderful exercise for allowing teams to have the time to discuss and come to a shared understanding of their definition of done. Having used these card decks multiple times it never ceses to amaze me how two people can read the same phrase on an index card and put that card in completely different groupings. Meaning that they conceptualize the meaning of the words very differently. This exercise brings these various divergent mental models of reality to light. Then we have the opportunity to have a useful dialogue about the meaning of just one little aspect of the definition that is understood by various people in different ways. Typically, I find that the understand that results is much stronger, deeper, and richer for the team members.

We, can do this for managers, leaders and stakeholders also.
Amy Lightholder said…
Hi David! I would like to use this exercise with my team on Monday, but it looks like your cards/guideline PDF links have died. Can you post new ones?
derekwwade said…
This is built out of awesome. Reminds me a bit of the Affinity Definition Game (http://derekwwade.net/blog/2006/04/16/the-affinity-definition-game/) It's interesting how important it is for us to have a shared understanding of what our symbols (e.g. "done") mean, but how UNimportant it is for us to actually hammer out a formal definition.
Anonymous said…
David,

Hello friend, long time no see. What a great exercise! I am SO going to use this with my next team!

Have you thought about submitting this game/exercise to tastycupcakes.org ?

Charles Bradley
Professional Scrum Trainer and Coach
http://www.ScrumCrazy.com

Most Popular on Agile Complexification Inverter

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Do You Put “CSM” After Your Name?

I’ve noticed a new trend—people have been gaining titles. When I was younger, only doctors had initials (like MD) after their names. I always figured that was because society held doctors, and sometime priests (OFM) in such high regard that we wanted to point out their higher learning. I hope it was to encourage others to apply themselves in school and become doctors also. Could it have been boastful?

The Wikipedia describes these “post-nominal initials”:
Post-nominal letters, also called post-nominal initials, are letters placed after the name of a person to indicate that the individual holds a position, educational degree, accreditation, office, or honor. An individual may use several different sets of post-nominal letters. The order in which these are listed after a name is based on the order of precedence and category of the order. That’s good enough for me.
So I ask you: is the use of CSM or CSP an appropriate use of post-nominal initials?
If your not an agilista, you may wonder …

Situational Leadership II Model & Theory

Have you ever been in a situation where you thought the technique needed to move forward was one thing, yet the person leading (your leader) assumed something else was what was needed?  Did you feel misaligned, unheard, marginalized?  Would you believe that 54% of all leaders only use ONE style of leadership - regardless of the situation?  Does that one style of leading work well for the many levels of development we see on a team?

Perhaps your team should investigate one of the most widely used leadership models in the world ("used to train over 5 million managers in the world’s most respected organizations").  And it's not just for the leaders.  The training is most effective when everyone receives the training and uses the model.  The use of a ubiquitous language on your team is a collaboration accelerator.  When everyone is using the same mental model, speaking the same vernacular hours of frustration and discussion may be curtailed, and alignment achieved, outcomes …

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…