Skip to main content

Radical Management Gathering

Revolutionizing The World of Work

When I talk to large organizations about Scrum, I frequently hear "this is great, but what do we do in fields like hardware development or pharmaceuticals, where we can't produce potentially shippable product every thirty days?" Radical Management provides an interesting answer while building on the strengths of Scrum, Agile and Lean:
The purpose of work is to delight your customers. 
So "delivering" every Sprint means something other than delivering a good or service in a finished state. It means delivering an increment of Delight to your customers.

This May, Steve Denning (The Leader’s Guide to Radical Management) and Seth Kahan (Getting Change Right) will be hosting a two day gathering where "coolness, innovation and serious fun intersect." And I am proud to be a Practice Partner!

We want people who are tired of a world in which people are being treated as things, where employees are seen as “human resources” and customers are seen as “demand” that has to be manufactured.

We are offering here more than a set of tools. We are seeking to create a state of mind that starts with a change of heart.

This is about locating that sweet spot where coolness, innovation and serious fun intersect. The fact that it also happens to be ultra efficient and productive is another big plus, because that means that the economics will drive it forward.

This is about creating stuff that people must have. And in the process, we stop wasting time on stupid things, spinning wheels, going through useless routines, attending management prayer meetings and spending endless amounts of time and energy on second-guessing what the boss wants.

I hope that you will join us! Check out Steve Denning's blog for more information or jump straight to registration...



    Reto said…
    A blog covering customer/user satisfaction has -sadly- stopped long ago: Creating passionate users from Kathy Sierra -
    Peter said…
    Hi Reto, I looked at this, and it was clear that some bad things were happening, but it wasn't really clear what happened. Can you give us a synopsis?


    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…