Skip to main content

What's your frozen coke bottle?

A recurring problem of Agile projects is management commitment. Today I gave a talk on getting the change process started. Based on a combination of my own experiences and the patterns documented in Rising and Mann's Fearless Change, I talked about how to get an idea launched and gain initial acceptance to move forward. But even after a successful start, getting and keeping management on board has always been a difficult problem.

A frozen coke bottle can be a powerful symbol of the need for change.
Photo (c) Jonathan Lansey, used with kind permission.

Today I encountered another book about making change happen: Our Iceberg is Melting, by John Kotter. (And thanks to Remo Schmid for lending me the book!) John tells a fable about a young penguin named Fred. Fred is a bit of a loner, but lives with his herd on an iceberg on the coast of Antarctica. Through careful observation, Fred a) notices that the iceberg is melting, and b) because of the way that it is melting, he becomes convinced that terrible things will happen next winter and the herd must act to prevent catastrophe.

According to Fred, the iceberg is melting from the middle, leaving an air pocket, which fills with water. When that water freezes, it will expand, causing the destruction of the iceberg with terrible consequences for the penguin population living there.

Of course most penguins don't believe Fred, and he struggles for acceptance of his ideas. (Several important steps occur here which I will gloss over). Finally, Fred and his Executive Sponsor stage an experiment. By chance, they have found a glass coke bottle, which they fill with water and leave in the ice overnight. If Fred's theory is correct, then as the water turns to ice, it will expand and destroy the coke bottle. Exactly this happens, and the exploded coke bottle becomes a powerful symbol for convincing everyone from the board on down of the urgency of the problem and the need to do something about it.

(At this point, many more important steps take place as the birds eventually adjust to reality and find a way to thrive and prosper in the changed world.)

Getting the attention of top management. Creating a sense of urgency. Seems like the missing link. What's your Coke Bottle? How will you get management's attention and the attention of your co-workers?


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…