The purpose of a business case is to capture the reasoning for initiating a project or task. It is often presented in a well-structured written document, but may also sometimes come in the form of a short verbal argumentation. The logic of the business case is that any time resources such as money or effort are consumed, they should be in support of the business. An example could be that a software upgrade might improve system performance but the “business case” is that better performance would improve customer satisfaction.
Business cases can range from comprehensive and highly structured, as required by formal project management methodologies, to informal and brief.
Information included in a formal business case could be the background of the project, the expected business benefits, the options considered (with reasons for rejecting or carrying forward each option), the expected costs of the project, a gap analysis and the expected risks.
Consideration should also be given to the option of doing nothing including the costs and risks of inactivity. From this information, the justification for the project is derived.
The Business Case is updated constantly for the justification of the project. Each time a stage of the project is finished, the Business Case will be updated according to the revised planning and is assessed whether it still makes sense for the project to proceed.
To perform the Prince2 Health Check for the Business Case, click here!
These are the questions to answer:
Related posts:
no comments yet.
Behind the scenes: Prince2 Risk Health Check explained »« Behind the scenes: Organisation Health Check explained
Names and email addresses are required (email addresses aren't displayed), url's are optional.
Comments may contain the following xhtml tags:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>