Skip to main content

Scrum Breakfast Zurich:

Four years ago, I started the Scrum Breakfast in Zurich. As my tenure as moderator of the Scrum draws to a (temporary) close, I thought it would be interesting to have some presentations about the longer term effects of Scrum, so both the November and December Breakfasts will look at this topic in more depth.

Ernst Basler and Partner is known for their work in Infrastructure and Transportation Systems, Energy + Technology, Environment + Water, Resources and Climate Change. The Swiss Federal Office of Roads (ASTRA) contracted with them to develop the MISTRA Base System - a database of virtually all relevant data around roads and road building in Switzerland.

Last Christmas, EBP and the ASTRA decided to use Scrum to organize this project. The project had already been started. The requirements were extensive, complex and in many cases still under discussion, and the time was short. Scrum should help them master this situation.

Today the project has been running under Scrum for about 10 months. Nicole Stahel, Co-Manager of the Department „Informatik im Verkehrswesen“ will discuss the challenges, their solutions, and the longer term effects of switching to Scrum.

Registration and Info

Event: Scrum Breakfast in Zurich
Title: Scrum - an Experience Report after 10 Months of Experience
When: November 2, 2011, 8 am to 11am
Where: SwissICT, Vulkanstrasse 120, 8037 Zurich
Language: German
Registration and more Info: SwissICT

Reserve the Next Date / Going Away Toast

The Scrum Breakfast in December features Gerhard Andrey, co-Founder of Liip, a company where Scrum has truly entered the DNA at all levels. Liip was also my first external Scrum coaching / training assignment, so I am looking forward to this truly long term perspective.

As my sabbatical in the USA starts in January, this will also be my last Scrum Breakfast in Zurich for a while. I plan to bring some bubbly to open during networking part after the talk.

Mark the Date! December 7, 8am to 11am. (We should have the registration form online in a few days).

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 …