The quantities entered in a project business case can move after the budget is approved: a quote is revised, roll-out falls behind, an activity volume is not borne out. A case read only once then risks describing a project that no longer exists.
This document, also called an investment case or business justification, measures, in the reading we propose, four things: the full cost of the project, the expected benefits by type, the time it takes for them to arrive, and the risks weighing on the first three. Each measure is established according to written conventions, is entrusted to a person who will keep it up to date beyond the launch, and has its limit. The financial summary (net present value, payback period or another instrument) is then calculated, according to the finance department’s rules. Our article on the ROI of artificial intelligence describes its conventions on a particular case; the subject here is the measures that feed it.
Full cost, beyond the project budget
The budget requested from the committee may cover only delivery. Full cost adds what the organisation will pay elsewhere: the time of internal teams, including that of users involved in design, acceptance testing and training; the period during which the old and new systems run together; operation and maintenance over the calculation horizon; the retirement of what the project replaces.
It is established item by item, each with its assumption and its source: a quote, a price list, an effort estimated by those who will do the work. Conventions are written down with the figure: the horizon chosen, whether or not internal time is valued, the contingency. A range, wide at framing and then narrowed as studies progress, is more informative than a single amount.
We propose entrusting this measure to the project manager during the project, with management control validating its conventions. At closure, the operation line passes to the department that will run the result, and its name appears in the case from the framing stage.
Taken alone, this cost compares with nothing. Not doing the project also has a cost (maintenance of an ageing system, a contract to renew), and the case costs this baseline option in the same way as the others.
Expected benefits, classified by type
A total of benefits adds up elements that are not observed in the same place. The case benefits from presenting them by type, according to a classification we propose here and that each organisation adjusts.
| Type of benefit | How it is established | Where it is observed | Its limit |
|---|---|---|---|
| New revenue or eliminated spending | Expected change in a designated budget line, compared with its starting value | In the accounts of the benefiting department | The line also varies for reasons other than the project |
| Avoided spending | Cost the baseline option would have incurred: a contract to renew, equipment to replace | In no account: it rests on the baseline scenario | It is worth what that scenario is worth |
| Time freed up | Hours estimated on a process measured before the project | In the decision that reallocates these hours | As long as nobody reallocates them, no account shows it |
| Measurable non-financial effect | Indicator tracked by the business, with its starting value and target: processing time, complaints | On the indicator, after go-live | It cannot be added to the amounts |
| Compliance | Designation of the obligation and its deadline | On the date the obligation is met | The gain does not ground the decision: the case compares ways of meeting it |
We propose that each line carry the name of a business owner, outside the project team, who commits to the starting value, the target and the date of observation. The project manager delivers what makes the benefit possible; obtaining it falls to those whose work changes.
Two projects can claim the same benefit. The duplication becomes visible when the cases are read side by side, at portfolio level, whose vocabulary is set out in our entry on PPM.
The timing of benefits and the risks of the case
The timing that counts in the case runs beyond go-live. A benefit arrives when the result is used: after roll-out, adoption, sometimes the shutdown of the old tool. The case therefore carries, for each benefit, a start date and a gradual ramp-up, established with the business owner on the basis of the roll-out plan.
This measure depends on the schedule: it shifts by as much as go-live slips, and the project manager updates it at each replanning. What happens after the chosen horizon is beyond it.
The risks of the case are distinct from the project’s risk register, covered in our article on project risk management. They concern the assumptions of the other three measures: an activity volume, a price, a level of adoption, the delivery date of another project. They are established by listing these assumptions, then redoing the calculation with an unfavourable value for each, one at a time. Those that reverse the conclusion are to be checked first, then monitored.
We propose that the sponsor own this list, since they defend the case. It quantifies no probability. It shows what the justification depends on, which is enough to identify the points to review.
A project business case reviewed at each decision point
In the allocation we propose, the case has an owner, the sponsor, and each measure has its own: cost falls to the project manager and then to the operating department, benefits to the business owners, conventions to management control. The project office, or the portfolio body, keeps the review calendar.
The review takes place at the points where the organisation can still change its mind: end of framing, commitment to delivery, go-live, then the dates for observing benefits. Among its principles, the PRINCE2 method includes continued business justification, under which the business case is re-examined at each stage. At each review, the case sets the remaining spend against what remains to be obtained: this is the first question covered in our article on the project review.
The case remains open after project closure. Benefits may be observed later, once the team has been disbanded: the review then falls to the body that arbitrates the portfolio. Our page on project portfolio management describes this mechanism, from the benefit assumptions written at launch to their verification after delivery.
When the case and what the teams report diverge, or before a major commitment, an independent examination can take the assumptions back to their source. Our page on project audit includes the project’s rationale among its angles of examination.
Finally, a business case judges a project against its own options. Knowing whether it is the best use of resources requires comparing it with other projects, which belongs to the portfolio.
The case is closed on the day the last benefit entered has been observed, or abandoned in writing. This date, and the name of the person who will pronounce it, appear from the first version.