The Achilles’ Heel of Agile

Guest post by Jurgen Appelo

When I wrote this, I was working in a big open office space in the Van Nelle Factory in Rotterdam (see photo). About 100 people work in an office that was the first of its kind in Europe, when it was built in 1929. And more than 80 years later, architecture lovers from all over the world still come to admire it, take pictures, and make drawings. I sometimes waved at them.

photo of open office style at Van Nelle Office
Van Nelle office, reprinted by permission of Stephan Meijer

A big open office space has advantages and disadvantages. Advantages are flexibility and easy communication. The main disadvantage is that it is a shared resource for all who work there. Climate, sound, and light are hard to manage in a space like that, and the optimal configuration for the whole is never optimal for all. But our office manager did the best she could in trying to maximize pleasant working conditions, while maintaining tight rules to keep things under control. A shared open office is not the ideal environment to give people full responsibility over their own working space.

Self-organization is usually promoted in agile software development. But when shared resources are not managed by a central authority, self-organization often results in the Tragedy of the Commons. The name refers to a situation in which multiple self-organizing systems, all acting in their own self-interest, overexploit a shared limited resource, even when they all know it is not in anyone’s interest for this to happen. The impact that humanity has on CO2 levels in the air, trees in the forests, and fish in the sea, is right now the most debated and intensively researched case of the Tragedy of the Commons. Organizations also have shared resources, like budgets, office space, and system administrators. We could see them as the business-equivalent of the air we breathe, the landscape we change, and the fish we eat.

Research indicates that four ingredients (called the four I’s) are needed for sustainability of shared resources [Van Vugt 2009:42]:

  • Institutions [managers] who work on building trusting relationships between competing systems [teams] in order to increase acceptance of common rules;
  • Information that increases understanding of the physical and social environment, in order to reduce uncertainty (because uncertainty results in bias towards self-interest);
  • Identity, or a need for a social “belonging” that encompasses all participants, to improve and broaden one’s sense of community and reduce competition between teams;
  • Incentives that address the need to improve oneself, while punishing overuse and rewarding responsible use.

Research shows that it is imperative that there is some form of management (or governance) to protect these shared resources by working on these four I’s. (I realize that most modern day governments are not setting a good example of how to do that.) In the case of shared resources, whether it concerns money, space, or system administrators, someone outside of the development teams must keep an eye on long-term sustainability instead of short-term gains by individual teams.

The Tragedy of the Commons is the Achilles’ heel of Agile. It takes management to protect that heel, in order to prevent teams from depleting resources, and crippling the organization.

This article is an adaptation from Management 3.0: Leading Agile Developers, Developing Agile Leaders, by Jurgen Appelo. The book will be published by Addison-Wesley, in Mike Cohn’s Signature Series.

Related: Embrace Diversity, Erase Uniformitymanagement 3.0agile software development booksVW Phaeton assembly plant

Posted in Books, IT, Lean thinking, Management, Psychology, Respect, Software Development, Systems thinking | Tagged , , , , , , , , | 4 Comments

Management Improvement Carnival #118

Mike Wroblewski is hosting the Management Improvement Carnival #118 on the Got Boondoggle? blog, highlights include:

  • Voice of Customer (VOC): What does it mean? By Mark Wheeler – “Most companies have some type of VOC program in place. Many programs fall short of delivering measurable value. This failure often lies at the definition level of VOC. But how do you actually define it?”
  • He Should Have Seen It by Mark Rosenthal – “We talk about 5S, separating the necessary from the unnecessary, a lot, but usually apply it to things. What about information?” (Also read the link in this post!)
  • Going to Gemba with Grandma by John Wetzel- “I saw something that I would never have discovered if I hadn’t gone to the gemba.”

Related: Management Improvement Carnival #97Management Improvement Carnival #82Management and Leadership Quotes

Posted in Carnival, Lean thinking, Management | Tagged | Comments Off on Management Improvement Carnival #118

Building Adoption of Management Improvement Ideas in Your Organization

Continuation of How to Get a New Management Strategy, Tool or Concept Adopted

Target something that actually provides a good story. It often helps if there have been failures in attempts to solve a problem in the past. That makes the new success more impressive. Something that is relate-able to the audience you are trying to win over is also useful. Even if senior management cares about an issue, if the solution is so technical they are completely baffled, they will be happy with a solution but they won’t be as excited about expanding the strategy you are trying to encourage when they can understand the process that lead to a solution.

Favor efforts that will help you build organizational capacity to do more of what you want going forward (adopt lean thinking, use design of experiments…). Some of this is about building expertise in the organization. It is also about building your circle of influence. Growing your ability to influence how the organization grows will help you encourage the improvements you believe in.

