Skip to main content

Scrum Course Review

Last year I had the privilege of training 91 people in Scrum and Agile Project Management. Two in-house courses and five public courses, including a Certified Scrum Master course together with Andreas Schliep.
After every course, I ask the participants for feedback. And I am happy to report that the overall impression is on the average between 4.2 and 4.7 on a 1-to-5 scale. (In fact, if someone gives me a 3, I try to find out why!). 

What do people like about my courses? Some high points from the CSM Course:
  • Gripping case studies
  • Tennis ball games ('ball point game')
  • Important questions got answered
  • Brownies
  • Scrum as the organizing principle of the course
  • Dialogue between Scrum Trainers Peter & Andreas
And from the Scrum Jumpstart courses:
  • Sprint Zero & One
  • Ball point game
  • Retrospective as introduction to the Scrum
  • Open discussion about real cases
  • Practical exercises
But the most important part are the suggestions for improvement. And after every course, I try to address as many of the potential improvements as possible.

Some suggestions from the last courses which will be implemented by the next course:
  • Better training rooms - in 2009 the open courses should be held at Digicomp.
  • Support networking between participants - for those who want to exchange contacts with other participants
  • A Beginners Scrum Course (Scrum Jump Start) and an Advanced (Certification) Scrum Course - this was always the case, but now the descriptions, audience and prerequisites are clearer.
  • A Product Owner's Scrum Course - for Planning and Managing Agile Projects. The Product Owner has the hardest job in Scrum. I had to postpone this till February, but the first one will be held next month.
Thank you to all the participants last year. The program for 1Q 2009 Scrum Courses is now online. I look forward to seeing you again, either in a course or at a future Scrum Breakfast!


Popular posts from this blog

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…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…