Timing:
15 minutes
Ingredients:
- Copies of the twelve principles of agile software (http://agilemanifesto.org/principles.html)
- White-boards and/or flip-charts
- Markers
Recipe:
This is an exercise that we came up with to better communicate the twelve principles behind the Agile Manifesto. In their existing form, it is challenging for people to read and understand each principle and, just as importantly, to easily refer to them later.
- Divide participants in to groups, each with a white-board or flip-chart and markers.
- Have the teams write down the numbers 1 through 12.
- Challenge each team to, within a 15 minute time-box, come up with three words maximum that effectively capture each of the twelve principles.
- To avoid ‘analysis paralysis’, make sure to give the teams time updates throughout (e.g. 10, 5, 2, 1 minute warnings). You will find that teams will speed up towards the end.
- When time is up, go through each principle and discuss which are the most important words. Sometimes I like to ask people what their most and least favorite principles are.
- Post the condensed principles somewhere visible, so as to make it a regular talking point.
Here is an example:
- Produce Value Early
- Welcome Change
- Iterative Delivery
- Daily Business Collaboration
- Trust Motivated Team
- Face to Face
- Working Software
- Sustainable Pace
- Technical Excellence
- K.I.S.S.
- Self-Organize
- Reflect and Adjust
Learning Points:
- This is an effective way of capturing each principle in a much more concise and memorable way.
- Probably the most valuable part of this exercise, is in the discussion that the teams have when trying to come up with the words. They need to first understand the principle before breaking it down.
- Teams can establish a collective understanding and ownership of each principle.
- This also makes for a good review exercise in a classroom environment.
VN:F [1.9.13_1145]
Rating: 4.4/5 (9 votes cast)
Pocket-sized Principles, 4.4 out of 5 based on 9 ratings Written by: Don McGreal on January 24, 2010.
Last revised by: Heitor Filho on February 4, 2011.
Parabens!
Achei muito interessante e prático não só este post, mas todo site|blog!!
Fico contente em descobri um site assim que facilita e agiliza a nossa assimilassão do Agil.
)
Legal Verlon, ficamos contentes que voce gostou! Volte sempre!
I have used this game three times and I have found it to be very effective.
One challenge I find with it is consolidating the output from the multiple groups into a single list. I like having a single list as it is a simple, clear, artifact that can be left on the team wall.
What I have found works well it to create another list with the 12 numbers on it. Then I got a volunteer scribe, usually asking the person who had the neatest writing from the original groups. Then I gather the team around and have them come up with a ‘final’ pocket-sized principle. Usually, an informal dialog was sufficient for someone to suggest something and for the team to agree. Sometimes, I make suggestions and have used the decider protocol if things are moving too slowly.
This additional discussion provides another opportunity for the team to talk about the principle which is the most useful part. However, this add another 15 minutes or so for the activity.