Skip to main content

Scrum Breakfast in Zürich, April 2, 2008: From Scream to Scrum, A Customer Tells His Side of the Story.

Two months ago, Marcello Leonardi presented his experiences as Scrum Master of the White Label Classifieds project. This month, Patrick Weiss, customer and Product Owner for the same project (and others), will tell his side of the story at the Scrum Breakfast in Zürich.

Patrick Weiss is the Leader of eSolutions at Publiconnect and is responsible for the conception and development of booking tools (e.g. MyPubliconnect) and While Label Classified Market Portals (e.g. nzzexecutive.ch, publicjobs.ch, osthome.ch). Previously he was responsible for Product Management in Marketing at the Publicitas HQ and responsible for Advertising for various publications, including Coop-Presse, Baslerstab, etc. Presently he is working on completing the Omnium Global Executive MBA from the HSG and Rotman School of Management of the University of Toronto. As Product Owner (or "Chief Pig"), he has logged 30 Sprints over 1 1/2 years, corresponding to a total project volume of around 5 Million Swiss Francs.

Patrick's talk will focus on
  1. Introduction of Scrum in the WLC and MyP+ Projects
  2. Planing, developing and releasing of Publisherconnect v5.0
  3. Lessons learned
Date: 4 April 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 our sponsor namics provides the coffee, gipfeli (croissants) and orange juice. To register, just send me a private message or better register on xing.

The Scrum Breakfast is monthly exchange of information around Scrum. The breakfast offers discussion, information and hands-on experience to CIO's, executive and operational project managers. The program starts with a short presentation about on an in interesting topic around Scrum. Then follows a moderated discussion among the participants to encourage an exchange of know-how and experiences.

The Scrum Breakfast takes place the first Wednesday of each month. The doors open at 8am and the talk starts at 8.35 (so people coming by train can arrive at 8.30 and still catch the start of the talk). The presentations & discussion are usually in German.

Comments

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…

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…

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 …