Business::business Project::benefits Costs::should Expected::include Process::analysis Elements::sector
A business case captures 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 argument or presentation. The logic of the business case is that, whenever resources such as money or effort are consumed, they should be in support of a specific business need. An example could be that a software upgrade might improve system performance, but the "business case" is that better performance would improve customer satisfaction, require less task processing time, or reduce system maintenance costs. A compelling business case adequately captures both the quantifiable and non-quantifiable characteristics of a proposed project. Business case depends on business attitude and business volume.
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. Note that it is not the job of the project manager to build the business case, this task is usually the responsibility of stakeholders and sponsors.<ref name="ref1">Building a Project’s Business Case PM Hut, 8 January 2009</ref>
Business case sections
Intro Reasons for creating a business case Development and approval process Not Public sector projects See also Notes References External Links
|PREVIOUS: Intro||NEXT: Reasons for creating a business case|