Skip to main content

Scrum Course Program for 2010 in Switzerland

Together with my partners in DasScrumTeam, I have put together my public training program for 2010 in Switzerland.

The biggest difference you will note are:
  • All Jumpstarts are now Certified Scrum Master Trainings.  The focus remains on getting started with Scrum but we meet the CSM requirements, so why not?
  • The Product Owner Course is now always a certified course, and lasts 3 days instead of 2. There is too much information to do it justice in 2 days
  • I am now offering CSM Jumpstarts in Bern and Geneva
  • Next to Andreas Schliep, I am also co-training with Peter Beck. 
  • All courses start at 9.00am, so that it is easier to come in the morning from remote parts of Switzerland or abroad.
All courses are in German, except as noted. Here are the course dates:

Certified ScrumMaster/Jumpstart (description in English - Deutsch )
For Developers, Testers, ScrumMasters, Business Analysts, Managers and Teams who want a first taste of Scrum.
  • 28/29-Jan-10 – Bern (3 Spaces Left, earlybird pricing ends today)
  • 15/16-Mar-10 – Zurich
  • 15/16-Apr-10 – Geneva (in English, with South African Trainer Peter Hundermark)
  • 17/18-Jun-10 – Bern
  • 26/27-Aug-10 – Bern
  • 07/08-Oct-10 – Zurich
  • 11/12-Nov-10 – Bern
Earlybird (1 Month in Advance) Price CHF 1'800, Regular Price CHF 1'900.--

Certified ScrumMaster/Advanced (description in English - Deutsch )
For users who have worked with Scrum and want to deepen their understanding
  • 08/09-Apr-10 – Zurich
  • 15/16-Jul-10 – Zurich
  • 02/03-Dez-10 – Zurich
Earlybird (1 Month in Advance) Price CHF 2'000, Regular Price CHF 2'100.--

Certified Scrum Product Owner (description in English - Deutsch )
For Program Managers, Project Leaders, Business Analysts and others who want to know how to guide a Scrum Team to Sucess
  • 17..19-Mar-10 – Zurich
  • 30-Jun..2-Jul-10 – Zurich
  • 15..17-Sep-10 – Zurich
  • 27..29-Okt-10 – Zurich
  • 15..17-Dez-10 – Zurich
Earlybird (1 Month in Advance) Price CHF 2'800, Regular Price CHF 2'900.--

You can download the Overview or Register online.

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 …