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!


Comments

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 …