Skip to main content

Agile is spreading, and management will be the last to know

A few months ago, I watch a stunning video about how bacteria overcome antibiotics. It's stunning how fast the adaptation can occur! I believe agility is transforming the world of work in a similar way. I believe top management is most resistant.

It is stunning how quickly bacteria overwhelm the antibiotics. In just 12 days, E. Coli bacteria can adapt to survive in an environment that has 1000x the concentration of antibiotics which would kill the bacteria at the beginning of the process. The bacteria adapt constantly - they are agile! Antibiotics adapt very slowly - in this case, not at all. So I guess that makes them waterfall if the agile counterpart is fast enough.

How bacteria overcome antibiotics


Jurgen Apello recently assembled a list of Agile Models, Methods and Movements. As I write this, there are 150 entries in the list. At least 25, and perhaps as many as 50 of them are not about software. There are methods for Product Innovation, Building Cars, Education and Schools, Personal Time Management, Collaboration, Coaching, Marketing and more.

Some of them are about organization and management: Radical Management, Management 3.0, Beyond Budgeting, Sociocracy and Holacracy are among the more prominent. While there are some examples, see for instance the SD-Learning consortium, AFAIK none of them is mainstream at the C-level.

The field of software development corresponds to the zone of level 1 dosage of antibiotics. Today agile software development is now mainstream in development groups, even as many people and companies still struggle to do it well. 

The next level is the immediate leadership of customers, managers and stakeholders. This corresponds to level 10.  There are many adaptations, including frameworks like SAFe and LeSS, but this domain is still more traditional than agile. (I am currently working on a course for Stakeholders. Please contact me if you'd like to help with solution validation! Thanks!)

Each new Agile framework is an adaptation to a new domain. Non-software areas, like building cars and other tangible products, correspond to dosage level 100. Here agility is just starting to make inroads.

And the most resistant? The C-Level of big companies and organizations. These institutions are most insulated from all kinds of change and disruption. They are represented by the 1000x level antibiotic dosage.

I believe stakeholders of software projects will be the next group to adopt/adapt to agility. Many other domains will start applying the lessons of agility soon. Top management (and government) will be the last to know! 


Comments

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…