The Money Files

The processes you have for project management – or lack of them – can add significant risk to your project. But you don’t often find them called out on the risk log.

Poor processes can add time delays, extra steps and confusion. They contribute to poor communication and overspending. They impact project quality. In short, processes that aren’t optimal can hinder your ability to deliver a decent outcome for the project.

Unfortunately, processes are often constrained by the company you are in. If you are mandated to follow certain processes, you have little flexibility to do anything about them. That’s not a good situation to be in – ideally you should be able to tailor the process to the size and complexity of your project.

I’ve highlighted three of the main process-related factors that influence risk on your project in the video below.

Read more articles about risk.

Pin for later reading:

How often have you looked at a set of data points and wondered what the… point was of capturing them at all? I’ve seen PMOs with measures for how many projects were closed in a month but not measures for whether those closed projects were done on time and on budget, for example. Sometimes I think our desire to catalogue and record everything goes a little bit too far. There isn’t any point in capturing data that no one cares about.

This graphic shows three core principles for creating and using metrics. They are universally applicable but good for project managers because we have to think up (and then find ways to track) KPIs and success criteria measures for our projects. And if you’re in a PMO role, you must have a bunch of data points you are collecting too – I wonder how many of them make it into the reports you produce for stakeholders? And then how many stakeholders actually read and care about them?

For more on the topic of what makes a good measure for your project, take a look at this article, which digs into some examples and how to make sure that you are creating measures that are useful, in more detail.

It’s January: the time that we reflect on past achievements and future goals. So let’s take a moment to look back at how you did at work with your approaches to project cost management.

I know, I know… you followed your team’s methodology to the letter and did All The Things. But really – did you? I know that for me, with all the deadlines to hit and meetings, reports to prep and executives with unrealistic expectations… I didn’t do everything as well as I would have liked.

Let’s be a little bit honest here. Below, I’ve listed 10 things that you should be able to say that you did during 2018 that relate to how you should have handled your project finances. How many of these can you confidently say you did to the best of your ability?

1.I managed my project budget

It might seem odd to include this, but I still hear from project managers on an alarmingly regular basis, who say they don’t have any oversight or influence into the project budget. The financials are handled by other people. They only have to track and manage the project tasks.

This is wrong. So wrong, on so many levels. This attitude by management that implies project managers are not “good enough” to manage financial information undermines what we should be doing with the profession.

You should have access to the financial information relating to your project and you should be the person handling project finances. If you don’t do it personally, that could be because someone else in the project team does it, for example, if you are a project administrator and the project manager does it. Or you are the project manager and you have a project financial admin person on secondment from Finance who handles the tracking for you.

It should be someone on the immediate project team who you can talk to and who will tell you the truth about the numbers.

2.I set a project budget baseline

Did you set a baseline for project costs? A baseline is a snapshot in time that shows you the total of your project financials at a certain point.
You can see what should be included in your project budget in this article. All those items, added together, give you the total project budget. But they change over time. The baseline is a record of what your budget was at a given point.

It’s useful because you can use it to check how close you are to your original plans for spending.

3.I agreed a contingency amount with my sponsor

If you started a new project at some point in 2018, you should have had a conversation about contingency.

This is added to your budget (it’s part of your cost baseline). It’s a little cushion for emergencies, the amount of which you can make up based on your best guess or a standard % measure, or you can work it out more scientifically by looking at risks and calculating amount required to adequately address them.

Read more about the difference between management reserves and contingency reserves.

4.I tracked time

Project management time spent is an overhead for your project. You can work out the amount of time spent doing the managing if you track your time (as well as your team members). It’s tempting to log everything to a bucket task called ‘project management’ and book yourself at 100%. But that wouldn’t be accurate.

Try to track your own time a bit more realistically, splitting it down by work package, project stage, type of activity or something else.

It’s helpful to know how much effort it took to get a project off the ground, especially when you come to review benefits later. You can also include this information in the business case for future projects. It can help you better estimate the amount of management time required.

5.I celebrated success with my team

Hopefully you had something you could celebrate in 2018. And celebrating can be done on the cheap (read more about how to motivate your team with spending anything). But it’s nice to be able to reward your team with something that does cost money, however small.

Perhaps you took them out to lunch and the project paid. Or there was a launch event or something. Putting a small amount of money aside for celebrations is definitely a good thing.

6. I estimated accurately

Did you follow the estimating lifecycle?

While I’ve said in the title here: “I estimated…” I don’t actually mean you personally. I mean that you involved the right subject matter experts to get decent estimates. I mean that you used solid, robust estimating techniques to make good choices about how much your tasks were going to cost.