It is very helpful to show connections between individual efforts. Often you build using various tools: in several instances using PDSA cycle to guide improvement, in others mistake-proofing to cement improvement, in another adopting one piece flow to make problems visible and encourage improvement, in another assuring the respect for people to build the right culture for improvement, and in another using an understanding of variation to make evidence based decision rather than jumping to faulty conclusions with limited information. These management tools, concepts, methods and ideas any many more, are used together for a reason. They support each other. So it is very helpful if you tie them together. As you start adding new tools, ideas and concepts to the management system show how they support each other. Individual tools can help. But the gains they offer are minor compared to the gains possible with a systemic change of management.

Another good strategy is picking the right people to involve in an effort. If you are trying to gain support, find those people in the organization that set the tone that others follow (which are not merely those with organizational power due to their job title). It is nice if you can find such people that have generally positive outlooks and like new challenges (this is often the case). If the culture is very toxic you may well have some who are likely to try and discourage hope in others (often because they have been disappointed so many times themselves they have finally decided not to be disappointed again). Often (though not always) you can win these people over.
Continue reading

Posted in Deming, Management, Popular, Quality tools, Systems thinking, Toyota Production System (TPS) | Tagged , , , , , , , , , , , | 16 Comments

How to Get a New Management Strategy, Tool or Concept Adopted

Often when learning about Deming’s ideas on management, lean manufacturing, design of experiments, PDSA… people become excited. They discover new ideas that show great promise to alleviate the troubles they have in their workplace and lead them to better results. But how to actually get their organization to adopt the ideas often confounds them. In fact, I believe most potential improvements efforts may well fail even before they start because people can’t get past this problem.

I believe the way to encourage adoption of management improvement tools, methods and ideas is to solve people’s problems (or give them new opportunities). Instead of trying to convince people by talking about why they need to adopt some new ideas, I think it is much better to show them. To encourage the adoption of whatever it is (a philosophy like Deming or a new tool) try to find projects that would be good candidates for visible success. And then build on those successes.

For adopting whole new ways of working (like lean thinking) you go through this process many times, adding more and more new ideas to the accepted way of doing things. It is a bit easier if you are the CEO, but I think the strategy is very similar whoever you are. For smaller efforts a boss can often just mandate it. But for something like a large improvement in the way work is done (adopting a lean management system, for example), the challenge is the same. You have to convince people that the new methods and ideas are valuable and that they can use the ideas to help improve results.

Start small, it is very helpful if initial efforts are fairly small and straight forward. You often will have limited resources (and limited time people are willing to invest) at first. so start by picking projects that can be accomplished easily and once people have seen success more resources (including what is normally the most important one – people’s time) should be available. Though, honestly getting people to commit will likely be a challenge for a long time.

It is a rare organization that adopts a continual improvement, long term focus, system thinking mindset initially. The tendency is often strong to focus on fire fighting, fear (am I taking a risk by doing x, if I spend time improving y – what about the monthly target my boss is measuring me on…) and maintaining the status quo. It is baffling to many hoping for improvement, when you have huge successes, and yet the old way of doing things retains a great hold. The inertia of organizations is huge.
Continue reading

Posted in Deming, Innovation, Lean thinking, Management, Popular, Process improvement, Psychology, Quality tools, Systems thinking | Tagged , , , , , , , , , , , , , | 15 Comments

Don’t Treat People Like You Want to be Treated

I have never understood the logic behind the idea that you should treat people like you want to be treated. I know I am different; I don’t want what lots of other people seem to want. If I treat them how I want to be treated, they are not happy.

I understand the sentiment behind the statement. I think it is much more effectively stated as: treat people how they want to be treated. An understanding of psychology will provide you with the understanding that people are different and want to be treated differently, while wanting to feel that they are valued and respected. Some people will like a boisterous extroverted environment and others will want to be able to have some time to concentrate and think by themselves. Some people will want to avoid confrontation at almost any costs others will want to deal openly and directly with issues confronting the organization. And most people will be somewhere in between the alternatives.

I don’t want to be thanked for trivial matters. But I have seen lots of people do like this. I do like to be challenged on what I claim and debate the merits of the idea (if I can learn I am wrong, it is much better to do it early and change – instead of waiting for some problem to develop). I notice a lot of others don’t like this at all. I don’t like to be interrupted when I am trying to concentrate. I know lots of others don’t understand this. And when they are treating others as they want to be treated the thought that others are trying to concentrate doesn’t cross their minds. They are not intentionally trying to be disruptive. They are trying to include others as they would like to be included. I find it annoying when we celebrate some minor success while much more serious problems are left unaddressed. I realize most others don’t have this problem.

