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...

Details:

    Comments

    Reto said…
    A blog covering customer/user satisfaction has -sadly- stopped long ago: Creating passionate users from Kathy Sierra - http://headrush.typepad.com/
    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?

    Thanks!

    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…

    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…

    What is the role of a Business Analyst in Scrum?

    When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

    One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
    What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…