Current Status
The number of projects planned or re-planned using the CCPM method stands at 26. This is about two thirds of all our running projects. We have made progress. But, the amount of effort I have to spend poking my nose into some projects seems too high. I intervene far too many times and I’m worried about it.
The project performance indicators are showing we may hit the wall soon if I don’t find a way of avoiding it. The wall is the promised due dates for the projects I’m intervening in. What is the number one reason project managers miss their due dates? They run out of time. Why re we running out of time? And, I’m paranoid. Murphy is waiting to trip us up.
Each project manager has had some time to learn how to lead a CCPM project. The ability to focus on the same set of critical chain tasks can be described as stability enhancing. That’s a good thing around here. And, my ability to get confident answers to “where is the project stuck” questions is satisfying. The answers appear after a few clicks of the mouse. Everything seems to be going fine at the project level.
The Search for Less Expediting
But, why is there still too much expediting from my portfolio level? Some of the projects we recently re-planned required us to go back to our customers and confirm the new dates. Of course, each customer was skeptical of our new dues dates. But, what could they do? We already had the contract and some said they expected us to be late anyway. Sigh.
Staring at the screen or procrastinating over what to do next was not doing anyone any good. Admitting to yourself you are out of your depth is not an easy thing to do either. Yes, the promises we made to our customers are one thing. My promises to our own folks and to our company was another. I have to look into the eyes of these people. How am I going to feel if some day I realized they hadn’t been taken care of? Especially, when I was in a position to do so.
Get Help If You Need It
The tightness in my stomach was worsening. The dizziness is starting to build in my head, so I picked up the phone and called Gary, our non-software salesman. I tracked him down on a beach in Cost Rica. He said the sun was shining and the morning paddle he made around the deep blue inlet was refreshing. But, he had a few minutes for me.
I asked, “With so many projects running under the CCPM rules, why hasn’t our portfolio performance improved at the same rate? I’m concerned we won’t deliver as late as we used to, but I’m not sure we’ll deliver on the dates promised either.”
“I’m glad you called,” he said, “I only have a few minutes, but let me ask you a few questions. How many of the CCPM planned projects do you have running right now?”
“All of them,” I chuckled, “Since they were already underway, we re-planned them and started them as soon as everything checked out.”
“OK,” said Gary, “we may have to check your decision to do that, but here’s another question. What are your most loaded resources?”
I said, “I’m not sure. As you know, we haven’t hired or fired anyone in the past several months. So, the total resource pool hasn’t changed much.”
Gary said, “I know what may be going on, but you will need to check these things yourself. I’m being called away.”
“No problem, what do I need to do? I don’t have a lot of time myself, but I’m sure they are for different reasons that yours,” I said.
Gary says, “Since you, the manager of the project portfolio, do not know the most loaded resources concerns me. You also started projects as soon as they are re-planned. This also concerns me. You may have inadvertently overloaded your resource pool by starting some projects too soon. If you have started projects too soon it’s easy to create multi-tasking between projects. And, when multi-tasking increases, what happens to lead times?”
“Lead times always go up,” I say. I’m glad Gary is being blunt with me. I need some motivation and some clear thinking to get past the tightening screws in my stomach.
Gary says. “Look into the Pipelining process documentation. You will find your answers there. You may find some projects should not have been started right away. In other words, you re-started them too soon. Sorry, that’s all I have time for. I’ve got to go.”
Do Your Research
The phone went silent and I was left with a daydream from a beach vacation long ago. Anyway, we took great care to cut the multi-tasking within projects, it would be a shame to now have multi-tasking between projects. If we have exceeded our resource capacity that would explain it. I clicked on the software documentation and found the Pipelining section.
In the Pipeline section of the User Guide, I read that the Dynamic Drum synchronizes the release of all projects with the Pipeline status. The Dynamic Drum is focused on maximizing the throughput for the entire portfolio of projects. This is what we are missing. Gary and I talked about this a long time ago, so I continue reading.
The User Guide also says the Dynamic Drum is forward looking, not based on historical results or the past use of the resource loading data. This must mean the resource the software is using as the drum resource changes as projects are stared and introduced into the portfolio’s pipeline.
The Dynamic Drum Feature
I click on the Dynamic Drum button and walked through the predefined steps. I ranked the projects and watched the software highlight the resource selected as the Drum resource. It’s our Video Developers. They are the one’s which provide the customer code for the unique features our customers want. Almost every project uses them.
I check the status of the resource loading on another screen. Sure enough, our Video Developers are overloaded. But, so are a few others that I was not aware of. My intuition only goes so far, doesn’t it? I used to be able to tell which resources were overloaded in the past because I worked in the company for so long. I know these people. But, with the changes we’ve made, my intuition isn’t as well developed. I’m going to have to rely on the software to help me after all.
The two things Gary was worried about are indeed true. We have too many projects running and a few resources are showing overloads. I remember now, the earlier we start then the earlier we will finish is not correct. Gary went over this with us. Our new mantra should be, “To finish early, start as late as possible.” I started projects too soon. I didn’t want to lose any time. Folks were already working on these projects and didn’t want to lose momentum. These may all be good reasons, but missing the due dates was not worth it.
Gary’s prediction may be right. If I run the software’s Dynamic Drum the recommended project Start Dates may delay some of the projects from starting today. It will show some projects were released ahead of time and effected the resource use across the portfolio. If I change anything now, it would cause a major wave of disruption across the portfolio. It’s time to call a staff meeting and explain our situation.
A Group’s Problem Needs a Group Solution
Right after lunch, most of my staff are assembled in the conference room. It was a hot afternoon and rush of air conditioning was audible in the background. Jim and Karen came in together, but sat on opposite sides of the room. I know they have been seeing each other on the side, but it was none of my business. At least not until it started to effect their performance.
I started the meeting by saying, “We’ve got a problem. I’m sorry I didn’t catch this sooner, but we may have too many projects running. Too many projects in execution means we have overloaded our resource pool. Not every resource in our resource pool, but a few which many of you have on your projects. Too many overloads, too much multi-tasking, and too long lead times.”
I shared the screens I had looked at earlier. I showed them which resources were overloaded. And, showed them which resource the software suggested as the Dynamic Drum.
Jim asked, “What happens if you take the software’s suggestion?” Jim was wearing a pin-striped short sleeve shirt. Unusual for him, his thick hair was not perfectly in place.
Let the Software Support You
I said, “The software will suggest the optimal start date for each project in the Pipeline status. To include the already running projects in the calculation we need to place them back into the Pipeline. Only then can we understand how many projects our resource pool can handle.”
I let that sink in for a few seconds and said, “And, I don’t know how long these already running projects will stay in the pipeline. But, we have to take some of the load off our resource pool and improve our flow. Improving our flow will improve our throughput. And, improving our throughput will have a positive effect on almost every project’s due date performance.”
The frustrated faces stared at me. I was afraid of that, but when you find yourself in a deep hole, stop digging. We had to find a way out or all our work over the past few months will have been for nothing.
I searched for the right words and said, “I’m sorry for the hassle, but here’s what we are going to do. I’ll put every running project back into Pipeline status. I’ll run the Dynamic Drum process and let the system suggest the start date for each project. For those projects with a start date of today, we can put them back into execution. For those with suggested start dates in the future, we’ll redeploy the effected resources. These re-deployments may help the running projects finish sooner.”
Accepting the Software’s Suggestions
The software staggered the start dates of a few projects and left many of the project back where they started. We exposed capacity for the few resources which were overloaded before. We also exposed capacity for most resources which were not overloaded to begin with. They were redeployed to the running projects. This extra capacity may be enough to improve our flow. The resulting throughput improvement will help us deliver all our projects on time. Makes sense.
But, the main thing I learned is that I can’t run away from my responsibilities. I can’t hide from them because I’m afraid to proceed. The longer the procrastination, the larger the pain. So, what’s worse, the big pain of tomorrow or the tightness in my stomach and the dizziness in my head today? I’m glad Gary was there to point me in the right duration. We all need people like him to get us off the X.
Promising Results
A few weeks later, the first CCPM project we promised to deliver on time was delivered two days early. The projects due by next week were also performing well.
Multi-tasking is the single greatest contributor to poor project performance. And, as difficult as it was to reschedule our projects, is was a major breakthrough for us. It is key to not over-schedule our resource pool. It’s also the key to improving the stability and the throughput of our company.