The definition of a project is (as per the APM Body of Knowledge 6th Edition) “a unique, transient endeavour, undertaken to achieve planned objectives, which could be defined in terms of outputs, outcomes or benefits. A project is usually deemed to be a success if it achieves the objectives according to their acceptance criteria, within an agreed timescale and budget.” This means that a project is trying to change something or create something. Working back from this, the creation of a project means that something has been identified that needs to be changed or indeed needs to be created. Project Business Cases are documents that captures the WHY of the project. Why is the project required? Project Business Cases do not delve deep into the how, when, where, who etc as this is all part of the Project Management Plan (or PMP for short).
Note, Project Business Cases can often be called different things. They have been referred to as Project Brief, Project Charter, High-Level Project Plan and others.
Whatever the Business Case is called, its reason for being is to clearly show WHY the project should be created. It should provide enough justification to senior managers within the organisation so that they can assess and give the project the go-ahead.
The Business Case is owned by the Project Sponsor. Not the Project Manager. It is the highest-level justification for beginning a project. Projects should be endorsed at a high-level by the Project Sponsor who should effectively “own” the project. It is that person who also owns the benefits of the project and provides the crucial link between the project and the overall business. The Business Case will show how the project contributes to, and supports, the corporate strategy. Projects should sustain or increase the competitive advantage of an organisation.
As we have noted, Project Business Cases outline the WHY behind a project. For this reason, it is clear that the Business Case should be the very first thing produced. The project should not be authorised without a Business Case. In fact, it is the very document that will be presented to the board (or project authorizing group) in order to get permission to start and to devote resources to producing a comprehensive Project Management Plan.
Quite often, an organisation will have a standard way, or template, for writing a Business Case. In organisations that are fairly advanced with their Project Management processes and have embedded best-practice, the Business Case template will have been designed to include the key bits of information that the board (or project authorising body) need, or want, in order to fully assess and authorize a project’s suitability for the specific organisation.
However, typically, there are common key parts that should be included. These are:
Every project is boundaried by TIME / COST / QUALITY requirements. It is crucial to identify these within a Business Case. In the real world boundaries often shift, minds are changed and goalposts move. It is incredibly difficult to deliver a successful project with moving goalposts. One way of stopping them move is having them clearly identified at the very start within the Business Case.