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?

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 …