Skip to main content

Agile Software Development or Radical Management?

In any case, an idea who's time has come!

Steve Denning, recently wrote a 5 part series of articles on the forbes.com blog: Why Amazon Can't Make A Kindle In the USA. The response was extraordinary for a management article and unheard of for an Agile article - as I write this, the first article alone has been read over 280'000 times. The follow up articles had another 100'000 reads.

Radical Management is taking the message of Lean, Agile and Scrum to general management.


Now, when I talk to thought leaders in business, I often hear - 'yes, I have been teaching 'this' for years! -- where 'this' means self-organization, short feedback loops, working with or delighting the customer, minimizing waste, removing impediments, creating a learning organization, or other values, principles and practices of Scrum, Lean, and Agile.

Finally the message is getting through!

IT and manufacturing organizations doing Agile, Scrum and Lean were the evangelists and early adopters. Now they are finding they are finding common values and practices in everything from Rental Car operations to building housing.

Now is the time for the early majority in business management to get on the train! Do you want to get on board?
  • Radical Management Gathering in Zurich for C-Suite Managers: Steve Denning and I will host a 1-day introduction into the principles and practices of Radical Management
    Info & Registration
  • Lean Agile Scrum Conference - keynotes from Steve Denning and David J. Anderson, 16 Workshops and Sessions from experts around Europe for all levels of the organization. Of course 'the Doctor is IN' a free clinic from expert to expert in a private atmosphere, so you can get solutions for your issues.
    Info and Registration. 
And if that's not enough: as sponsors of the Conference, Peter Beck, Andreas Schliep and will be there and look forward to seeing you there as well!

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 …