Easy way to explain the power of acceptance criteria, Small activity that
explains the concept. The activity is interactive and takes about 30 minutes max to complete, including the discussion. All we need are some
pens and paper and, for a little more individual effect.
Let's run the activity:
First of all, let me start with child hood activity, generally we were doing at school. Drawing the mango or table or book pics. I decided to use a simple book pic to explain the concept of acceptance criteria.
The simple and easy, exercise we are go to do that: "Just draw me a book". When you pose this question people will generally nod their heads in agreement. Then simply say, "OK, take some paper and a pen (color) and just sketch me out a book." All most all, people will start drawing there book; some people will ask questions about what the book should be like, but simply say, "Just draw me a book."
Team are doing, In min while draw your own book on a pice of pager or a board, which is not at all visible to other.
My book look like below:
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, "Good to see nice book draw by xyz-- but not what I wanted". The simplest way to rejecting the all drawn book by all.
Now every one will definitely, asked question, what you are looking for:
Finally, you can ask the team 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.
Final Words!
Thanks! Why don't you give it a go, and let me know how you get on. Hopping you have enjoyed reading acceptance criteria, agile, scrum.
Happy learning and implementation.
Let's run the activity:
First of all, let me start with child hood activity, generally we were doing at school. Drawing the mango or table or book pics. I decided to use a simple book pic to explain the concept of acceptance criteria.
The simple and easy, exercise we are go to do that: "Just draw me a book". When you pose this question people will generally nod their heads in agreement. Then simply say, "OK, take some paper and a pen (color) and just sketch me out a book." All most all, people will start drawing there book; some people will ask questions about what the book should be like, but simply say, "Just draw me a book."
Team are doing, In min while draw your own book on a pice of pager or a board, which is not at all visible to other.
My book look like below:
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, "Good to see nice book draw by xyz-- but not what I wanted". The simplest way to rejecting the all drawn book by all.
Now every one will definitely, asked question, what you are looking for:
- There is a open book.
- First page have details, drawn two horizontal line.
- Second page have details about C inside O.
- Book is drown by black pan with white background.
After these requirement, if you asked team to draw, they they will draw, What you have drown like similar, with minimal gape.
With help of above, we need to draw and validate accordingly. If there is any change in requirement simple, ask the time and budget. If permit to do that start redrawing the book.
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 table or self should be for placeholder).
Finally, you can ask the team 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.
Final Words!
Thanks! Why don't you give it a go, and let me know how you get on. Hopping you have enjoyed reading acceptance criteria, agile, scrum.
Happy learning and implementation.
Nice!
ReplyDelete