Change Management - Cronologia

Maxime.sottini il 15:01, 10 mag 2016

2016-05-10T15:01:39Z

Maxime.sottini: /* Operational model */

2016-05-10T15:00:14Z

‎Operational model

Maxime.sottini il 14:59, 10 mag 2016

2016-05-10T14:59:02Z

Andreas.munteanu il 14:43, 10 mag 2016

2016-05-10T14:43:55Z

Andreas.munteanu: /* Services */

2016-05-09T13:35:55Z

‎Services

Andreas.munteanu: /* Services */

2016-05-09T13:22:25Z

‎Services

Andreas.munteanu: /* Services */

2016-05-09T13:20:28Z

‎Services

Maxime.sottini: /* Views */

2015-10-13T14:20:24Z

‎Views

Maxime.sottini il 08:34, 24 lug 2015

2015-07-24T08:34:13Z

Maxime.sottini il 08:31, 24 lug 2015

2015-07-24T08:31:23Z

Mostra modifiche

@@ Riga 1: / Riga 1: @@
-''[[Glossary|Change Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process according to the ITIL and ISO/IEC 20000 guidelines.
+''[[Glossary#C|Change Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process according to the ITIL and ISO/IEC 20000 guidelines.
 Of course the preconfigured process (the ''[[Glossary|workflow cartridge]]'') is just an accelerator and the tuning / completion of the initial configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.
@@ Riga 8: / Riga 8: @@
 The preconfigured process has the objective to facilitate and support the effective and efficient execution of ''[[Glossary#C|changes]]''. At the core of the process configuration is the following operational model.
 [[File:Change Management Operational Model v1.0.JPG|centre|thumb|800x800px|Change Management operational model]]
-The requester, an authorized ''[[Glossary|client]]'', service manager, member of the ''[[Glossary|service desk]]'' or technical team or n related process (such as [[Glossary|''Incident Management'']] or ''[[Glossary|Problem Management]]'') requires to open a ''[[Glossary|Request for Change]]'' (RfC). The service manager takes in charge it and assigns an owner who coordinates all the tasks needed to fulfil the ''[[Glossary|change]]''. The owner requests the ''[[Glossary|change]]'' authorization to the ''[[Glossary|change authority]]'', if needed. As appropriate, technical team members may directly implement and deploy the ''[[Glossary|change]]'' or make it through the ''[[Glossary|Release Management]]'' process and later the ''[[Glossary|Depolyment Change]]''.
+The requester, an authorized ''[[Glossary|client]]'', service manager, member of the ''[[Glossary|service desk]]'' or technical team or n related process (such as [[Glossary#I|''Incident Management'']] or ''[[Glossary|Problem Management]]'') requires to open a ''[[Glossary|Request for Change]]'' (RfC). The service manager takes in charge it and assigns an owner who coordinates all the tasks needed to fulfil the ''[[Glossary|change]]''. The owner requests the ''[[Glossary|change]]'' authorization to the ''[[Glossary|change authority]]'', if needed. As appropriate, technical team members may directly implement and deploy the ''[[Glossary|change]]'' or make it through the ''[[Glossary|Release Management]]'' process and later the ''[[Glossary|Depolyment Change]]''.
 == Roles ==

@@ Riga 6: / Riga 6: @@
 == Operational model ==
-The preconfigured process has the objective to facilitate and support the effective and efficient execution of ''[[Glossary#|changes]]''. At the core of the process configuration is the following operational model.
+The preconfigured process has the objective to facilitate and support the effective and efficient execution of ''[[Glossary#C|changes]]''. At the core of the process configuration is the following operational model.
 [[File:Change Management Operational Model v1.0.JPG|centre|thumb|800x800px|Change Management operational model]]
 The requester, an authorized ''[[Glossary|client]]'', service manager, member of the ''[[Glossary|service desk]]'' or technical team or n related process (such as [[Glossary|''Incident Management'']] or ''[[Glossary|Problem Management]]'') requires to open a ''[[Glossary|Request for Change]]'' (RfC). The service manager takes in charge it and assigns an owner who coordinates all the tasks needed to fulfil the ''[[Glossary|change]]''. The owner requests the ''[[Glossary|change]]'' authorization to the ''[[Glossary|change authority]]'', if needed. As appropriate, technical team members may directly implement and deploy the ''[[Glossary|change]]'' or make it through the ''[[Glossary|Release Management]]'' process and later the ''[[Glossary|Depolyment Change]]''.

@@ Riga 6: / Riga 6: @@
 == Operational model ==
-The preconfigured process has the objective to facilitate and support the effective and efficient execution of ''[[Glossary|changes]]''. At the core of the process configuration is the following operational model.
+The preconfigured process has the objective to facilitate and support the effective and efficient execution of ''[[Glossary#|changes]]''. At the core of the process configuration is the following operational model.
 [[File:Change Management Operational Model v1.0.JPG|centre|thumb|800x800px|Change Management operational model]]
 The requester, an authorized ''[[Glossary|client]]'', service manager, member of the ''[[Glossary|service desk]]'' or technical team or n related process (such as [[Glossary|''Incident Management'']] or ''[[Glossary|Problem Management]]'') requires to open a ''[[Glossary|Request for Change]]'' (RfC). The service manager takes in charge it and assigns an owner who coordinates all the tasks needed to fulfil the ''[[Glossary|change]]''. The owner requests the ''[[Glossary|change]]'' authorization to the ''[[Glossary|change authority]]'', if needed. As appropriate, technical team members may directly implement and deploy the ''[[Glossary|change]]'' or make it through the ''[[Glossary|Release Management]]'' process and later the ''[[Glossary|Depolyment Change]]''.

@@ Riga 20: / Riga 20: @@
 * Opens ''[[Glossary|requests for change]]'' on behalf of himself/herself or for a third party
 ||  This role is mapped on:
-* a system ''[[Glossary|resource]] ''with ''[[Glossary|user]] ''of ''[[Glossary|user type]] ''"Requester". The login identifier of this ''[[Glossary|user]] ''is "FinalUser";
+* a system ''[[Glossary#R|resource]] ''with ''[[Glossary#U|user]] ''of ''[[Glossary|user type]] ''"Requester". The login identifier of this ''[[Glossary|user]] ''is "FinalUser";
 * service manager (see after);
 * service desk members (system ''[[Glossary|resources]] ''with ''[[Glossary|user]] ''of ''[[Glossary|user type]] ''"Resource"; the login identifier of this ''[[Glossary|user]] ''is "SDSpecialist";
@@ Riga 94: / Riga 94: @@
 * Takes in charge and assigns the change owner
 * Monitors how the ''[[Get started with itmSUITE®|changes]]'' are evolving for the ''[[Glossary|service(s)]]'' he/she is responsible for
-|| This role is mapped on a system ''[[Glossary|resource]] ''with ''[[Glossary|user]] ''of ''[[Glossary|user type]] ''"Project/Service Manager". There are different service managers configured for specific ''[[Glossary|services]]''. See [[Incident Management#Services|Services]] section in this page for further information.
+|| This role is mapped on a system ''[[Glossary|resource]] ''with ''[[Glossary|user]] ''of ''[[Glossary|user type]] ''"Project/Service Manager". There are different service managers configured for specific ''[[Glossary|services]]''. See [[Change Management#Services|Services]] section in this page for further information.
 |-

@@ Riga 380: / Riga 380: @@
 {| class="wikitable"
-! [[Change Management|Change]] domain areas !! ''[[Glossary|Service]]'' !! ''[[Glossary|Service manager]]''
+! ''[[Glossary|Change]]'' domain areas !! ''[[Glossary|Service]]'' !! ''[[Glossary|Service manager]]''
 |-

@@ Riga 510: / Riga 510: @@
 |-
-| Changes to review || ''[[Glossary|Changes]]'' in status "Completed" where <u>Change Type</u> is "Emergency" or where <u>Change Type</u> is "Normal" and <u>Change Category</u>" Significant"..    ||  || X
+| Changes to review || ''[[Glossary|Changes]]'' in status "Completed" where <u>Change Type</u> is "Emergency" or where <u>Change Type</u> is "Normal" and <u>Change Category</u>" Significant".    ||  || X
 ||  ||X ||
@@ Riga 526: / Riga 526: @@
 |-
-| Changes approved for deployment || ''[[Glossary|Chnages]]'' in status "Deployment Approved".    ||  || X
+| Changes approved for deployment || ''[[Glossary|Changes]]'' in status "Deployment Approved".    ||  || X
 ||  || X
 ||

@@ Riga 655: / Riga 655: @@
 #* Fill the ''[[Glossary|change]] ''form with <u>Owner</u>, <u>Solution Group</u> and, may be, <u>Master Solution Group</u>, <u>Ticket Worker</u>,
 #*  Pressing the '''SAVE & NEXT''' command, choose the "1. Assign ticket" ''[[Glossary|workflow transition]] ''
-The ''[[Glossary|change]]'' is now in ''[[Glossary|workflow status]]'' "In Analysis".
+The ''[[Glossary|change]]'' is now in ''[[Glossary|workflow status]]'' "In Analysis".[[Incident Management|<nowiki/>]]<nowiki/>