Skip to main content

New: CSPO Courses in Zurich

I am pleased to once again offer a Certified Scrum Product Owner courses in Zurich.  (see my CSPO Course Description).

I have always been an entrepreneur at heart and the Product Owner role has always fascinated me. I have always been on the lookout for better ways to live role of the Product Owner. From Kanban, to Lean Leadership and Lean Startup to Radical Management: there are so many good approaches to help you be a better Product Owner (see for instance Scrum and 5 Principles of Radical Management).

I love teaching product ownership.

My other job is Product Owner and investor in the HappinessApp. So I am not just a coach or theoretician, I am living the role of Product Owner. This has been my best project and its been my worst project, and I will share the ups and downs of that product and others with you as you learn the values, principles, and tools of the trade of the Product Owner. (Check out our next product, the HappinessApp for Events).

In this two-day course you learn what you need to know to lead a Scrum Team effectively. You learn to the tools for creating great products and you meet the requirements for being a Certified Scrum Product Owner by the Scrum Alliance.

Like my Certified Scrum Master course in Zurich, attendence will be strictly limited to 10 people for an intense experience. Like my CSM course, it will normally be held in English unless everyone agrees to speak German (guaranteed German courses on request).

Want to register for the CSPO course? Jump to my registration page now!

Other Changes:
  • I have extended the class hours for all courses by 30 minutes a day. Classes now officially end at 18:00 (6pm) sharp. This is really a reflection of reality and enables members of the PMI to claim 15 PDUs instead of 14.  (See also the CSM Course Description)
  • Are you interested transforming your team or organization with Scrum or Radical Management? I have updated my directory of company Scrum trainings, workshops and executive retreats.

Happy New Year Everyone!

Comments

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…

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…

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 …