The Money Files

The Practice Standard for Earned Value sets out the Develop Schedule process, which is simply a way of turning all the stuff in your WBS into a workable plan with timescales. Basically, it’s time to turn the WBS into a Gantt chart.

I guess you could use earned value for non-Gantt chart scheduling, but I can’t get my head around how that would work (tell me in the comments if this is something you do!).

The Practice Standard doesn’t go into loads of detail about how to make a project schedule, as there are other places you can go for that information – like the Practice Standard for Scheduling and also the PMBOK® Guide. However, the particular earned value bits of scheduling are covered in the EV standard, and especially this process.

Inputs

There are two inputs to this process:

• The scope baseline
• The resource breakdown structure.

The scope baseline is more than just the WBS. It also includes the scope statement and the WBS dictionary, so it’s the full set of documents about project scope and the full understanding of what the scope is. It’s the exact spec to a level of detail that allows someone in the team to get the work done.

The resource breakdown structure is the comprehensive guide to who is working on the project as well as the other, non-people, resources required to get the job done.

What to do

The Practice Standard is light on the ‘how to schedule’ element, as I mentioned above, but from a specifically EV perspective, here’s what to take into account:

• Create the schedule in a scheduling tool.
• Make sure dependencies are noted and accounted for, using the scheduling features of your tool
• Manage the relationship with the budget by setting up whatever you need to in the system that will manage that relationship. This might mean setting up control accounts in your accounting software or however you are tracking the budget figures for the project.

This last part is particularly important because it’s the way the schedule and budget relate that drives the EV calculations. You need the same dates, milestones, assumptions and resources set up in each so the measurement is consistent between both systems. In other words, you need to be sure that the work being done is accurately accounted for so that you are working out the right planned value.

Finally, get your project schedule approved the normal way and it then becomes the schedule baseline, against which you can track progress and monitor performance.

Outputs

The output for the Develop Schedule process is only the integrated master schedule, as you would expect.

The ‘master’ part of the IMS, as I understand it, is a way of referring to the fact this is the top level project schedule. The control account managers may have detailed sub-plans for their parts, and you might have intermediate level plans, depending on how complicated the project is. But the IMS – the master schedule – is the full picture of everything required to get the project done.

Dealing with changes

As with any aspect of project management, we have to allow and account for what happens when things change. It’s great to have the IMS as your overarching master schedule and performance measurement baseline, but it’s unrealistic to think that we’ll deliver everything perfectly to plan because that isn’t what happens in real life.

So, we need to use the change control process as and when needed, to make sure the whole thing stays aligned to actual performance. That’s not to say you’ll be re-baselining the project every day, but you will keep the schedule up to date with real progress to compare back to the original baseline, and then re-baseline if and when that becomes appropriate.

If you make schedule changes, you also need to consider what that means for the project budget. When using EVM, you can’t get away from the fact that the two need to align – that’s the point of this way of project tracking, after all.

The IMS exists as a way to outline what the team is planning to do and it gives you the logic for measuring performance. It’s important to get it as good as it can possibly be because it’s what future progress will be measured against and it’s used for calculating future outcomes – and you should want those to be as accurate as possible.

Next time, I’ll be looking at the next process in the earned value landscape, which is establishing the budget.

Pin for later reading

I’m surprisingly enjoying my deep dive into earned value management – it’s not a technique I would say I’m hugely experienced in, but it’s something I’m committed to learning more about.

In this infographic I summarise the 5 limitations of earned value:

• Numbers don’t tell you the whole story and you need a bit of contextual narrative too
• Data has to be accurate otherwise you’re making assumptions and predictions based on what isn’t truly happening
• Quality has to be assumed because EV doesn’t factor in quality as part of the way it measures performance
• EV and Agile aren’t perfectly aligned but that’s OK because if you’re in an agile team you’ll have other (more appropriate) ways of measuring performance
• There is a lot of jargon! And the words sometimes can get in the way of being clear about what you are talking about.

What other limitations of Earned Value have you come across as you’ve used it? Or perhaps you aren’t using EV because of another limitation that is stopping you from embracing it in your environment? Let us know in the comments below!

This is an occasional series on project risk management, and last time we looked at what options are available to you as part of your risk response strategy. Today, we’re looking at how do you actually implement risk responses.

There’s a whole risk response process in the PMBOK® Guide that helps you work out how to approach this part of managing your project.

The Implement Risk Responses process is where you take your response plans and actually do the work to make them happen. The execution of risk response plans is important because you can’t always rely on talking about a potential problem as enough to get it remedied.

There’s no single time to be doing this – you’ll be identifying risks the whole way through your project, so as and when you’ve come up with a new one, you’ll prepare the risk response plan and then implement it. Make time during the project to ensure you think through how to do the implementation part of the risk response strategy – incorporate it into your regular risk meetings.

Inputs

The inputs to this process are:

• The project management plan, and in particular, the risk management plan section
• Project documents including the lessons learned register, the risk register (because this is where you will have written down what you are supposed to be doing) and risk reports if you have them
• Organisational process assets.

The risk management plan will include the names of people responsible for the risk management process, and that’s helpful for assigning ownership of the management actions. You may also have info in there that relates to the level of acceptable risk – this is what you are trying to achieve by doing your risk management activities. It’s not always necessary to remove the risk completely; sometimes just reducing it to a level that’s acceptable to the project or the business is enough.

The OPAs are things like the corporate lessons learned repository which might give you insights into how other risk management approaches were implemented and what were effective techniques at doing so.

Tools and Techniques

The tools and techniques are going to depend very much on what kind of implementing you are doing. How to implement the ‘acceptance’ strategy is obviously very different to an approach where you are going all-out to mitigate it with a huge action plan.

However, there are some common threads to what kinds of tools and techniques you can adopt here, including:

• Expert judgement (drawing on the expertise of your team leaders and your own knowledge about how best to implement the plans)
• Interpersonal and team skills, especially influencing – that’s mainly going to fall to you to ensure that the work gets done
• Project management information system (document and record what you are doing).

Basically, use your PM knowledge to ensure that the planned actions for risk response actually happen.

Outputs

The outputs of this process are:

• Change requests (because your plans might involve adding or removing tasks to your project schedule, for example)
• Project document updates, especially to the issue log, lessons learned register, team assignments (as people’s work assignments need to be updated to reflect their new tasks), the risk register and risk reports.

And, of course, the work of doing the risk responses – built into your To Do lists and action logs, and discussions with team members.

As you get more experienced with project management, you won’t spend much time thinking about ‘doing’ this process. It just happens naturally as part of the things you’re doing on the project. It becomes an integrated part of how you manage risk, and so much aligned to the other parts of risk management that it all flows together. I don’t have meetings where I sit down and say, “Today we are going to do the implement risk responses process.” That’s just not a called out part of how we make risk management happen… but the process does happen. It’s simply integral to everything else and a natural part of how we work together as a team.

The process exists to remind you to make sure that risk responses aren’t something that you simply talk about. You want to avoid that issue of writing down risks and having a lovely risk log, but all the risks sit on there and nothing happens to actually take action on them.

Next time I’ll be looking at how to monitor risks to ensure that your action plans are being carried out as you would expect and are having the right impact on your project.

Pin for later reading

Let’s say you’ve been asked to look over a business case, or your sponsor has drafted a basic business case and has asked you to get it ready for the next review.

In this video, I’ll give you 5 things to look out for: 5 red flags that are worth spotting before your business case gets too far through the process of project acceptance, because if you don’t resolve them, the project will be really hard to manage and you’ll have all kinds of expectation management issues.

Enjoy the video!

Pin for later reading

The Practice Standard for Earned Value sets out the Assign Responsibility process, which is simply a way of making sure everyone knows who is doing what. It’s important in earned value because you need someone to take ownership for every piece of work – that’s the best way to track at each individual element of the work breakdown structure.

Inputs

There is only one input to the Assign Responsibility process and that’s the scope baseline.

What to do

Assigning responsibility isn’t a great name for this process, because ideally individuals in the team will volunteer for the responsibility, knowing that it is part of their job role. I prefer to allow people to step into the responsibility rather than forcing it on them, because I think you gain better buy in and results that way.

However, sometimes I have been known to specifically say, “So I’ll write you down as the owner for that task?” and call out someone as the individual responsible, in a nice way.

Assigning responsibility is about more than someone knowing it is their job to do the work. It’s also about making sure everyone else knows that it is their role, and that it is officially documented somewhere. That’s what this process does.

Create an organisation structure for the project. I tend to do that in PowerPoint, simply making a structure chart with names on that I can then drop into the relevant project documentation. You might have to create several ‘layers’ of your chart so that everyone responsible for substantive pieces of work for the purposes of EV tracking has their information documented.

The Practice Standard recommends that you take the list of people responsible for things and map them against the WBS to create a matrix instead of using an org chart structure. That certainly gives you more granularity and makes it very clear who is doing what.

Outputs

The outputs for the Assign Responsibility process are:

• The organisational breakdown structure – the hierarchy diagram that shows which team/area are involved in the project
• The Responsibility Assignment Matrix

The RAM matrix is a bit different to the traditional RACI matrix because it lists the work packages from the WBS across the top and then the teams or individuals down the side. Look at the relevant intersections and where they meet, put a cross to mark the fact that this person (or team) is responsible for this part of the WBS.

Each X marks a control account: an area of work that is going to be tracked and managed by a control account manager. This is the team leader responsible for doing the work, but CAM is the term used in the world of earned value.

How detailed should you make the plans?

There’s no right answer to this. The WBS and the OBS should be as detailed as necessary to get the job done. Go down to the right level for your project – you’ll have to use your professional judgement for this.

Ideally you are looking for control accounts to be at a level of complexity and scale that makes it possible for them to be managed adequately by one person. Too detailed, and you’ll end up with people responsible for fragments of work and so many control accounts that they are hard to manage in their entirety. Too few and the CAMs won’t truly be able to control the work within them as the tasks will rely on too many people or activities outside of their control.

Plus, think about how much time and energy you and the CAMs have got to dedicate to the admin of running a low-level, detailed plan. Do you really want to take on the management of a lot of tiny things? Isn’t there some saving to be had in combining a few more work packages and making your control accounts sit at the next level up?

Ultimately, you’ll have to make the call but don’t make it too hard for yourself or your team.

Managing changes

You might be thinking: that’s all very good but what happens when things change? Well, things always change, and you have to be alert to that. Respond to changes as and when they happen, using the change control process that you’ve adopted.

Make sure that the CAM impacted by the change (or group of CAMs if there are several) know what has changed and what that means for their work. Update the documentation accordingly. That assumes that you know about the change before the CAM – and sometimes that won’t be the case. They’ll be coming to you with suggestions for changes, so in that case, push them through the change control process and update the rest of the team as appropriate.

The Assign Responsibility process is really all about making sure people know what falls into their remit. If you work with an experienced in-house team, you probably won’t have much difficulty here. If you work with contractors, sub-contractors or external suppliers, make sure that the boundaries of their work are clear – this process helps formalise all of what you should be doing already.

Pin for later reading