Skip to main content

Scrum Course Retrospective: Team Training Rocks!

What do we do well Last Week I held two open courses on Scrum: Agile Project Management with Scrum and Scrum Sprint Zero. Both took place here in beautiful downtown Zurich, Switzerland. The participants learned about Scrum but they also learned about the potential that a team can unleash under the right conditions.

Ball Point Game

2nd Round  - The Group comes closer together Third round, new topologyLast Round, passes are more reliable
The ball point came was a fascinating example of how teams can self organize to improve themselves. The team must produce something with tennis balls (let's just call them points for the moment). After getting an explanation how to produce points, the group estimates how many they can achieve.

The first individual estimate was 8. The first group estimate as 24. They took bets on whether 24 could be exceeded. Their first run was 18. After 4 runs, they accomplished 67 and their best run was 75 - nearly 10 times the original estimate and 4 times the first run. How did they achieve this? Inspect and adapt, i.e. using the basics of Scrum.

Sprint Zero

Those who stayed for the second course experienced "Zero and One," a simulated a project start up with Scrum. Sprint Zero: getting an initial product backlog and getting ready to start, and Sprint One - producing the first increment of functionality.

During Sprint Zero, the group was trying to figure out how to work together: Who is the boss? What do we have to do?. By Sprint One, the group had come together as a team. They got into the grove and produced startling results. I just watched in amazement.

Participant's Reaction

The participants were very satisfied with the course. All participants felt they could recommend the course. 2/3rds or more gave the courses top note -- ":-)" -- for overall satisfaction. High points included the ball point game, the retrospective as introduction to the Scrum, the open discussion about real cases, and the practical exercises.

Next Courses

The true teacher learns from his students. The next Agile Project Management with Scrum course will focus on the team learning to work together as a team and with Scrum. So "Zero and One" will be moved into that course. The advanced planning topics will be taught in a separate course, Agile Planning and Estimating.

For your calendars:
  • Agile Project Management with Scrum - for early adopters and others who cannot take two whole days off. October 27 and 30, November 3 and 6, from 15.00 to 19.00
  • Agile Project Management with Scrum - for teams who want learn Scrum and unleash their inner potential, December 4 and 5, 2008, 8.30 to 17.00
  • Agile Estimating and Planning - planning and estimating agile projects, for IT consumers and suppliers. Decenmber 11, 2008, 8.30 to 17.00
All courses will be held in Zürich, Switzerland (Schweiz) and in German. Prices and registration info will follow shortly.

Last but not least

All the photos from the course can be found on flickr. The links that I promised the class will be posted later today as a comment.


I've heard positive things about the ball point game before... if you are looking for other great coaching games within agile, check this wiki out.

I saw a session with these guys at Agile 2008 and was impressed with what they are starting to pull together. Use and contribute!
Peter said…
Thanks. This reference is very useful. I like sound of the retrospective game and am looking forward to trying it out.

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …