Managing Business Case - Cronologia

Maxime.sottini: /* Business case elements and how to manage */

2016-04-05T15:06:06Z

‎Business case elements and how to manage

Maxime.sottini: /* Business case elements and how to manage */

2016-04-05T09:15:42Z

‎Business case elements and how to manage

Maxime.sottini: /* Business case elements and how to manage */

2016-04-05T08:14:49Z

‎Business case elements and how to manage

Maxime.sottini: /* Business case elements and how to manage */

2016-04-05T07:46:28Z

‎Business case elements and how to manage

Maxime.sottini: /* Business case elements and how to manage */

2016-04-05T07:38:59Z

‎Business case elements and how to manage

Maxime.sottini: /* Business case elements and how to manage */

2016-04-05T07:36:24Z

‎Business case elements and how to manage

Maxime.sottini: /* Business case elements and how to manage */

2016-04-05T07:35:57Z

‎Business case elements and how to manage

Maxime.sottini: /* Business case managed through a workflow */

2016-04-05T07:33:16Z

‎Business case managed through a workflow

Maxime.sottini: /* Business case managed through a workflow */

2016-04-05T07:32:32Z

‎Business case managed through a workflow

Maxime.sottini il 07:17, 5 apr 2016

2016-04-05T07:17:12Z

@@ Riga 52: / Riga 52: @@
 |-
-| Major risks ||This information can be managed in the business case document. See also [[Project risks|project risk management guide]] for more information.
+| Major risks ||This information can be managed in the business case document. See also [[Project risks|project risk management guide]] for alternative options.
 |}

@@ Riga 49: / Riga 49: @@
 If the business case is managed as a ''[[glossary|project milestone]]'', the cost information can be saved with an ''[[glossary|estimation]]'' related to the ''[[glossary|project milestone]]''. Customized reporting can be designed and implemented using the [[REP - Reporting module]].
 |-
-| Investment appraisal ||This information can be managed in the business case document. Some Key Performance Indicator
+| Investment appraisal ||This information can be managed in the business case document. Some Key Performance Indicators (e.g. Earn) are available in together with the estimation which can be saved with a ''[[glossary]]''.  Customized reporting can be designed and implemented using the [[REP - Reporting module]].
 |-
-| Major risks ||
+| Major risks ||This information can be managed in the business case document. See also [[Project risks|project risk management guide]] for more information.
 |}

@@ Riga 15: / Riga 15: @@
 == Business case managed through a [[glossary|workflow]] ==
 A third and more flexible (although more complex approach) is to manage the business case (and its approval) through a ''[[glossary|workflow]]''. This requires that the [[SM - Service Desk and Service Management|SM - Service Desk and Service Management module]] is activated as a prerequisite. This allows to manage all the business case information and  related process steps although it requires a specific configuration.
 == Business case elements and how to manage ==
@@ Riga 34: / Riga 37: @@
 |-
-| Expected benefits ||This information can be managed in the business case document itself. A high level description of the benefits could be included in the <u>''General''</u> section field <u>Reasons</u>. However an alternative approach is possible by defining and using a specific ''[[glossary|workflow]]'' to manage the benefits lifecycle. However, this requires the [[SM - Service Desk and Service Management|SM - Service Desk and Service Management module]] and the configuration of the ''[[glossary|workflow]]''. Ad hoc reporting can be designed by using the [[REP - Reporting module]].
+| Expected benefits ||This information can be managed in the business case document itself. A high level description of the benefits could be included in the <u>''General''</u> section field <u>Reasons</u>. However an alternative approach is possible by defining and using a specific ''[[glossary|workflow]]'' to manage the benefits lifecycle. However, this requires the [[SM - Service Desk and Service Management|SM - Service Desk and Service Management module]] and the configuration of the ''[[glossary|workflow]]''. Customized reporting can be designed and implemented using the [[REP - Reporting module]].
 |-
@@ Riga 43: / Riga 46: @@
 |-
-| Costs || If the business case is managed as a project milestones the project Activities section information (the project gantt) can be saved with an estimation related to the project milestone.
+| Costs || This information can be managed in the business case document or with a dedicated one.
 |-
-| Investment appraisal ||
+| Investment appraisal ||This information can be managed in the business case document. Some Key Performance Indicator
 |-

@@ Riga 40: / Riga 40: @@
 |-
-| Timescale ||This information can be managed in the business case document itself. However, if the business case is managed as a project milestones Costs
+| Timescale ||This information can be managed in the business case document or with a dedicated one.
 |-
 | Investment appraisal ||

@@ Riga 40: / Riga 40: @@
 |-
-| Timescale ||This information can be managed in the business case document itself. However, if the business case is managed
+| Timescale ||This information can be managed in the business case document itself. However, if the business case is managed as a project milestones Costs
 ||

@@ Riga 5: / Riga 5: @@
 There can be different approaches with different levels of complexity.
-== ''Business case as a document and informationsic approach'' ==
+== ''Business case as a document and information'' ==
 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).
@@ Riga 37: / Riga 37: @@
 |-
-| Expected dis-benefits ||See
+| Expected dis-benefits ||See expected benefits.
-ected benefitsx
+|-
-|-
+a project milestones
 |-

@@ Riga 1: / Riga 1: @@
 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 table next to learn how this elements could be arranged within itmSUITE®.
+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.
 There can be different approaches with different levels of complexity.
@@ Riga 13: / Riga 13: @@
 The <u>Status</u> of the ''[[glossary|project milestone]]'' (e.g. "Executed") and its <u>Result</u> (e.g. "Ok") may represent the status of the business case approval.
-== Business case managed through a workflow ==
+== Business case managed through a [[glossary|workflow]] ==
-A third and more flexible (although more complex approach) is to manage the business case (and its approval) through a ''[[glossary|workflow]]''.
+A third and more flexible (although more complex approach) is to manage the business case (and its approval) through a ''[[glossary|workflow]]''. This requires that the [[SM - Service Desk and Service Management|SM - Service Desk and Service Management module]] is activated as a prerequisite. This allows to manage all the business case information and  related process steps although it requires a specific configuration.
 {| class="wikitable"
 ! Business case element !! How to manage
 |-
-| Business case document and approval ||
+| Business case document and approval || The business case information and approval can be managed according to one of the previously described alternative approaches (as a document, via ''[[glossary|project milestones]]'' or via ''[[glossary|workflow]]'').
 |-
-| Executive summary ||
+| Executive summary ||This information is typically managed with <u>''General''</u> section fields <u>Objectives</u> and <u>Background and Reasons</u> or in the business case document itself.
 |-
-| Reasons ||
+| Reasons ||This information is typically managed with ''<u>General</u> ''section field <u>Reasons</u> or in the business case document itself.
 |-
-| Business options ||
+| Business options ||This information is typically managed in the business case document itself.
 |-
-| Expected benefits ||
+| Expected benefits ||This information can be managed in the business case document itself. A high level description of the benefits could be included in the <u>''General''</u> section field <u>Reasons</u>. However an alternative approach is possible by defining and using a specific ''[[glossary|workflow]]'' to manage the benefits lifecycle. However, this requires the [[SM - Service Desk and Service Management|SM - Service Desk and Service Management module]] and the configuration of the ''[[glossary|workflow]]''. Ad hoc reporting can be designed by using the [[REP - Reporting module]].
 |-