Skip to main content

Impressions - Lean Agile Scrum Conference in Zürich

It really happened! 140 people from the USA, Europe and mostly from Switzerland got together to learn and share information about all facets of lean and agile. When I started talking about Scrum in the fall of 2006, I was pretty alone.

Low Points
  • Confusion about the starting time - We planned a block of 2 hours for the Scrum Breakfast, starting at 8. The talk was planned to begin at 8.35  But the block "Registration and Coffee" didn't make it on to the program the way it should have. Mea Culpa!
  • Speaker changes - we had a couple of last minute changes in the program - "excitement" for the organizers, potential disappointment for the participants. But people stepped up to fill the gap with great, well recieved presentations.
  • Delay on one of the tracks caused timing problems.
High Points:
  • Ken Schwaber - I had the priveledge of attending and co-teaching at Ken's CSM Course. Very different from every other Scrum Course I have attended. The emphasis on ethics, honesty and professionalism. Simplicity and elegance. 20 years of doing Scrum really makes a
  • Zurich is the birthplace of Extreme Programming(!). Joseph Pelrine told us stories of his brainstorming with Kent Beck about why XP worked at Chrysler but not here.
  • Self Organization - not just talking about it, but seeing it in action. Beautiful to watch!
  • Good talks, differing opinions
  • Lean, Agile & Scrum belong together. Scrum and XP really are fusing.  I have always believed strongly in a ying/yang relationship between Scrum and XP: agile management is a pre-requisite for agile engineering. Once you have agile management, you have to have agile engineering. Without agile managment, agile engineers beat their heads against lethargic walls.
Special thanks to:
  • Anton Schultschick, Head of the ISG Group at the ETH, who made the venue possible
  • Manuela Weber, Carol Lechner and Ruth Zimmerli - for the smoothest organization I have ever experienced. Food, registration, room preparation, marking the signs
  • François Bachmann and Mark Hediger for stepping up at the last minute to give interesting and well received talks.
  • Hans-Peter Korn for publicizing the event on all the community channels
  • Patrick Baumgartner for bringing us on to twitter.
If you publish any photos on flickr, remember to tag them laszh - I am starting to upload as we speak...


Anonymous said…
Karl Scotland hat gesagt er werde die Slides zum Kanban/Lean-Vortrag auf der Konferenz Website veröffentlichen.
Ist das schon geschehen?
Peter said…
No, it has not yet happened and yes, they will be posted shortly.

I am still missing a presentation or two, but we will put them up on the SwissICT website ASAP.

I will post the link here.
Peter said…
Wie im separatem Artikel angekündigt, sind die Präsis jetzt bei der SwissICT zu holen.

Karl Scotlands's Präsi ist zZt nur noch auf seinem Homepage zu finden.

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 …