Throughout a project it is easy to lose track of 'why' the project needs to be done. The Business Case states why the work is worth doing and because of this it is a crucial part of a project.
Given the information available at the start of a project the outline of the business case is likely to be only a high level view. It provides a foundation for a more extensive and detailed business case development in the initiating a project process.
PRINCE2 suggests the following actions:
Executive to draft the outline Business Case based on what is currently known about the project:
✔ Understand the objectives of, and the reasons for, the project as defined in the project mandate
✔ Understand how the project will contribute toward corporate and/or programme objectives
✔ Understand how the project will be funded
✔ Review the Lessons Log for lessons related to business justification
✔ Check for any standards mandated for the format and presentation of the Business Case (templates, cost metrics etc.)
✔ Assemble any relevant background information, e.g. contracts, feasibility reports, service level agreements etc.
✔ If necessary, seek approval of the outline Business Case from corporate or programme management
Project Manager to consult with the Senior User and Executive to define what the project is to deliver, and create the Project Product Description:
✔ Capture the customer's quality expectations
✔ Capture and agree the project's acceptance criteria
✔ Check feasibility of the timescale requirements from the project mandate or as reqUired by the outline Business Case
✔ Determine any key milestones
✔ Review the risks captured in the Daily Log and summarize the key risks affecting viability of the project in the outline Business Case.
