Differenze tra le versioni di "Managing Business Case"
(Etichetta: visualeditor) |
|||
| Riga 1: | Riga 1: | ||
Project management best practices recommend that, in many circumstances, a business case should be established for the ''[[glossary|project]]''. | Project management best practices recommend that, in many circumstances, a business case should be established for the ''[[glossary|project]]''. | ||
| − | The key sections and components of a business case may be: executive summary, reasons, business options, expected benefits, expected dis-benefits, timescale, costs, investment appraisal and major risks. See the | + | The key sections and components of a business case may be: executive summary, reasons, business options, expected benefits, expected dis-benefits, timescale, costs, investment appraisal and major risks. See the table next to learn how this elements could be arranged within itmSUITE®. |
| + | There can be different approaches with different levels of complexity. | ||
| + | |||
| + | ''Basic approach'' | ||
| + | |||
| + | The business case is managed as a document. As such it is stored in the ''<u>Documents</u>'' section of the ''[[glossary|project]]'' (see [[Documents management|document management guide]] for more information). Some information (e.g. background and reasons) may also be copied and recorded in ''[[glossary|project]]'' specific fields (e.g. <u>Objectives</u> and <u>Background and Reasons</u> in ''<u>General</u>'' section). | ||
| + | |||
| + | ''Business case as a key [[glossary|project milestone]]'' | ||
| + | |||
| + | In this scenario a ''[[glossary|project milestone]]'' is used to store the information about the business case and its approvals. A ''[[glossary|project milestone]]'' category ('''''General/Projects/Milestones''''') could be created to classify business case reviews. The business case document is stored in the ''[[glossary|project milestone]]'' ''<u>Documents</u>'' section and its information could also be copied and recorded in | ||
| + | |||
| + | oject or project milestone specific fields.r | ||
{| class="wikitable" | {| class="wikitable" | ||
! Business case element !! How to manage | ! Business case element !! How to manage | ||
Versione delle 07:02, 5 apr 2016
Project management best practices recommend that, in many circumstances, a business case should be established for the project.
The key sections and components of a business case may be: executive summary, reasons, business options, expected benefits, expected dis-benefits, timescale, costs, investment appraisal and major risks. See the table next to learn how this elements could be arranged within itmSUITE®.
There can be different approaches with different levels of complexity.
Basic approach
The business case is managed as a document. As such it is stored in the Documents section of the project (see document management guide for more information). Some information (e.g. background and reasons) may also be copied and recorded in project specific fields (e.g. Objectives and Background and Reasons in General section).
Business case as a key project milestone
In this scenario a project milestone is used to store the information about the business case and its approvals. A project milestone category (General/Projects/Milestones) could be created to classify business case reviews. The business case document is stored in the project milestone Documents section and its information could also be copied and recorded in
oject or project milestone specific fields.r
| Business case element | How to manage |
|---|---|
| Business case document and approval | |
| Executive summary | |
| Reasons | |
| Business options | |
| Expected benefits | |
| Executive dis-benefits | |
| Timescale | |
| Costs | |
| Investment appraisal | |
| Major risks |
