Skip to main content


Showing posts from January, 2010

Cancel all your room reservations!

If there is one thing common to every big company I have ever coached, it is the lack of available meeting rooms. Getting people together is hard enough. Getting a meeting room is impossible!

This does not mean there aren't meeting rooms in the company. Just that most have them have been booked in repeating weekly, bi-weekly or monthly events.

So just setting up a retrospective or other similar event can be a major challenge. Last time I did it, the group assistant spent a few hours finding me a room.

I have a modest proposal: Let's make February 1st, 'Cancel all your room reservations' day! Cancel all your recurring meetings, free the rooms (and your calendar). Then on Tuesday, schedule only those meetings that you really need (who really needs these meetings in the first place?) and no more than 3 recurring events on a single appointment.

Is this a realistic suggestion? Of course not! Is the scarcity of meeting rooms trying to tell you something? Absolutely! You are …

Scrum Breakfast im February: Agile Governance

Once again, we are fortunate to welcome an international speaker to Zurich for the Scrum Breakfast. Pierre NEIS is a Sr. Management Consultant who is active in the Finance industry in and around Luxembourg. His topic:

Adoption of an Agile Governance Model

As a corporate leader, program or business manager, or line manager, you want your IT and Development activities to be aligned with your business. As more and more companies are doing Scrum, you are thinking about the implications of Scrum on your organization. Scrum promises better business alignment, higher employee productivity and satisfaction, and ultimately better profitability, but seems chaotic and uncontrolled. How do you implement Scrum in your company? How do you keep things under control?

This talk is for corporate leaders contemplating Scrum and anyone who wants to talk to them about the how and why of Scrum in medium and large companies. Pierre E. Neis will discuss the challenges facing companies adopting Scrum and disc…

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 daysI am now offering CSM Jumpstarts in Bern and GenevaNext 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)

Scrum in 100 Words or Less

[Update 9-Jan-10: See Comment 3 for a revised formulation of Scrum in 100 Words.]

If Scrum is so simple, why is it so hard to describe? Tobias Mayer recently launched the idea of Simple Scrum - Scrum reduced to its essence. I think the essence Scrum can be defined even more concisely - in 100 words or less. 100 words, which will be understood by the novice, without using the Scrum lingo -- Product Owner, ScrumMaster and other such words are not allowed.

The Essence of Scrum in 100 Words:

Scrum is an empirical management process for addressing complex problems that ensures effective communication between a Requester and an implementation Squad. The Requester represents the interests of all stakeholders. The self-organizing, interdisciplinary Squad produces finished outcomes at regular intervals in response to prioritized requests. They measure their progress in terms of finished outcomes.

The maximum interval is 30 days. After each interval, the Squad has produced an improved product …

Why are Scrum Teams better motivated?

At first blush, it seems that Scrum is based on radical concepts: Self-organization, incremental delivery, and a clear distinction between what and how and equally clear definitions of who is responsible for what.

Why is this a better approach for developing software? It turns out, there are three key success factors to solving complex problems: Autonomy, Mastery and Purpose. Too much focus on success can be counter-productive. This video from Dan Pink explains why (BTW - you can turn on German subtitles - well translated!):

I think this video also hints at one role of management in Scrum culture: creating an environment where people can be creative, problems can be solved and new ideas can bear fruit. Google's 20% or Atlassian's 'Fedex Days' don't arise out of a Sprint Contract, they arise out a management with a vision of a company becoming more competitive through the creativity of their staff. How motivated and creative are your staff?