33058RE: [scrumdevelopment] Intro to Agile / XP / Scrum game that takes 15-20 minutes?
- Oct 4 3:56 AM
Liked the “bonus round” concept, but I did it a little bit different. Instead of suggesting an arbitrary speed, I just changed one of the rules when the team reached stability and predictability. For example, in the first Sprint, the team estimated 50 ball points, but really did only 35. After a few sprints, the team got better knowledge of its capacity, started to make more accurate estimates and reached a point of stability – like estimating 65 points and deliverying 67 to 70 points. So I changed one of the rules, for example, in the last Sprint I would allow the team to hand the ball to the person standing directly next to them. After that, the team usually performs way better than they used to perform (because it makes the game easier).
The point here is to show that once a team gets stability, the only way to make them speed it up is to change the rules of the system. Just another way to do “bonus rounding” ;-)
Yesterday I applied the game you suggested with one of my teams, which is new to Scrum and still a little bit reticent about estimating in story points. I asked about the sanake bites, shark species, and a few more other numbers I looked up on the web, and the result was great – everybody felt that estimating using relative sizes is way more interesting, raises more questions and generates more interaction. And in the end, it’s quicker. I believe that from now on, this team will be less resistent to change. Great game, thanks for your contribution!
Love both of these games, have used the ball point game successfully myself but really like the bonus round concept so I will extend my ball point game to include this and I will also look at incorporating the story points game into by tool kit.
Another game I have used successfully I call the knot game but it is also referred to as spaghetti. (Thanks to Tobias Mayer for teaching it to me). This game basically takes you through how much better it is for a team to be self managing and to work things out for themselves as opposed to being micro managed or trying to write down all requirements up front aka waterfall.
I have a diagram that explains the game. If anyone is interested then let me know and I can forward it.
- << Previous post in topic