Skip to main content

Waste Reduction in Project Environment - A Lean View

Dr. Taiichi Ohno identified seven category of waste in manufacturing and production that can be applied to project management, to make project environment Leaner. Overproduction, Waiting, Transportation, excess inventory, excess motion, non-value-added processing and defects are the seven categories of waste in Lean manufacturing. Here is a brief translation of  7 categories of waste in project management environment, especially in multi-project environment or/and project management system of systems:

1- Overproduction in project environment happens:

  • when a task is assigned to a resource before the task is available!
  • or when a task is assigned to a resource because the resource is available and not because the task needs to be performed.
  • or doing a task as part of the project, but in fact it is not part of delivering the value of the project.
2- Waiting in project environment is one of those killers;
  • when a task is half way through, and a resource is pulled away to work on another task at the same time, the first task experiences waste in time as it waits or it is idle for the resource to perform other task. (inefficient multi-tasking)
  • when a predecessor tasks completes it's work, but it dose not get passed to successor. Therefore Successor experience waste by waiting for its hand off. (kinda No-Early-Work-Transfers)
3- Transportation waste can be translated into project environment as;
  • when wrong or unnecessary dependencies are in project schedule, one task should start only after the input of its predecessor task arrives, however that input is not really necessary.
  • when a review that generates looping back or rework is later in the process than it should be.
4- Excess Inventory in a project environment is;
  • when too much work is in progress (high level of WIP), and organization can not process them effectively. (this is a result of bad project pipeline management)
  • or when a skilled/limited resource is reserved for a task more than the actual time that is required for that task to be completed.
5- Excess emotion occurs in project environment;
  • when time has been put on a task that it is not really needed to be completed for the project or it is not needed for the task to be finished to create value.
  • when  holding onto a task that is complete (keep polishing the output or searching for hand off is all waste)
  • when a task is multitasked, time is required to setting it down or/and picking it up again. Such a time is waste.
6- Non-Value-Added Processing;
  • Adding more reviews and sign offs to deliveries that is not really necessary
  • or when resources are require to accomplish additional tasks within the project that those tasks are not part of the actual project, but are required! (for example, creating tickets/request in multiple systems for different parties to get permission to release/deploy a Web site, or having so many status meetings and reports)
7- Defects may take many forms;
  • wrong, missing an incomplete information (such as incomplete Scope, translating client requirements wrongly to other team members)
  • handing off work when it dose not meet hand off criteria.
What would happen to your projects if you experience less of 4 destructive project behaviors and minimum amount of waste? Simply, everything will be delivered on-time with higher quality!

Now, combine this with a project management framework or methodology such as Critical Chain Management or Scrum and you will get projects delivered even earlier than plan!

Why don't project based organizations reduce 7 wastes? why don't they prevent 4 destructive behaviors? don't they want to deliver projects sooner, faster and with higher quality?!

Because, it is not enough for a Project Based Organization (PBO) to change its mind set alone and expects a dramatic improvement in project delivery. PBO needs to reduce waste and prevent 4 destructive behaviors, and it needs to force its partners and vendors to do the same, and it needs to persuade its clients to do the same, and only then the whole system will be improved!

----------------------------------------------------
Similar and Related Blogs



Post a Comment

Popular posts from this blog

Escalate, Escalate, Escalate!

What is escalation at organizations? Is it a way to solve problems? Is it a way to report things? Is it a way to put more pressure? Is it a CYA technique? What is it? How do you use it at your organization? How other colleagues of yours use escalation? Really, think about it and observe.

At IT service companies, leadership measures the performance of IT Help Desk by number of escalated work items over a period of time. The less escalation the better. The reasons are simple:

It is cheaper for companies if an IT Help Desk Specialist resolves an issue than an experienced technical specialist at one or two level higher. This is simple math, one gets $X and the other get $X*2And when client gets result fast, he/she will be happier. So, less escalation equals happier client in IT Services. Client raise an issue, IT Help Desk Specialist resolve it, BOOM, Next!

At organizations, It is amazing (sadly) to see how much lower level managers escalate problems, that they and their fellows can resol…

DAD Inception Phase Workshop Agenda

Disciplined Agile Delivery (DAD) realised the reality of the projects and introduced back phases to Agile community. Whoever works in a project based company, especially a project based company where projects are usually less than one year in length and each are for different clients, understands the reality of Agile in such environment. When you start working on a new project for a new client, it is essential to go through a phase that you get to know each other better, to understand the business purpose of the project, to understand the scope of the project, to know what are the high level architecture and what technologies are going to be used and who is the initial team, and if funding is available and also when things must be delivered and to whom.
In answering these questions you may need to meet with different people, run couple of workshops and brainstorming sessions. And this is called Inception Phase. As DAD is more like a goal oriented decision framework and not a prescrip…

Collocation is not the silver bullet for success and agility

To collocate or not to collocate? Most companies that are new to agile have been "consulted" by a "Scrum" Agile Coach, who suggested that they must break their organisation and have cross-functional teams to sit together in one location. Is that the recipe for success?.. Is it really?

Even though collocation has its benefits, it is not the necessary condition for a successful delivery team. Collocation as a dogmatic view may hurt you more than you think, and will not necessarily help you to deliver more successful products.

I am neither for nor against collocation, but I have experienced and worked with both approaches. And each sometimes worked very well and sometimes failed. All the variations of teams geolocation (collocated, fully-dispersed, partially-dispersed, or distributed) can work. It all depends on how the collaboration model is setup, what is the context and conditions, and how much the team and organisation are aware of each other, and are aligned.

Ha…