Skip to main content

Scrum in a Management Consulting Context

When the topics is hot, people will come. And so it was for the first Scrum Breakfast in Zurich this year. 38 people came to learn and discuss the case of an early adopter of Scrum outside the Software context.

Michael Stump spent three months working with a consulting company -- that had nothing to do with software -- coaching them through a pilot project. On the face of it, consulting seems like a logical application for Scrum. By definition, consultants solve complex problems. Quality is important. And the problems are big enough that they can't be solved by one person alone.

On the other hand, internal competition is intense ("up or out"). Many practices around Scrum were established in a software context (user stories, potentially shippable product). So what does a backlog entry look like? What is the definition of done? How was the customer involved in the project. Many questions!

Michael presented his experiences introducing Scrum into this organization. Really interesting were the discussions around the definition of done, what impediments arose and how they handled them (for example team work and the trust culture vs. up-or-out), and the bottom line value doing Scrum.

What was the bottom line? Everyone had more fun on the job. The quality was substantially better. And the team was a factor of 3,4 more productive (although there was a lot of discussion about what this actually meant).


You can download Michael's presentation on the leanagilescrum.ch website. And Micheal is planning to repeat his talk at the Scrum Breakfast in Bern. Watch for it on the SwissICT Events page.

P.S. We started a new idea: Lean & Scrum for Newbies (dare we call them "Beginners?"). Mischa Ramseyer gave a 15 minute introduction into the practices and values for the benefit of the people coming for the first time. Probably a third to half of the participants shorted their morning coffee to listen in before the main program started. So we'll be repeating this in the future...

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…

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 …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…