Project Cost Management often puts people off. It feels complicated and has the mystical air of mathematical magic and wizardry. But there’s little your project sponsor, your client, or their Finance Director care about more than your budget and how closely you can stick to it.
Project cost over-runs are common. But this is not a cause for a defeatist attitude.
No. Instead, you must act with determination to understand project cost management and implement all the tools at your disposal to control costs and bring in your expenditure on budget.
We know that projects have different priorities – best understood through the Iron Triangle of time, cost and quality. Some projects are all about delivering your scope to an absolute set of quality standards. And others have an absolutely firm deadline that makes schedule their essential priority.
But, for some projects, quality can flex a little, and timescales can slip if they must. What is not negotiable is the budget. Once set, you must respect it, and deliver to it.
So, in this feature article, we’ll look at:
Project Cost Management is a process that has two principle components:
The Project Management Institute’s (PMI’s) Project management Body of Knowledge (the PMBoK) has Project Cost Management as one of its ten Knowledge Areas (or KAs).
I view project cost management as a master process, which you would document in your Project Cost Management Plan. This sets out the ‘rules of the road’ for how you are going to establish and manage your project costs. It is one of two primary control documents for the financial aspects of your project – alongside your Business Case. We also have a large guide to the Project Business Case.
If your project will spend significant amounts of someone else’s money, you need to demonstrate that you can:
Your Project Cost Management Plan sets all that out. You can consider it either as a part of your project management plan, or as an associated document. Either way, you must ensure that all aspects integrate well and are entirely consistent.
Here are some of the things to include:
You’ll also want to add in whatever else your Project Management Office(PMO), your Project Board, or your Project Sponsor asks you to include
The PMBOK has two processes:
But these are so deeply intertwined, that I prefer to think of them together. It is not always clear how to allocate a tool or method to one or other of these processes.
Happily, we have already published another of our big guides on Estimating: it’s a big and important topic. Do take a look at it: Project Estimation: Master the Tools and Techniques. No doubt, we’ll do another on Budgeting soon, so watch this space, and there will be a link here too!
The outcome of estimating and budgeting will be a Budget that sets out your baseline costs. You will use this as the basis for:
Estimating and budgeting is best done task-by-task. For each task, create an estimate and then a budget figure, for each class of cost.
So, you’ll need a grid (spreadsheets like Excel, Numbers, or Google Sheets are perfect) with a list of tasks down the side, and a list of categories of cost along the top.
The best source of your task list is your Work Breakdown Structure* (WBS). By adding costs to every task, you will be creating a Cost Breakdown Structure.
The benefit of this approach is that, once you move into delivery stage, you will be able to track expenditure by task, and compare it directly to budget.
* Note that I learned my project management in the UK. Here, a WBS contains ‘work’ – that is tasks, or activities. In the US, for example, a WBS breaks down the work into products. This approach will also work as the basis of your budget, but is more complex, as often many tasks contribute to the delivery of one or more products. So this approach often requires both aggregation of task costs to product level, and disaggregation of accumulated costs among multiple tasks.
Typical categories of cost include:
You may also need to include indirect costs that can only partially be attributed to a specific project. Common exampes include:
When preparing your estimates and budget, there will be a lot of uncertainties. Important ones to remember include:
The PMI’s PMBOK is weak on governance throughout. So it is little surprise that it has nothing (that I can find) to say about the governance of Project Cost Management.
But, as always, the UK Government’s PRINCE2 methodology has governance as a key strength, and points us in the right direction.
Clearly your Project Board and Sponsor have a crucial role to play in the oversight of your spending. It should be on the Project Board’s standing agenda to review budget reporting, and I favor ensuring that one member of the Project Board has sufficient financial skills to competently monitor and advise Board colleagues on the financial situation. For a substantial project (in terms of expenditure, profile, or risk), I suggest this needs to be someone with a financial qualification.
Some UK Governmental projects appoint a Senior Finance Officer (SFO) to the biggest projects. These carry out the same level of oversight and have the same level of accountability as the Senior Responsible Officer (SRO – the Sponsor), but in the domain of the project’s finances. In other models, the SFO is an advisor to support the SRO. I recommend you give these kinds of model careful consideration. Especially if your project has a large expenditure and significant risk or profile.
The other hugely valuable contribution to financial governance that PRINCE2 mandates is through the Gateway Review process. This is also used in non-PRINCE2 projects, so is well worth considering. Here, the Stage Gate process links directly to the release of funding to the project. Tranches of budgeted funding can only be released for spending on successful completion of a stage gate review, and approval by the review team or the Project Board. You’ll find we have a full-length article on the Project Stage Gate Process – and why it will make you a better project manager.
These are your activities to keep your project on budget.
Tracking actual expenditure against your budget. Ideally, do this as near to real-time as you can. The more your project is spending, the more frequently you need to monitor.
Taking corrective actions is expenditure looks like it will exceed budget or has already done so.
For most small projects, if I’m honest, a spreadsheet will do! But this approach is fraught with risks. If you are leading a larger project, you need a tool built for the job.
This type of tool is called a Project Management Information System (or PMIS – careful how you say it!). There are many varieties.
It is way (way, way) beyond the scope of this article to review the options out there. But for project cost management, you need a tool that can:
all of your financial data. And ideally, it will be easy to use and integrate well with other essential project management systems and process you use.
Another topic that is outside the scope of this article is EVM – sometimes known as EVA (Earned Value Analysis). This is a powerful toolkit for analysing budget and schedule performance, and their variances against each other. It also allows you to project trends and calculate forecasts to completion.
One particularly widely used figure is the To-Complete Performance Index (TCPI). This is a measure of how the remaining budget compared to the work you still need to do. A number bigger than 1 will mean you have more budget than you expected to need, when you prepared your budget. If it’s smaller than one, you’ll need to create savings by working more efficiently or economically than you planned.
Whatever methodology you use, you may need to prepare an assessment of your expenditure through time. This will give you a trend, form which you’ll need to forecast out-turn expenditure. If your estimated cost at completion exceeds your budget, you have two choices:
This is why you need a Project Cost Management Plan and good governance. Your plan should give you the answer to this question. At the very least, I always say that you need to notify your sponsor and Board if this is the case.
Reporting is a key adjunct to your monitor and control process. You need to report on:
We have also written a feature article on Reporting that will set your budget reporting in a wider context, as well as showing why it is so important.
As project managers, we never expect everything togo perfectly smoothly! So you’ll be needing to make a number of updates to project documentation and control tools throughout your project lifecycle.
Common updates that will stem from monitoring your project costs include:
The need to make changes will create a need to adjust your budget and forecasts. So your Change Control process will need to integrate fully with your project cost control. We have written another one of our giant guides about Change Control.
Finally, as we start to run out of space (can you do that on a web page? …Ed), I wan to briefly address the need to tailor your project cost management approach to the nature of your specific project.
Always scale your cost management process to match scale and risk of your project. A lot of the tools and methods are irrelevant to small projects. But likewise, for the largest projects, you’ll need sophisticated software tools to give you any chance of keeping track of your project spending. And they will need to be robust enough to provide the quality of audit trail your finance department mandates.
I’ve written much of this article to assume your project will take a Predictive, or planned approach. But what if you need to use an Adaptive (Agile) methodology?
Here, you’ll want a more light-touch estimation process. You cannot abandon estimating altogether. That would make it impossible for the sponsoring organization to make a robust decision. But you can use high-level approaches to make ‘order of magnitude estimates’ as a basis of informed decision-making.
Later, you can then make more detailed estimates at each iteration, to harness the greater levels of certainty over short-term planning horizons
Do let me know your experiences, your favorite tools, or any questions you have. I will respond to any comments below.
Dr Mike Clayton is one of the most successful and in-demand project management trainers in the UK. He is author of 13 best-selling books, including four about project management. He is also a prolific blogger and contributor to ProjectManager.com and Project, the journal of the Association for Project Management. Between 1990 and 2002, Mike was a successful project manager, leading large project teams and delivering complex projects. In 2016, Mike launched OnlinePMCourses.
Please log in again. The login page will open in a new window. After logging in you can close it and return to this page.