Skip to main content

Changes to DasScrumTeam Course Program for the Fall

In a few days, we at DasScrumTeam will announce our Swiss course program for the fall. We are planning 4 courses in Zürich (including 2 CSPO's) and 3 in Bern (including 1 CSPO). My partners, Andreas Schliep, Peter Beck and I decided to take this opportunity to make some improvements to our course program.

Here is a summary of the changes:
  • Consistant naming of all courses. "Jumpstart" now refers to entry level Scrum courses, so we have:
    • Certified ScrumMaster/Jumpstart -- in Switzerland, this is our current practice; in Germany and Austria, these are new names.
    • Certified Scrum Product Owner/Jumpstart -- the Jumpstart name is now applied to CSPO courses as well.
  • There are no new dates for "CSM for Scrum Professionals." We plan to re-evaluate our advanced course concept in the context of new guidance from the certifying bodies.
  • Our CSM/Jumpstart course will become a 3 day course, like the CSPO. We made this change because our participants repeatedly asked for more time for questions, more in-depth handling of more topics and more time for lunch and coffee breaks. That certain certifying organizations seem to prefer 3 day courses confirmed our decision.
  • Starting in January, 2012, these changes will apply to our courses in Germany and Austria as well.
What do these changes mean for courses that have already been published? Nothing. Published courses remain exactly as they are. Only new courses courses will be announced as 3 day "/Jumpstart" courses. The dates, descriptions and prices of existing courses remain as they are.

The prices for CSM/Jumpstart and CSPO/Jumpstart in Switzerland will be CHF 2'700 (early booker) and 2'950 regular price. Compared to our current CSPO prices, the early-booker prices are reduced by CHF 100. There is not VAT on public courses in Switzerland.

In Germany and Austria, the corresponding prices are €1'900 and €2'100. Again, the early booker price have been lowered by €150 compared to the current CSPO prices. Prices exclude VAT.


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 …