Today’s post is a guest article from Deltek, they’re part of Arras People’s project management software directory and always have good insights to share when it comes to the technical aspects of project management, in this case project planning.
What’s the topic du jour? Optimising, optimising and optimising some more. That’s right – today we’re discussing how to optimise your project plan. What does “optimising” your project plan mean? It means making it better, and more often than not, accelerating it.
At Deltek, we’ve seen a lot of projects where the baseline didn’t meet the commitments. Or, within that first 20% of project execution (where project teams were still planning for the rest of the job) the project was already late. Plans needed to be optimised… and quickly. But what were these project teams to do?
There are three popular methods for optimisation:
Method #1: Cut all activity durations by a certain percentage across the board.
This “haircut” method involves doing just what it says – cutting all activity durations by a certain percentage across the board to have the project finish quicker. The end result is a project plan that shows on-time delivery – and it’s really easy to employ. However, in reality, you do more harm than good. The first couple times you do this, it’ll most likely work as expected. But before too long, your project team will catch on. And do you know what they’ll start doing? They’ll pad their estimates by the amount of cuts they think you’re going to make – and you’re back to square one.
Method #2: Resource leveling.
Another method for optimizing a project plan is resource leveling. This is a capability found in most planning packages or scheduling software tools that helps you ensure you’re not overcommitting resources or trying to plan resources you don’t actually have access to. The problem with this method is that you usually just end up spreading work out over a longer period of time when you think your resources will be available. But a longer period of time equates to more expenses… and an unhappy project manager. So your resource-leveled schedule might end up getting rejected anyways.
Method #3: The path of least resistance.
Ah, so now we get to the good stuff – the path of least resistance. This method involves accelerating a plan with the fewest number of proposed changes to get the most benefit. Have you ever seen the stories on the news about the computer program that solved a rubix cube in only three or four moves? Computers and software help us do things faster and better because they have the power to try thousands of things in only a short period of time. So method #3 involves using Deltek Acumen (or another similar software tool) to run acceleration scenarios that can pinpoint the handful of sweet spots in your project plan where optimisation is possible. Now, it’s not as easy as just loading your project plan and clicking a button. First, we must make the software smart by telling it the places we know we can’t optimise – either because we don’t (and won’t) have the resources or technology to do it better, faster or stronger. In other words, if the software told us to make a change in Process #7, but we know it can’t be done there, that feedback wouldn’t be valuable. So by telling the software where we can’t optimize, it can then look at all of the other places we can – and provide us with a finite area to focus our changes. That’s a whole lot better than making standardised cuts that may or may not work, or getting stuck spinning our wheels in the planning stage with resource leveling.
Software or not, we encourage you to find optimal optimisation strategies that work for your business. In a recent Project Planning Uncensored podcast, Optimize. Optimize. Optimize, Deltek schedule quality guru Tom Polen digs deeper on each of these theories, and offers tips for making the greatest impact with optimization.
Tune in at http://bit.ly/2be76Ln.