Skip to main content

Making your Company a Better Place

Welcome to the future! Fellow revolutionaries! We are here to change the world. This is an invitation to meet here again on May 12, 2021. By that time, we will have transformed the Fortune 500. We will have transformed the government. We will have transformed the health sector. We will have transformed the education sector....

You might be wondering: how could we, the thirty people in this room, possibly change the world. We have few resources. We don’t have much money. We have little explicit power. We don’t have political clout in any conventional sense. So how could we possibly change the world?

The reason why we are going to be able to change the world is that we have a better idea. At the end of these two days, we will all own a set of ideas that will change the world.
With this compelling vision, Steve Denning, Seth Kahn and 5 Practice Partners (including yours truly) introduced the 25 participants into the world of Radical Management. Why did the 25 people come to take on such a daunting challenge? One participant, a senior manager at a large organization, explained it this way:
These ideas resonated with me. I work in a large organization and it’s obvious that command and control is a disaster and we need to aspire to these ways of working. In my company we just went through a change initiative that was about saving $10 million, but it was billed as bringing us closer to the customer. It was a complete lie. We are getting this wrong and the stakes are really high. We need this kind of thing so badly.
How are the new principles different from the old ones? Steve put up the following table:

Delighting the customers is more important than making money for shareholders?! How can than be?

Look at companies like Apple,, or Amazon. Why are these companies so profitable and so well regarded on Wall Street? Because they delight their customers. They innovate. They create new value and learn to thrive in the 21st century. And they are great places to work. Look at companies like General Electric or Walmart. Their stocks have gone nowhere. Their command and control culture has not enabled them to innovate.

According to the Deloitte Shift Index, only 20% of workers are passionate about their jobs. Since 1960, the life expectancy of a Fortune 500 company has declined from 75 years to 10 years today! Innovation and involvement is crucial and traditional management is not doing the job!

At the Scrum Breakfast this month, we'll explore this new work paradigm. If you want to change your company for the better, then check out this video and join us at the Scrum Breakfast in June!


javin paul said…
I like the imagination of perfect world :)

How Garbage collection works in Java
Peter said…
"Don't Dream It, Be It!" ;-)

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 …

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…