PRINCE2 Agile 2016
Previous Section   Next Section

A.2 Business case

A.2.1 Purpose

A business case is used to document the justification for the undertaking of a project, based on the estimated costs (of development, implementation and incremental ongoing operations and maintenance costs) against the anticipated benefits to be gained and offset by any associated risks. It should outline how and when the anticipated benefits can be measured.

The outline business case is developed in the Starting up a Project process and refined by the Initiating a Project process. The Directing a Project process covers the approval and re-affirmation of the business case.

The business case is used by the Controlling a Stage process when assessing impacts of issues and risks. It is reviewed and updated at the end of each management stage by the Managing a Stage Boundary process, and at the end of the project by the Closing a Project process.

A.2.2 Composition

  • Executive summary Highlights the key points in the business case, which should include important benefits and the return on investment (ROI)
  • Reasons Defines the reasons for undertaking the project and explains how the project will enable the achievement of corporate strategies and objectives
  • Business options Analysis and reasoned recommendation for the base business options of: do nothing, do the minimum or do something
  • Expected benefits The benefits that the project will deliver expressed in measurable terms against the situation as it exists prior to the project. Benefits should be both qualitative and quantitative. They should be aligned to corporate or programme benefits. Tolerances should be set for each benefit and for the aggregated benefit. Any benefits realization requirements should be stated
  • Expected dis-benefits Outcomes perceived as negative by one or more stakeholders. Dis-benefits are actual consequences of an activity whereas, by definition, a risk has some uncertainty about whether it will materialize. For example, a decision to merge two elements of an organization onto a new site may have benefits (e.g. better joint working), costs (e.g. expanding one of the two sites) and dis-benefits (e.g. drop in productivity during the merger). Dis-benefits need to be valued and incorporated into the investment appraisal
  • Timescale Over which the project will run (summary of the project plan) and the period over which the benefits will be realized. This information is subsequently used to help timing decisions when planning (project plan, stage plan and benefits review plan)
  • Costs A summary of the project costs (taken from the project plan), the ongoing operations and maintenance costs and their funding arrangements
  • Investment appraisal Compares the aggregated benefits and dis-benefits to the project costs (extracted from the project plan) and ongoing incremental operations and maintenance costs. The analysis may use techniques such as cash flow statement, ROI, net present value, internal rate of return and payback period. The objective is to be able to define the value of a project as an investment. The investment appraisal should address how the project will be funded
  • Major risks Gives a summary of the key risks associated with the project together with the likely impact and plans should they occur.
Previous Section   Next Section