Update: Since writing this post, I’ve become aware of two other descriptions of Affinity Estimating. Jukka Lindström posted his experiences on ScrumDevelopment, and Chris Sterling has written a great Step-by-step description.
Update: part 1, part 2, part 3 and part 4.
The last session that I’d like to report on is Lowell’s “Affinity Estimating.” Affinity Estimating is a technique many teams use to quickly and easily estimate (in Story Points) a large number of user stories. This is a great technique if you’re just starting a project and have a backlog that hasn’t been estimated yet.
Read the rest of this entry »
Filed under: Agile Software Development, Scrum, Training
Update: part 1, part 2, part 3 and part 4.
This is a continuation of my report from the Trainers gathering. In part 1 I gave an overview of some of the topics discussed and in part 2 I presented Boris’ Ball Point game. In this post I’d like to discuss anther exercise that was presented by Jens Østergaard . His exercise is designed to demonstrate the difficulties encountered when trying to interpret a written specification.
In this team-based exercise, each team is divided into “Developers” and “Spec-writers.” The “Developers” are separated from the “Spec-writers” and only allowed to communicate using written specifications. “Spec-writers” are then presented with a diagram that they need to communicate to the “Developers,” who, in turn, must interpret the written specifications and reproduce the diagram. The exercise is run twice with two different diagrams and a retrospective is held at the end of each run.
Read the rest of this entry »
Filed under: Agile Games, Agile Software Development, Scrum, Training
Update: part 1, part 2, part 3 and part 4.
In part 1 of my report on the Trainers Gathering I gave an gave a summary of the events that occurred. In this post I’d like to discuss one of the exercises that was discussed. Boris‘ Ball Point game is a fun and exciting way to explore process flow. The rules are quite simple and the more people you have, the more exiting it can be. We played with about 25 people, but it would be an excellent game for large groups up to approximately 50 people.
Read the rest of this entry »
Filed under: Agile Games, Agile Software Development, Scrum, Training
Recent Comments