Skip to main content

October Scrum Breakfast in Zürich: Projects Unsuitable for Agile?

The October Scrum Breakfast will once again address the theme of Scrum in the real world, this time examining the conflict between traditional "plan driven" and agile process models. A list of the topics:
  • Are there projects for which traditional plan driven process models are more appropriate, or where agile methods cannot effectively be applied?
  • What are the differences and commonalities between agile and plan driven processes?
  • Is it possible to combine the two into a 'best of both worlds' approach?
Daniel Tobler is a Software Architect at Zühlke Engineering AG. Through his daily work, he comes in contact with software projects for many different companies, which use different various process models. His work focuses mostly on interdiciplinary projects, which include hardware, software and mechanical engineering. He has been using Scrum (or elements of Scrum since 2002).

Daniel Tobler developed the latest Zühlke-Poster (SW Processes Today), which is the basis for the talk. He also teaches Object Oriented Design and Agile Software Development for the Master of Advanced Studies Program.

His talk will not mince words, so we should have an intense discussion after the talk. As usual, namics will sponsor the coffee, croissants and orange juice!

Date: 1 Octobber 2008
Time: Doors Open at 8:00, Talk from 8.35 to around 9.15. Forma Discusssion finished at 1:.00
Place: namics zürich, konradstrass 12/14, 8005 zürich, switzerland (schweiz)
2 Minutes Walk from Zürich HB, Near Tram Stop Sihlquai/HB

Registration:
This talk will be given in German!

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 …