Acceptance Criteria

Demonstrate Them by Drawing a House

14 May 2014

Tom Reynolds
The Agile Mindset Ltd


Some while ago, while thinking of a quick and easy way to demonstrate the power of acceptance criteria, I devised this small activity that explains the concept. The activity is interactive and takes about 20 minutes to complete, including the discussion. All you need are some pens and paper and, for a little more dramatic effect, a flip chart -- but that is not essential.

If you want to explain acceptance criteria, then this activity gets across the concept very well in a simple, straightforward, and powerful way. I have run this activity in the U.K. numerous times, as well as in Switzerland, and it has worked in both locations successfully.

Let me explain how to run the activity. If you want to simply yet powerfully demonstrate acceptance criteria, try it out for yourself.

First, let me start with some background. When I was at school, all of my classmates were always sketching outline drawings of houses on paper or in their exercise books. So I decided to use a simple house drawing to explain the concept of acceptance criteria. In the U.K., most houses are of a similar style, and I expect that the style I draw is one you can use in many locations. If you don't feel this style will work for you, however, feel free to alter your house to a sketch of one that will work in your location.

I start the exercise by asking the group whether, when at school, they drew houses in their schoolbooks. When you pose this question people will generally nod their heads in agreement. Then simply say, "OK, take some paper and a pen and just sketch me out a house." Most people will now start to draw their house; some people will ask questions about what the house should be like, but simply say, "Just draw me a house."

While they are doing this, draw your own house on a piece of paper or a flip chart sheet, making sure that no one else can see it.

I draw my house like this:



When everyone has finished, walk around and see what they have drawn. No one will have drawn what you have done, so as you go around say things such as, "Nice house -- but not what I wanted," or "How very artistic -- but unfortunately not the house that I wanted." You can make this very lighthearted, but essentially reject all of the houses as not being the house you were looking for.

Once you have been around the room, tell everyone that you need them to write down what you are now about to say, and say the following:
  • There is a door on the lower floor in the middle of the house.
  • On each side of the door there is a window.
  • On the upper floor, there are three windows evenly spaced across the house.
  • The house has a pitched roof.
  • There is a chimney.
  • The house has a garage.
  • The house has a fence around a garden.
  • The fence has a gate.
  • There is a path from the door of the house to the gate.
  • The garden has a tree.
Now ask your group to draw the house again.

When they have finished, turn around your flip chart (I find the flip chart works well and there is an element of a magic trick when you turn it around and reveal your house), and then ask them whether their house looks like yours. You will find that they will all have drawn a house that's very similar, and in some instances it will be almost exactly the same. Now you can go around the room and check the houses and, where they have met your acceptance criteria, you can say, "Yes, I can accept that house; that is what I wanted." If someone has missed something, you can reject it and explain why. If people have drawn what you wanted but added to it, then discuss this as gold-plating of your requirement.

Sometimes before revealing my house, I throw in a reference to Derren Brown (TV magician, cold reader, and lots of other stuff), or throw in your own local magician who does similar things. I say, "Did I subliminally make you draw what I wanted? You do realize that I trained him." And then, of course, add, "I'm only joking. Maybe I simply got what I wanted by giving you a set of acceptance criteria."

We can now debrief on the activity. Explain that through using a set of ten specific bullet points and statements, I got exactly what I wanted. Ask whether you told them how to draw the house. The answer is no, so again restate, "I even got what I wanted without telling you how to do it." You may find some people draw the tree or garage or chimney on the opposite side to you, so explain that you don't actually care; in this instance what's important is that you have them -- it's not important exactly where they are.

You can also go on to explain that when using acceptance criteria with user stories and in the context of software development, you can use tools to automate these acceptance criteria as tests. Therefore you build up an automated regression test pack that will tell you whenever you deviate from the requirements. State the fact that the acceptance criteria are your requirements, and they just happen to be requirements that you can use to test your software and then to automate your tests.

You can now explain how you used the acceptance criteria to verify that you got what you wanted.