I like to see data and evidence to back up claims and to explore what the data strongly shows and what conclusions are more tenuous. I know many just get bored by numbers and don’t want to see endless charts and figures. I like to be challenged and asked difficult questions in meetings. I know lots of people do not like this. I would like to ask other people difficult questions (but don’t – if I went with the treat people like you want to be treated idea I would ask). I like change that is part of a sensible strategy of improvement (that measures results to avoid change for that isn’t improvement, which I don’t like). However, I understand many people are uncomfortable with change. I despise sitting in meetings without agendas or a clear purpose that wander and don’t seem to accomplish anything. Others seem un-bothered by this (though I know in this feeling I am with the majority).

I think a key to managing people is to take time to think about the individuals involved, what your intention is, and then to act in a way that is tailored to how that person wants to be treated. Some people will want to be recognized publicly. Some people may want to discuss in private how they could do even better. Some people may like to be given the opportunity to lead a meeting. Others would rather be given the opportunity to create a new design for the intranet. Others may like the opportunity to train new staff on some aspect of their job. Some people may want opportunities to move up the corporate ladder. Others would rather have some time off to pursue other interests.

You should treat people how they want to be treated, not how you want to be treated.
Continue reading

Posted in Deming, Management, Psychology | Tagged , , , , , , , | 13 Comments

Management Improvement Carnival #117

Bryan Lund is hosting the Management Improvement Carnival #117 on the Training Within Industry blog, highlights include:

  • Mark Hamel at Gembatales warns us against the danger of serving two masters…I love the caricatures that he develops for the reader – spot on!
  • A great take on muda, muri and mura by David Kasprzak at My Flexible Pencil. The way David applies the 3Ms to cultural behaviors is clever and thought provoking. Although seemingly “intangible” at first, the cultural wastes that David describes here soon emerge as the first logical target for attack, thereby allowing individuals in the organization to focus on building the ideal relationships so desperately needed to perform at the highest potential.
  • Kevin makes the case for single piece shopping at Evolving Excellence, but not everyone is biting in the comments section…me, I’m on the fence on this. JIT for purchasing makes sense for many, many things but probably shouldn’t be applied blindly to all purchases…

Related: Management Improvement Carnival #952010 Management Review Carnival

Posted in Carnival, Lean thinking, Management | Tagged , | Comments Off on Management Improvement Carnival #117

Jason Fried: Why work doesn’t happen at work

In this TED talk, Jason Fried, founder of 37 signals, discusses how people get work done. When asked where do you go when you really need to get something done, almost no-one says: the office (unless it is early in the morning or late at night)? This is especially for creative people and knowledge workers. They need long stretches of uninterrupted time to concentrate. “The real problems in the office are the managers and the meetings.”

The main theme is that interruptions can severely damage performance, especially for what Peter Drucker called knowledge workers.

He offers 3 suggestions to make the office a place people can get work done. No talk Thursdays. And if that is too much how starting with 1/2 a day Thursday once a month. Second, replace active distraction (meeting, going and talking to a person) with passive distraction (email and IM) that a person can turn off when they need to focus. I have found this very useful myself. And third, cancel meetings. He closes with: I hope I have given managers reasons “to think about about laying off a little bit and giving people some time to get work done.”

Related: Understanding How to Manage GeeksBetter MeetingsWorkers Allowed Recreational Use of the Internet are More ProductiveManagement By IT Crowd Bosses

Posted in Creativity, Management, Psychology, Software Development, Systems thinking | Tagged , , , , , , , , , | 3 Comments

No True Lean Thinking or Agile Software Development

“There is no true value of any characteristic, state, or condition that is defined in terms of measurement or observation.” – Dr. W. Edwards Deming.

The value depends on your operational definition.

Once you operationalize management ideas in a real organization it necessarily should have differences from how it is operationalized elsewhere. As Deming said there are no effective simple recipes for management. It is one of the frustrations people have with Dr. Deming: that there is no cookbook telling you what you should go do as a manager. You need to understand things like: interactions, variation, psychology, systems thinking, how we know what we know (and what we “know” that isn’t so). And then you need to make decisions about how to apply these concepts in your organization.

There is value in being able to think and discuss ideas in a broader context than your organization. You lose a great deal of learning opportunities if you can’t. And having common idea about what common principles a lean thinking organization or agile software organization should have is helpful I believe. That is aided by abstract ideals of these management practices.

Dilbert comic on the futility of process and arbitrary deadlines

One of agile’s guiding principles is individuals and interactions over processes and tools. I am a Deming follower and that emphasizes the importance of process and system. The words in agile are anti-process. But in my experience it is really a specific type of process – and that is basically idiotic adherence to process that the software developers are sick of. This attitude is best summed up in Dilbert. There are plenty of what I would call process in the practice of agile – sprints, kanban, work in process limits, define what done means, using user stories, retrospectives, build in quality… Basically I think it is important to understand what the principles mean, but don’t get locked into dogmatic ideas.