I hope you got support from your colleagues and created a budget built on estimates you could rely on.

7. I applied good governance

Governance for project budgets means you got approval to make changes, you understood and sought approval for spending management reserves and contingency funds as appropriate and you generally had good housekeeping for your financial records. Any changes that were made would most likely have downstream implications for other project documents, so hopefully you kept those up to date too.

8. I included financial data in project reports

Good governance can also cover proper reporting to your project board or steering committee.

I frequently talk to project managers who don’t put financial information into their project reports. I get it – it’s time consuming to update your financials (at least for me; we are between project management tools and have reverted to spreadsheets for budget management for now). But really, what exec isn’t interested in how much the project has spent to date and is forecasting to spend by completion?

Project financial information really should be in your monthly reports.

9. I worked with suppliers in a positive way

Hopefully, 2018 was not full of supplier disputes for you. Perhaps you formally closed some contracts. Perhaps you worked with your procurement teams to bring on board new suppliers. Perhaps there was a supplier selection exercise that you facilitated on behalf of your project customer.

There are lots of ways to work with suppliers – with any luck you built some positive working relationships that will carry you forward into 2019.

10. I had a risk budget and managed it

Risk budgets are a particular challenge for me. I don’t often have the luxury of time to properly work out what risk management actions should be taken and allocate the funding – at least not before we dive straight into the delivery.

However, if you can, calculating the risk budget is definitely worthwhile.

Can you say you hit all the points? And are you going to hit them again during 2019?

If some of these things weren’t on your personal achievements list, then that could be because they aren’t activities relevant to the role you are in, and that’s fine. However, I’d argue that most project managers should be able to say they did all of these. What else would you add? Let me know in the comments below!

Pin for later reading:

How do you define the right level of quality on your project? Your project sponsor probably has expectations you need to meet. Your team has a level to which they can deliver. You have to find a way to balance the competing needs and hit a quality level that suits as many people as you can.

At least, that’s a good approach if you want to avoid too many grumpy faces round the table at your project lessons learned meeting.

This infographic, inspired by a fantastic short little book on project management called Project-Driven Creation by Jo Bos, Ernst Harting and Marlet Hesslelink, sets out the three levels of project quality that you can reach for your deliverables.

Which one do you hit most often?

Read more about this topic in the article here.

Today’s deep dive into the PMBOK Guide®-- Sixth Edition is into the second part of Project Schedule Management: the Define Activities process. I’m going to call out the differences between this process and what we used to have in the PMBOK Guide® -- Fifth Edition.

The project schedule is the main output of the Project Schedule Management Knowledge Area (unsurprisingly) and the action really starts with Define Activities.

Define Activities Process

This is the second process in the Knowledge Area. We’re still in the Planning process group.

Basically, this process is about making an activity list, covering all the different activities that need to be done to complete the work of the project. There are some other outputs too – we’ll come to them in a minute. But think of this process as the creation of your master To Do list.

Inputs

There are some small changes to the Inputs between the PMBOK Guide® -- Fifth Edition and Sixth Edition. In the current edition, inputs are:

• Project management plan
• Enterprise environmental factors
• Organisational process assets.

The schedule management plan and scope baseline have been ditched. That makes sense: the project management plan is such a broad, wide-ranging document that you don’t really have to specify the component parts.

Tools & Techniques

The Tools and Techniques for this process have changed slightly – meetings has been added (and if you want to get picky, it looks to me like the order of tools and techniques has been shifted around), which makes no practical difference day to day.

The addition of meetings makes sense in the context of the Knowledge Area. You can’t decide on what needs to be done unless you talk to people who are going to be doing the work, and you’ll do that through a meeting. That meeting could be informal, formal, a phone call, with lots of people or with one person.

Frankly, I think adding meetings in is a little bit pointless as it should go without saying that you have to talk to an expert in order to use expert judgment as a technique. But the PMBOK Guide® -- Sixth Edition is nothing if not diligent in setting out the detail.

Outputs

There are two new outputs: Change requests and Project management plan updates.

The point of adding change requests in here is because you should already have a scope baseline in place. As you work through the activities, talk to the right people and so on, you may uncover extra work that needs to be done – or work that doesn’t need to be done. This would generate a change request to amend the baselined scope.

Project management plan updates is a generic catch-all type of output that is included as anything you might do to create a schedule may have some kind of impact on the plan. For example, you might need to update the schedule or cost baselines. Once a change is approved, you’ll have to make changes to those documents too.

Next time I’ll be looking at Sequence Activities.

Pin for later reading: