Skip to main content

Which Scrum Course?

I was asked recently two related questions about Scrum and my Scrum Courses:
  1. Which course should I take?
  2. How do I get my manager on board with Scrum?
These two questions are more related than they seem. I offer four open courses. Scrum Jumpstart, Practical Product Owner, Certified Scrum Master and Certified Scrum Product Owner (the latter two in cooperation with Certified Scrum Trainer Andreas Schliep).

The Scrum Jumpstart course is about getting people informed and excited about Scrum. It's the best way to get your feet wet with Scrum.

This is also the course to get your manager into Scrum. Take him or her with you, so that s/he can share your excitement and experience with Scrum. It's not just about theory, it's about doing Scrum and doing exercises and role plays which make the advantages of Scrum obvious and intuitive. Scrum is an agile management practice, so your manager should feel right at home.

Scrum Jumpstart is also the course to send your team to as they are getting ready to start working with Scrum. The course focuses on the practices you need to work in a Scrum project. No fancy stuff (well, maybe a little bit), but afterward they can really do Scrum and are motivated to try it out!

The Certified Scrum Master (for advanced users) is as the name implies, for mastering advanced topics. How do handle multiple distributed teams across time-zone and language barriers? Andreas Schliep and I co-teach the course to give you contrasting (and sometimes even contradicting) points of view. The contents is largely determined by the participants, so an optimal learning experience is achieved. And of course, if certification is important to you, you need this course.

The Practical Product Owner and Certified Scrum Product Owner Courses are for learning how plan and manage agile projects, deal with the Scrum Team, and act as the interface between the Scrum Team and Customers, Users, Steering Committees and other Stakeholders. In short: How to be good Product Owner. If you are a manager, product or program manager, consultant or product owner in a Scrum or agile environment, these courses are for you.

At open courses in Switzerland or Germany, I teach in German. (I am looking for partnerships to organize French courses in France and maybe Italian courses in Italy -- please contact me). In-house courses can be taught in English, German or French (and maybe Italian).

Ken Schwaber will come to Switzerland to teach a CSM Course in Zurich. Ken is co-inventor of Scrum and a driving force behind its adoption. A chance to learn and master Scrum, direct from the source.


Figured out which course is right for you? These links will take you to registration...


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 …

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…