I’ve participated in several discussions and presentations lately where the subject of Lean and Agile came up and I think the relationship of the two is very interesting. If you pursued each of those approaches to the extreme and tried maximize what you would get out of each independently, they would tend to pull you in different directions:
- Lean emphasizes reducing “waste” and Agile emphasizes flexibility and adaptivity to meet customer needs.
- Those two approaches are not totally compatible with each other; however, they are not necessarily incompatible either. It just requires some skill to blend them together in the right proportions to fit a given situation
Here’s an example, Michael Nir recently made a presentation at an Agile Boston meeting about “The Agile PMO” which was based on his book of the same name. Michael indicated that a key potential role of an Agile PMO is to reduce waste in an organization and that goal is very consistent with Lean. An example of that could be under-utilization of people in the organization.
How Does Lean Reduce Waste?
Michael indicated that a key potential role of an Agile PMO is to reduce waste in an organization and that goal is very consistent with Lean. For example,
- Under-utilization of people in the organization,
- Under-utilization of resources, or
- Less than optimum utilization of resources
could certainly be a major source of waste in an organization. There are a number of ways that a PMO can reduce waste:
Utilization of Specialized Resources
If specialized resources that are not dedicated to project teams (such as DBA’s) are not well-planned and coordinated across teams:
- Project teams may be idle waiting for these specialized resources, or
- The specialized resources might not be fully-utilized waiting for work from project teams
Project Portfolio Management
If a project portfolio is not well-managed, allocation of resources to project teams may not be not well-aligned with company business goals and priorities
Project Management of Individual Projects
If individual projects are not well-managed and are allowed to go off track, the allocation of resources to projects may not be optimized to maximize the business results for the company
Development Process Definition and Training
- The development process is not well-defined,
- Tools aren’t adequate to support the process, and/or
- Project teams are not well-trained to execute the process
the execution of the process will not be consistent across teams and may not be as efficient and effective as it could be
In all of those areas, a PMO might add value by reducing waste but how far do you go with that?
Can You Reduce Waste to Zero?
Carried to an extreme, a focus on simply reducing waste could easily become dysfunctional. Michael mentioned that waste in some organizations could be as high as 95%. What would happen if you attempted to reduce waste to 0%?
- First, reducing waste to 0% is probably an unrealistic and impossible goal. No business is totally predictable where everything is known in advance to enable perfect prioritization, planning, and scheduling of resources
- Second, putting too much emphasis on reducing waste would would mean superimposing a level of control and standardization on projects. That could easily be inconsistent with achieving the flexibility and adaptivity required by an Agile approach
What’s the Right Answer?
Given that conflict, what’s the right answer? This is not necessarily an easy problem to solve. It will take some skill to figure out the right blend of:
- Focusing on lean and reducing waste and
- Preserving the flexibility and adaptivity required by an Agile approach.
There clearly seems to be an optimum point between the two extremes of focusing on those two extremes individually. A PMO could probably perform a value-added role in helping an organization find that optimum point.
Finding that optimum point is yet another example of the need for “systems thinking”. Here’s a previous post I wrote on that subject:
People many times like to over-simplify what is really much more complex and reduce it to a simple, binary choice between two extremes:
- “Agile” versus “Waterfall” is one example of that and
- “Lean” versus “Agile” is another example.
On the surface, Lean and Agile might appear to be in conflict with each other. If you pursued each approach individually and mechanically without really understanding the principles behind each at a deeper level, they could easily be in conflict.
On the other hand, if you take take a systems-thinking approach to understand these seemingly disparate approaches at a deeper level. you will begin to develop a fresh new perspective to see them as complementary to each other rather than competitive.
Michael made a key point that it is a matter of focusing on value versus control and he’s absolutely right. Here are some ways a PMO could add value:
- Better defining processes and tools,
- Providing training to people, and
- Doing some level of project portfolio management and resource planning of people
Each of those can potentially add value; however, it does take some skill to determine the optimum point beyond which it stops producing value and starts to become dysfunctional.
You can find related articles on the topic of “Understanding Agile” here:
You will find much more detail on this in my Online Agile Project Management Training.