Skip to main content

Achieving Phase Change: Why is it so difficult to change management

In preparation for the #Stoos Gathering, we have been asking 'Why is it so difficult to change management? While we are not the first to ask the question, it has once again stimulated much discussion (@jurgen's blog, @steve's blog, or on the ScrumAlliance Linkedin group).

Back when the #Occupy movements were getting started, Steve Denning wrote, "What do the occupiers want? Phase Change."
People increasingly sense that things aren’t going to get better unless something big is done, some fundamental change is made in our financial structures. It won’t be small-time rejiggering—a tiny cut in this tax, a minor reduction in that program—that will get us out of this. Like Oliver Twist, they intuit—however incoherently and inarticulately—that we need a phase change, a change in which everything is different.

Phase changes follow patterns regardless of physical or social makeup. They entail a change from one level of order to another. Phase changes are everywhere in nature: from ice to water, from water to steam, from iron to magnet, from seed to flower, from birth to life.

What does it take to make a phase change happen? Energy. Lot's of energy. Let's look at what it takes to change ice into liquid water:

Image Courtesy of Wikipedia
It takes only 1 calorie to raise the temperature of 1 gram (= 1 milliliter) of water by 1 degree C, but it takes 80 calories to transform 1 gram of ice into one gram of liquid water, and the temperature is still 0C! If the water were liquid at 0C, those 80 calories would raise the temperature to 80C!

We have seen examples of social phase change, most recently the Arab Spring. Figuratively speaking, the temperature is still there very cold, and the societies may yet refreeze, but there is now movement in these societies.

And what of management? Most management structures are still pretty inflexible, pretty frozen. But every Scrum team or Kanban project is part of the thaw. Every radical manager is a source of energy, helping his/her company to warmer spring.

Help us catalyze a phase change at the #Stoos Gathering: when have you experienced phase change? What made it happen? And how can we apply that to transform management?


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…