The baseline — whether it be about the schedule, the budget or the scope — is essential in projects. Without it you have no way to measure the performance of your work. But there may be a few things you don’t know about baselines in Microsoft Project. In this article I share five facets of baselines worth adding to your mental knowledgebase. Although I’ve taken the images from Project 2016, the same techniques I cover here can be reproduced with Project 2010 and Project 2013.
- There are 11 Baselines
In Project setting a baseline is easy. You select the ribbon tab “Project” and in the “Schedule” group select “Set Baseline” and then select “Set Baseline.”
A new menu opens and gives you the option to set the baseline for just a selection of tasks or the whole schedule in total. Pressing OK without changing any of the settings will set the baseline, and you’re done.
But, you can do more. Here’s a screenshot when you open the dropdown arrow beside Baseline:
You have the chance to set up to 11 baselines for your schedule. It might also be nice to know what the baseline saves for you. Here’s the list of fields that are saved, with “Baseline #” in front of it:
- Only One Baseline Works with Earned Value Management
It’s a good thing that you can save more than just one baseline. Just think about scope changes. You may end up wanting to save Baseline 1, 2 or 3… (More on that in tip #4.)
But keep in mind, only “Baseline” — the first baseline, which doesn’t have a number — works together with the earned value management functionality within Microsoft Project!
You’ll need to use the first baseline if you intend to work with EVM and want to use Project to get a good sense of your planned value (PV), actual cost work performed or actual costs (ACWP/AC) and schedule variance (SV). All the EV items work with either the actual schedule or the information from the first baseline.
- You Can Show Any Baseline with This Simple Trick
There are a couple of views with baseline already available to you when you have done nothing in regards to customization. The most notable view is the Tracking Gantt.
The Tracking Gantt is a great way to visualize progress on your schedule for several reasons:
- It contains a visual on percent complete (also for summary rows and the project summary row);
- It shows the critical path in red; and
- It shows the baseline (but only the baseline).
The last reason gives us food for thought. Can we show a schedule and compare it with Baselines 1 through 10? You might want to do this for a lessons-learned session, for instance, where you’d decompose the schedule and review where things went wrong and could be improved or where things went very well. If a schedule had three scope changes, you might be interested to see the gap between the original schedule and the finished product. That way you could generate a view on how good or bad your project managers are in their estimations. (Don’t get me wrong; the consensus is that we all really stink at estimating! Wouldn’t it be nice to be reminded of it on a regular basis?)
So how do you show the other baselines? It’s easy! In the newer versions (2010 and up) there’s an option in the contextual tab, Gantt chart tools | Format, in the ribbon.
The option is called Baseline, and it’s available from the group, Bar Styles. Here you have a dropdown giving you the option to show every baseline compared to the current Gantt view. For instance, I made a new baseline (Baseline number 1) with the schedule I showed earlier, and here’s the resulting Tracking Gantt view:
While this may look like the same picture as above, it shows Baseline1 instead of “Baseline.” Take a closer look at the darker bars underneath the actual schedule. You can now switch between the baselines to compare them.
If you’d like to see the different baselines together, here’s an image from a guest post done by Bonnie Biafore on my blog.
- You Should Set up Two Baselines Each Time
Back to the scope changes, because there’s something to keep in mind here. Whenever you have a change in scope, you might like to compare the actual schedule to the current approved budget and timeline, right? That means you set a new baseline and work with that baseline in your progress reports.
Again, the thing you need to keep in mind is that you’ll have to use “Baseline” for earned value management.
So, when you change the baseline, you’ll overwrite that one to make your calculations reliable. But you’ll also want to retain the original baseline for your lessons-learned sessions. That’s why I suggest you create not one but two baselines every time you have a schedule approved by management or your client. This is how I would suggest you proceed:
|Type of approval||Which baselines to set|
|Original approval||Baseline and Baseline 1|
|First scope change||Baseline and Baseline 2|
|Second scope change||Baseline and Baseline 3|
|Ninth scope change |
(I'd hope, of course, that it never came to this...)
|Baseline and Baseline 10|
With this technique you never have to wonder about which baseline you should pick in the Tracking Gantt because you have the right one there already. And your EVM measurements will still be correct.
- You Can Lock Six Baselines if You Use Project Server or Project Online
If you’re using Project together with the server installment (EPM 2007, EPM 2010, PPM 2013, PPM 2016 and Project Online), you’re in luck! There’s even more baseline magic you can tap into.
If your organization needs reports that contain baseline information in a structure set by the enterprise project management office or something similar, there might be a reason to lock those baselines from random changes! You can do this for the first six baselines — meaning, Baseline and Baseline 1 through 5. In this way you could create a permissions structure. The PMO would have the authority to set the locked baseline using those six baselines, and you’d be able to continue using baselines six through 10 for your own unofficial purposes. One caveat: Setting these permissions is something you probably won’t be able to do yourself. Contact an administrator to get this feature implemented.
While there’s plenty more to understand about baselines, I hope this story will give you some new tricks for honing your project management skills.
Do you have your own baseline tips? Share them in the comments below so the entire MPUG community will benefit.