There are principles that seem to me necessary to, for example, consider an effort as lean management. There must be respect for people in lean management. If it isn’t there, then I don’t think it is lean. It might be management using some ideas and tools from lean, but it isn’t lean management. Exactly how respect for people is manifest is up to the organization. The same thing holds for other principles.

Thoughts on No True Agile, No True Lean, No True Latte

Related: Dr. Deming: There is No True ValueHow to Manage What You Can’t MeasureInvolve IT Staff in Business Process ImprovementThe Illusion of Knowledge

Continue reading

Posted in Deming, Lean thinking, Software Development | Tagged , , , , , , , | 1 Comment

Management Improvement Carnival #116

The management blog carnival is published 3 times a month with select recent management blog posts. Also try Curious Cat Management Articles for online management improvement articles: you can subscribe to an RSS feed for management articles now.

  • Why Google can’t build Instagram – ” 4. Google forces its developers to use its infrastructure, which wasn’t developed for small social projects. At Google you can’t use MySQL and Ruby on Rails. You’ve gotta build everything to deploy on its internal database “Big Table,” they call it. That wasn’t designed for small little dinky social projects. Engineers tell me it’s hard to develop for and not as productive as other tools that external developers get to use.”
  • Don’t Let Benchmarking Replace Your Own Process Engineering by Mark Graban – “One thing I’ve seen in hospitals is that there’s a general lack of Industrial Engineering (aka Management Engineering, in healthcare) basics that would allow a department or manager to determine the right staffing levels based on inputs including patient demand, quality and safety requirements, and that hospital’s processes.”
  • Putting Performance Reviews On Probation – Samuel Culbert, author of Get Rid Of The Performance Review!, couldn’t agree more. “It’s the most ridiculous practice in the world,” he tells NPR’s Neal Conan. “It’s bogus, fraudulent, dishonest at its core, and reflects stupid, bad, cowardly management.”
  • How many different types of A3’s are there? by Tracey Richardson – “I will briefly describe the 4 different types of A3’s and when to use them based on my experience: Problem Solving A3, Proposal A3, Status Report A3, Strategic Planning A3”
  • Should story points be assigned to a bug fixing story by Mike Cohn – “My usual recommendation is to assign points to the bug fixing. This really achieves the best of both worlds. We are able to see how much work the team is really able to accomplish but also able to look at the historical data and see how much went into the bug-fixing story each sprint. Knowing this can be helpful to a team and its product owner”
  • Continue reading

Posted in Carnival, Management | Tagged | Comments Off on Management Improvement Carnival #116

Airport Security with Lean Management Principles

The ‘Israelification’ of airports: High security, little bother [the broken link was removed]

We [Israel] said, ‘We’re not going to do this. You’re going to find a way that will take care of security without touching the efficiency of the airport.”

“The whole time, they are looking into your eyes — which is very embarrassing. But this is one of the ways they figure out if you are suspicious or not. It takes 20, 25 seconds,” said Sela. Lines are staggered. People are not allowed to bunch up into inviting targets for a bomber who has gotten this far.

Lean thinking: customer focus, value stream (don’t take actions that destroy the value stream to supposedly meet some other goal), respect for people [this is a much deeper concept than treat employees with respect], evidence based decision making (do what works – “look into your eyes”), invest in your people (Israel’s solution requires people that are good at their job and committed to doing a good job – frankly it requires engaged managers which is another thing missing from our system).

The USA solution if something suspicious is found in bag screening? Evacuate the entire airport terminal. Very poor design (it is hard to over-emphasis how poor this is). It will take time to design fixes into physical space, as it always does in lean thinking. It has been nearly 10 years. Where is the progress?

[the embedded video link was broken so it has been removed]

A screener at Ben-Gurion has a pair of better options. First, the screening area is surrounded by contoured, blast-proof glass that can contain the detonation of up to 100 kilos of plastic explosive. Only the few dozen people within the screening area need be removed, and only to a point a few metres away.

Second, all the screening areas contain ‘bomb boxes’. If a screener spots a suspect bag, he/she is trained to pick it up and place it in the box, which is blast proof. A bomb squad arrives shortly and wheels the box away for further investigation.

This is a very small simple example of how we can simply stop a problem that would cripple one of your airports,” Sela said.

Lean thinking: design the workspace to the task at hand. Obviously done in one place and not the other. Also it shows the thought behind designing solutions that do not destroy the value stream unlike the approach taken in the USA. And the better solution puts a design in place that gives primacy to safety: the supposed reason for all the effort.
Continue reading

Posted in Creativity, Customer focus, Deming, Lean thinking, Psychology, Respect | Tagged , , , , , , , , | 1 Comment