Skip to main content

Lean Agile Scrum Conference in Zürich - June 4, 2009

After saying, 'mark you calendars, mark your calendars' for what seems like an eternity, we now have pleasure of announcing the first Lean Agile Scrum Conference in Zürich.

Lean, Agile and Scrum: 3 words which have been the subject of much hype of late. As storm clouds gather on the horizon, companies look for strategies to meet the challenge. Lean, Agile and Scrum hold the promise of creating better products, lower costs, quicker reactions to customer needs, and better predictability in software development. Or are they just this years hype? And if these strategies do offer real value, how do you adopt them into your company? What are the risks and side effects? Who has gone down this path before and what were their experiences, positive and negative?

Under the motto of "Beyond Hype: Agile in der Praxis" Zürichs first Lean Agile Scrum conference seeks to answer these questions.

Ken Schwaber, the co-creator of Scrum will speak about the state of Scrum and lead an advanced workshop on getting the most out of Scrum.

3 tutorials and two advanced workshops for management and software engineers introduce you to and develop your understanding of the concepts and practices from all facets of the Lean/Agile approach to software development.

Experienced practitioners and experts from Switzerland and abroad will present their experience with Agile adoption in their companies and discuss the management challenges of adopting and achieving a Lean-Agile state within your company.

08.00 - 08.30 
08.30 - 10.00 Scrum Breakfast
(will be held exectionally at the ETH), free admission as always)
10.30 - 12.00 
12.00 - 13.00 
13.00 - 14.00 
14.00 - 16.45 
Experience Reports, Talks and
Ken Schwaber's Scrum-But Workshop (limited places)
17.00 - 17.30 

And at the end of the day, a podium of experts will answer your remaining questions. You will go home having gained an understanding of what Lean, Agile and Scrum can do for your and your company, shared experiences with peers and colleagues who have or are planning a similar strategy, and gained an appreciation challenges and obstacles you will face and how you can overcome those problems..

Date: June 4, 2009, 8.00 to 17.30
Location: ETH Zürich, Gloriastrasse 35, 8006 Zürich (Building ETZ)
Detailed Program: Online
Cost: 80 to 550 CHF, depending ...
Info and registration: SwissICT

BTW - Conference participants are entitled to a 10% discount to Ken Schwabers Certified Scrum Master Course on June 2 and 3. Register now! - places are limited.


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 …

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…