Business Case
[The introduction of the Business Case should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Business Case.]
[To give a context to the reader, briefly describe the product that is to be developed. Include the name of the system and possibly an acronym, if one is used. Explain what problem it solves and why the development will be worth the effort. Refer to the Vision document.]
[Define the business context for the product. In which domain is it going to function (for example, telecom or bank) and what market who are the users? State whether the product is being developed to fulfill a contract or if it is a commercial product. If it is a continuation of an existing project, this should also be mentioned.]
[State the objectives for developing the product the reasons why this is worthwhile. This includes a tentative schedule, and some assessment of schedule risks. Clearly defined and expressed objectives provide good grounds for formulating milestones and managing risks; that is, keeping the project on track and ensuring its success.]
[An example of a possible cost-benefit analysis table is shown below.]
Financial Forecast - <n> years |
Value |
Totals |
Benefits |
|
|
|
[revenue enhancement] |
$ |
|
|
[expense reduction] |
$ |
|
|
[intangibles (good will, visibility)] |
$ |
$ |
|
|
|
|
Costs |
|
|
|
[capital] |
$ |
|
|
[expense] |
$ |
$ |
|
|
|
|
ROI (benefits/costs) |
|
% |
[Express the constraints under which the project is undertaken. These constraints impact risk and cost. They could be things like external interfaces that the system must adhere to, standards, certifications or a technical approach employed for strategic reasons, such as using a certain database technology or distribution mechanisms.]