Skip to main content

Scrum Breakfast in Zürich: March 5, 2008

The next Scrum Breakfast in Zurich is dedicated once again to a report on practical experience. We are fortunate to welcome one of the most experience Scrum Masters in Switzerland, Jiri Lundak, who will talk about

Scrum in the Public Sector: Practical Experiences

Two months ago a 4 year project development project came to a conclusion. Along the way, it transitioned from being a traditionally managed project to being a Scrum Project. His talk emphasizes the problems (and also the successes) of using Scrum in public sector projects.

Topics:

  • Hurdles a software company faces, when it decides to become agile
  • The challenge of staying agile
  • Lesson learned

Bio:

Jiri is the head of Software Development at Löwenfels Partner AG in Luzern. The company is specialized in developing software for the Swiss social security agencies.

With over 20 years of experience as a software engineer, architect, team leader and project leader, he has been working with agile software development since more than 9 years, emphasizing XP and Scrum. He became the second Scrum Master in Switzerland in 2004. Today he is working on transmitting his experiences in conferences, training courses and other event. He is working on a book, "Agile Processes - Recognizing and Avoiding Traps".


Date: 5 March 2008 (always the first Wednesday of the Month)
Time: Doors open at 8.00am, conclusion 10.00am.
The talk starts at 8.35 (so that you can come by train at 8.30 and still be on time).
Location: namics ag, Konradstrasse 12, CH-8005 Zürich

The talk will be held in German.

Attendance is free and, as always, namics is sponsoring the coffee, gipfeli (croissants) and orange juice. To register, just send me a private message or better register on xing.

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 …