Skip to content

good practice and innovation
about us infoKits Tools & Techniques Publications Events
You are here: Home » infoKits » Project Management infoKit » The Business Case

p3m What is P3M? Project Management Banner

PRINCE2

In PRINCE2 methodology, development of the business case relates to the following sub-processes:

  • Preparing a Project Brief (SU4)
  • Authorising Initiation (DP1)
  • Refining the Business Case and Risks (IP3)
  • Authorising a Project (DP2)
  • Updating a Project Business Case (SB3)
  • Authorising a Stage or Exception Plan (DP3)
  • Examining Project Issues (CS4)
  • Identifying Follow-on Actions (CP2)
  • OGC PRINCE2 website

The Business Case

Preparing a Business Case need not necessarily be a lengthy or difficult exercise. The amount of time worth spending on this is necessarily related to the likely scale and cost of the project. Even if you are faced with the second of the above scenarios, where the project is already something of a fait accompli, it is worth drafting a short outline and confirming with your sponsor that this is indeed what they have in mind. As a minimum this would summarise what you are doing, why you are doing it and what alternatives exist.

The Business Case is an important document as it states what the project is intended to achieve. Throughout the life of the project as you come to the end of each stage, this document is referred to as a basis for deciding:

  • can the business case still be achieved?

  • does the business case need updating?

  • should the project continue?

In a worst case scenario it may be that a management group has decided on a course of action without adequately exploring whether this is necessarily the most effective way forward or whether it will adequately meet the identified needs. An alternative, and equally likely scenario, is that it has set time and cost limits in advance of a proper analysis of what the project involves. To be fair, especially in relation to systems implementations, such optimism can often be provoked by the claims of vendor sales teams and consultants about how easy it is to apply their 'standard' implementation methodology in your institution. In these cases the business case should state the reasons why alternatives weren't fully explored or the fact that time and cost estimates may need to be revised once proper planning is under way. Statistical data or other evidence from colleagues in the sector can help to make your case. Hopefully this will be sufficient to make your sponsor pause for thought and consider the best way forward. If nothing else it will at least give you some protection when you have to go back and tell them that things aren't going to work out quite like they thought.

Resources


Bookmark and Share
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)