Now move the debrief onto how you can use the acceptance criteria to scope your story. Pose this question: "I have given you my acceptance criteria and have asked you how much it is to build my house. You tell me £1 million and I say, 'That is too much. I only have £900,000. What can I do to reduce the scope of the my house?'" The group will give you answers such as, "Remove the garage and the tree." You can now ask the question, "What could I do to increase scope of my house?" You will get answers such as, "Build a double garage," etc. You can also use this to discuss how you can change the scope of a story to take into account time. "How long it will take? I don't have that much time. What can I do to get it earlier?"

You can now make the point that not only are acceptance criteria your requirements that can be used for tests, and not only can they control the scope of your story, but they can also control the behavior that you expect to see (such as whether the garage should be to the right of the house).

Finally, you can ask the group the general question about how they feel about this. Do they find it powerful? Most people are amazed and surprised by the simplicity and the power of acceptance criteria.

So that is how I run the activity. I have run this many times with many people and have always found it to work well.

Why don't you give it a go, and let me know how you get on.


Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.



Article Rating

Current rating: 4.5 (6 ratings)

Comments

Jayaprakash Prabhakar, CSPO, 5/14/2014 12:20:02 PM
Nicely explained, Tom ! This explains
1. How important is to have a detailed AC
2. How can it bring communication between PO and the team

Thanks for sharing !
Raffaello Torraco, CSM,CSPO, 5/14/2014 3:30:17 PM
Thanks a lot Tom, I have already shared this on my linkedin :)
Gurpreet Singh, CSP,CSM, 5/14/2014 10:56:33 PM
amazing!
Chris Waggoner, CSP,CSM,CSPO, 5/14/2014 11:49:57 PM
Brilliant!
Matt Chocqueel-Mangan, CSM, 5/16/2014 4:03:09 AM
Fantastic. Such a simple exercise, but sounds really effective - thanks for sharing it Tom. Will be giving it a go with the teams here.
AMLENDU CHOUDHARY, CSM, 5/16/2014 7:57:50 AM
This is really nice way to explain team about acceptance criteria(Generally toughest part while defining user stories).
Zach Bonaker, CSP,CSM,CSPO, 5/16/2014 9:50:23 AM
This is a neat idea, but something isn't sitting well with me. The example "acceptance criteria", to me, feel a lot closer to IEEE830 requirements statements, rather than acceptance criteria from a user story conversation.

The house shall have a door on the lower floor in the middle of the house.
The upper floor shall have three windows evenly spaced across the house.
The house shall have a pitched roof.
Etc.

Perhaps, as the future resident of the house, you are aware of all these fine details. But what if you're not?

The first part of this exercise actually seemed more appropriate to me! Rather than get the entire house drawn to specifications the first time, allow some room for emergent design to take place! The observations users make on iterations are very powerful feedback loops... and the lightweight framework of acceptance criteria make it easy to get the customer's voice into a conversation.

I really like the idea of this example, but to me, this just felt a lot closer to an exercise in requirements specification! Perhaps using this method in more of an iterative fashion to build out the house in pieces, leveraging quick conversations around each section, would be an idea to try?
Daniel Lynn, CSM, 5/16/2014 10:30:50 AM
I've done this exercise a few years ago and it's great for it's purpose - it is a jarring exercise to show people their bias. I've been wondering if there's a way to get more out of it though. What if you did the same exercise a third time and instead of these acceptance criteria, you say:

- The user should not be woken up by the sun in the morning.
- The user should be able to welcome people to his home on his front porch.

and so on.

I honestly don't know how it'd go - I'll have to try it when I get a chance. I think what would happen is that you'd have a number of creative, different solutions that all solve the user's problems well, and that seems to be what we're looking for in Agile.
Colin Sweetman, CSP,CSM, 5/27/2014 6:23:55 AM
Nice simple exercise to illustrate the fundamentals. Thank you for sharing, Tom.

Col.

You must Login or Signup to comment.