Skip to main content

Switzerland Lean and Scrum Course Program 2011

At long last, I am pleased to announce our course plan for the first half of 2011 in Switzerland:

As in 2010, Peter Beck, Andreas Schliep and I will offer a regular program of practical Certified Scrum Trainings in Switzerland: CSM/Jumpstarts in Zürich and Bern, CSPO in Zürich and advanced courses for experienced ScrumMasters to sharpen their understanding of Scrum:
  1. CSM/Advanced is now called CSM for Scrum Professionals and lasts three days instead of two. We found two days was not enough to review the basics and explore advanced topics. It also reflects the emerging guidelines for the new CSP1/CSP2 certifications. So there is a new description and of course a new price.
  2. We are proud to announce a new course: Team Leadership Skills for Scrum Professionals  -- a course for left-brained professionals on using their right brain to lead their teams to success -- led by Peter Beck and Dr. Siegfried Kaltenecker. July 7 & 8. 
  3. Tom & Mary Poppendieck will return for a Lean Leadership Course in May in Switzerland. Register here by December 31 for a special super early bird price (CHF 2'240 instead of 2'800.--).
  4. Courses in Zurich will be held at Business Solution Group AG, Buckhauserstrasse 24, 8048 Zurich. Courses in Bern will continue to be held at Digicomp Academy.
  5. Our prices are basically unchanged. The difference between early booker and regular price has been harmonized between our EU and Swiss courses - the difference is now 150CHF ( ~= €100.--). The early booker prices are unchanged.
  6. All courses in 2011 are organized by DasScrumTeam GmbH. The new AGBs are located on our home page.
After the Amsterdam Scrum Gathering, I was fortunate to participate in the workshop 'Training from the Back of the Room' with Sharon Bowman. This is to training courses what Agile is to software development. All I can is 'Wow!' You'll notice the difference from the first minute.

The first public course to profit from this experience with be this week's CSM/Advanced. There are still 4 spaces left (BTW - the CSPO is sold out). Register here.

For more information:


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…

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 …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…