– See All Project Management Key Concepts –

Baselined Documents in Project Management

When we’re developing the project management plan a lot of the time we’re going to need to create baselines.

Baselines are one of the key concepts that is really important, because they are a point in time where data or information is locked in place, with any changes needing to go through a formal change or configuration management process to be reviewed, approved and accepted.

There are multiple documents that require baselining in your project management plan, and most of those will relate to the key constraints in your project such as:

• Scope – the scope that you are going to deliver.
• Time or the schedule – you might have your Gantt chart or the locked-in schedule, and you don’t really want that to change because you’re delivering something at the end and your customers are relying on that to be delivered.
• Cost – if someone is sponsoring this project or paying for this project then of course they don’t want that cost to change, at least not without the proper approval process.

So what are these documents that we’re talking about? Well the need to be baselined fairly early on in your project, during the initiation and planning of your project.

First of all we’ve got the scope baseline. This is the approved version of a scope statement, a nice simple statement of what you are delivering to your customer. Then you’ve got the associated work breakdown structure or WBS and its associated WBS dictionary. That’s basically the scope broken down into smaller parts.

Then ultimately the activities that we’ll need to to deliver those parts – all of those parts of your scope – we want to lock that in so that we know that we’re going to deliver it on time, and we know if we’re not going to deliver it on time.

Then there is the schedule baseline, which is the approved version of the schedule model (that can be your Gantt or even just dates and activities depending on how you outline that in your project management plan) and can be used as a basis for comparison to the actual results so once it’s locked in. For example, how are we actually tracking over time? Are we on track, or we not going well? That’s what we really want to know.

Lastly we’ve got the cost baseline. This is the approved version of the time based project budget where we’ve got our activities, the things that need to be completed and we’ve got the cost associated with those activities. All of the schedule and the scope – if any of that changes then obviously that will have a big impact on the cost of the project as well, so all of these things are interrelated.

Before a baseline is actually defined, all of these documents can be updated as many times as necessary. You’ll find that right at the beginning of your project, during the project charter and maybe just before you’ve locked in your project management plan, no formal process is required at that time. But once that baseline is locked in then they can only be changed through the “perform integrated change control” process which we’ll probably notice is around 4.6 in the PMBOK guide. Any stakeholder can raise a change request, that’s how this is done. Anyone related to your project, whether it’s someone impacted by the project or whether it’s the sponsor who’s sponsoring the project, whether it’s the people doing the the work packages in the team of the project, they can raise a change request for that to be looked at which will go through the change control process. That change control process is usually outlined in your project management plan as the configuration management plan.

What Does a Configuration Management Plan Process look like?

It will be different for each organisation and even each team you work in. Maybe the process for you is raising a change request to the project manager, the project manager checks it out with a few different stakeholders or the required information, or maybe that’s someone in the project management team who then goes through to the sponsor or to the associated steering committee for example. Depending on how your project is outlined, which of course relates to the enterprise environmental factors which you’ll see come up a lot in the PMBOK guide. This is how the company operates, and every company is different. There will be similarities, there might be templates, there might be different politics or different parts of the company that need to be approached, or maybe different parts of the company that don’t talk to each other at all. You need to be aware of these enterprise environmental factors in how to get work done and that will impact the configuration management plan, which is how to make changes to your project and your project baselines once they are locked in. And that is project Baselines.

 – David McLachlan

– See All Project Management Key Concepts –