The transition from traditional sonoma property management to Critical Chain Project Management (CCPM) in a multi-project environment presents a formidable problem with projects of long duration. A simple method is presented for that transition and provides the metrics necessary to directly encourage and cement the behaviors needed for Critical Chain Multi-Project Management. This paper assumes the reader is familiar with CCPM.
The Multi-Project Implementation
This paper focuses on the period of time from planning the first Critical Chain (CC) project, the cut-over project, to completion of the last traditionally managed project. This can be a long period of time before the company has fully implemented Critical Chain Project Management. Theory of Constraints (TOC) practitioners involved in Critical Chain Mulit-Project Management (CCMPM), often find this transition to be the toughest part of an implementation.
The Implementation Conflict
In order to successfully implement Critical Chain Multi-Project Management, we must obtain support for it. Everyone expects that CCPM will be another flavor-of-the-month implementation that fades away if properly ignored. To obtain that support, we must start with one project to prove that CCPM works. And to be successful, we must change the whole project system to CCMPM. Because Critical Chain requires Buffer Management and traditional projects can’t use it, we must implement CC on all projects at the same time.
Implement One Critical Chain Project First
Even though we know it works, we must prove that it works “here!” A common solution is to use a pilot (trial) project as a way to demonstrate CCPM and get the bugs out of the existing system. One project at a time is much simpler to implement than many. The pilot project should not be thought of as a trial. It’s really the first Critical Chain (CC) project, the cut-over project. Every new project following it will also be a CC project.
Typically, for a transition, the cut-over project is planned while the work-in-process is ignored. But in a multi-project management environment, that means that some or many shared resources will be fought over by the CC and non-CC projects. The resources are usually expected to multitask and have several projects in work at one time. Multitasking is a huge factor in projects being slow. How can scarce resources be assigned where they are most needed, if the statuses of these projects are measured differently?
The common approach to adding a new project to the pipeline of projects is to commit to a date and put it in the system. With little understanding of the amount of work in the system and the system’s capacity, work is pushed in with the expectation that it will get done.
With a system full of work-in-process projects, it will take a long time to complete this first CC project. Continued multitasking between projects will assure it. The reality is that people are asked to not multitask on the CC project while they are multitasking on the others. The non-CC projects will delay the faster, CC project. It will be difficult to determine and measure the Critical Chain project’s success compared to the others. Some people will believe it gets special attention and will demand to share its resources.