Deployment Change - Cronologia

Maxime.sottini: /* Operational model */

2015-10-28T17:53:42Z

‎Operational model

Maxime.sottini: Maxime.sottini moved page DDeployment Change to Deployment Change without leaving a redirect

2015-10-28T17:49:20Z

Maxime.sottini moved page DDeployment Change to Deployment Change without leaving a redirect

Maxime.sottini: /* Reporting */

2015-10-28T15:56:10Z

‎Reporting

Maxime.sottini: /* Reporting */

2015-10-28T15:55:20Z

‎Reporting

Maxime.sottini: /* Reporting */

2015-10-28T15:55:01Z

‎Reporting

Maxime.sottini: /* Reporting */

2015-10-28T15:40:10Z

‎Reporting

Maxime.sottini: /* Reporting */

2015-10-28T15:38:06Z

‎Reporting

Maxime.sottini: /* Reporting */

2015-10-28T15:37:28Z

‎Reporting

Maxime.sottini: /* Reporting */

2015-10-28T15:30:02Z

‎Reporting

Maxime.sottini: /* Notifications */

2015-10-28T15:26:57Z

‎Notifications

@@ Riga 8: / Riga 8: @@
 The preconfigured process has the objective to deploy a [[glossary|''release'']]  and is a'' [[glossary|standard change]]''. At the core of the process configuration is the following simple operational model.
 [[File:Deployment Change Operational Model v1.0.jpg|centre|thumb|625x625px|Deployment Change operational model]]
-From the ''[[Release and Deployment Management]]'' process a command (button) is available to trigger the ''[[glossary|Deployment Change]]'' process. This opens a new [[glossary|''Deployment Change'']] instance. This is done by an ''[[glossary|action]] ''which  sets also sets a release team (a defined ''[[glossary|group]]''). The members of the release team can therefore see the deployment change and set the owner of it. The owner performs or coordinates the deployment activities. When the activities are completed another ''[[glossary|action]]'' automatically gives a feedback to the ''[[Release and Deployment Management]]'' process.
+From the ''[[Release and Deployment Management]]'' process a command (button) is available to trigger the ''[[glossary|Deployment Change]]'' process. This opens a new [[glossary|''Deployment Change'']] instance. This is done by an ''[[glossary|action]] ''which  sets also sets a release team (a defined ''[[glossary|group]]''). The members of the release team can therefore see the ''[[glossary|deployment change]]'' and set the owner of it. The owner performs or coordinates the deployment activities. When the activities are completed another ''[[glossary|action]]'' automatically gives a feedback to the ''[[Release and Deployment Management]]'' process.
 == Roles ==
@@ Riga 18: / Riga 18: @@
 |-
 |Requester ||
-* This is the ''[[glossary|user]]'' who triggers a deployment change while managing a ''[[glossary|release]]''
+* This is the ''[[glossary|user]]'' who triggers a ''[[glossary|deployment change]]'' while managing a ''[[glossary|release]]''
-||  See the ''[[Release and Deployment Management]]'' process for detailed information on who is enabled to start deployment changes
+||  See the ''[[Release and Deployment Management]]'' process for detailed information on who is enabled to start ''[[glossary|deployment changes]]''
 |-
 | Owner ||
-* Assign tasks to be performed to complete the deployment change
+* Assign tasks to be performed to complete the ''[[glossary|deployment change]]''
-*  Watches over and monitors the deployment change'' ''along all its life cycle
+*  Watches over and monitors the ''[[glossary|deployment change]] ''along all its life cycle
 * Activates escalation/ routing/ requests
 * Manages all the communications with the requester
-* Checks the implementation and sets the deployment change'' ''to closed
+* Checks the implementation and sets the ''[[glossary|deployment change]] ''to closed
 || This role is picked up by a member of the deployment team (a specific ''[[glossary|group]]'').
 |-
 | Deployment team member  ||
-* He/she receives the notification on the assignment of a deployment change to the team
+* He/she receives the notification on the assignment of a ''[[glossary|deployment change]]'' to the team
-* Based on the team rules, he/she autonomously picks up a deployment change as an owner or wait for the deployment team manager assignment
+* Based on the team rules, he/she autonomously picks up a ''[[glossary|deployment change]]'' as an owner or wait for the deployment team manager assignment
-*  He/she carries out any assigned task of a deployment change
+*  He/she carries out any assigned task of a ''[[glossary|deployment change]]''
 * He/she notices when assigned tasks are completed or when he/she is unable to complete them
 || ''[[glossary|Resources]]'' belonging to the "Deployment team" ''[[glossary|group]]''; the login identifier of one of these ''users ''is "DepTeamMemb").
@@ Riga 41: / Riga 41: @@
 |-
 | Deployment team manager ||
-* He/she receives the notification on the assignment of a deployment change to the team
+* He/she receives the notification on the assignment of a ''[[glossary|deployment change]]'' to the team
 *  Based on the team rules, he/she assigns a deployment team member
 *  He/she may also act as deployment team member
@@ Riga 49: / Riga 49: @@
 == Process ==
-A deployment change is opened during the execution of the ''[[Release and Deployment Management]]'' process and is kept linked to the instance of the ''[[glossary|release]]'' it is originated from.
+A ''[[glossary|deployment change]]'' is opened during the execution of the ''[[Release and Deployment Management]]'' process and is kept linked to the instance of the ''[[glossary|release]]'' it is originated from.
 A ''[[Get started with itmSUITE®|workflow]]'' is configured to support the ''[[Glossary|Deployment Management]]'' process. The ''[[Glossary|workflow]]'' is characterized by ''[[Glossary|workflow statuses]]'' and ''[[Glossary|workflow transitions]]''. The figures below illustrate the process.
@@ Riga 59: / Riga 59: @@
 |-
-| "Default" || A preliminary status which is displayed when a deployment change is created.
+| "Default" || A preliminary status which is displayed when a ''[[glossary|deployment change]]'' is created.
 |-
-| "Opened" || The deployment change has been recorded and requested.
+| "Opened" || The ''[[glossary|deployment change]]'' has been recorded and requested.
 |-
-| "Cancelled" || The deployment change'' ''is not confirmed and, therefore, cancelled.
+| "Cancelled" || The ''[[glossary|deployment change]] ''is not confirmed and, therefore, cancelled.
 |-
-| "Closed" || The deployment change is completed and closed.
+| "Closed" || The ''[[glossary|deployment change]]'' is completed and closed.
 |}
@@ Riga 89: / Riga 89: @@
 === Related processes ===
-The key related process is ''[[Release and Deployment Management]]''. The tab ''<u>Related Items</u>'' of the deployment change and, in particular, the sub tab <u>''Tickets''</u> of it allows to view all the existing relationships between the deployment change and ''[[Release and Deployment Management]]''.
+The key related process is ''[[Release and Deployment Management]]''. The tab ''<u>Related Items</u>'' of the ''[[glossary|deployment change]]'' and, in particular, the sub tab <u>''Tickets''</u> of it allows to view all the existing relationships between the ''[[glossary|deployment change]]'' and ''[[Release and Deployment Management]]''.
 ==== Release and deployment management ====
-A new deployment change can be initiated from a ''[[Glossary|release]]'' and updating the deployment change will provide a feedback to the [[glossary|''release'']] itself. <nowiki/>
+A new ''[[glossary|deployment change]]'' can be initiated from a ''[[Glossary|release]]'' and updating the ''[[glossary|deployment change]]'' will provide a feedback to the [[glossary|''release'']] itself. <nowiki/>
 == Services ==
-The deployment changes are opened on the "Deployment Management" ''[[Get started with itmSUITE®|service]]''. The ''[[glossary|user]]'' "DeplManager" is the ''[[glossary|service manager]]'' of the "Deployment Management" ''[[glossary|service]]''.
+The ''[[glossary|deployment changes]]'' are opened on the "Deployment Management" ''[[Get started with itmSUITE®|service]]''. The ''[[glossary|user]]'' "DeplManager" is the ''[[glossary|service manager]]'' of the "Deployment Management" ''[[glossary|service]]''.
 == Management information ==
-Many management information are available as fields in the deployment change management configured form. The following table illustrates the intended use of key information and its behaviour. '''<u>NOTE</u>''': information are available (visible) and can be modified according to a specific configuration which is meant to be suitable for the organizational roles involved in the process.
+Many management information are available as fields in the ''[[glossary|deployment change]]'' management configured form. The following table illustrates the intended use of key information and its behaviour. '''<u>NOTE</u>''': information are available (visible) and can be modified according to a specific configuration which is meant to be suitable for the organizational roles involved in the process.
 {| class="wikitable sortable"
@@ Riga 107: / Riga 107: @@
 |-
-| ''<u>General Information</u>'' || <u>Short Description</u> || To provide a short description of the ''[[Glossary|deployment change]]''. ||This mandatory field is automatically filled by the action creating the deployment change but can be edited.
+| ''<u>General Information</u>'' || <u>Short Description</u> || To provide a short description of the ''[[Glossary|deployment change]]''. ||This mandatory field is automatically filled by the action creating the ''[[glossary|deployment change]]'' but can be edited.
 |-

← Versione meno recente		Versione delle 15:56, 28 ott 2015
Riga 251:		Riga 251:
	<nowiki>*</nowiki> "Analysis time" is defined within the ''[[Glossary\|OCE]]'' ''[[Glossary\|module]]''.		<nowiki>*</nowiki> "Analysis time" is defined within the ''[[Glossary\|OCE]]'' ''[[Glossary\|module]]''.

−	A basic form of reporting is also provided by ''[[Glossary\|views]]. ''Views basically allow to list ''[[Glossary\|changes]]'' and their attributes but may also be configured to calculates sums, averages on some of them.'' ''The available ''[[Glossary\|views]]'' are illustrated in the dedicated [[Incident Management#Views\|section]] of this page.[[Incident Management\|<nowiki/>]]<nowiki/>	+	A basic form of reporting is also provided by ''[[Glossary\|views]]. ''Views basically allow to list ''[[Glossary\|deployment changes]]'' and their attributes but may also be configured to calculates sums, averages on some of them.'' ''The available ''[[Glossary\|views]]'' are illustrated in the dedicated [[Incident Management#Views\|section]] of this page.[[Incident Management\|<nowiki/>]]<nowiki/>

@@ Riga 247: / Riga 247: @@
 |-
 |Deployment change - trend || An histogram showing the ''[[Glossary|Deployment change]] ''volumes monthly trend. || Deployment team, release team and supervising team.
 |}

@@ Riga 246: / Riga 246: @@
 |-
-|Deployment change - trend || An histogram showing the ''[[Glossary|Deployment change]] ''volumes monthly trend. || Service managers and technical team members.
+|Deployment change - trend || An histogram showing the ''[[Glossary|Deployment change]] ''volumes monthly trend. || Deployment team, release team and supervising team.
 |-

@@ Riga 246: / Riga 246: @@
 |-
-|Change per service - trend || An histogram showing the ''[[Glossary|change]] ''volumes per ''[[Glossary|service]]'' monthly trend. || Service managers and technical team members.
+|Deployment change - trend || An histogram showing the ''[[Glossary|Deployment change]] ''volumes monthly trend. || Service managers and technical team members.
 |-

← Versione meno recente	Versione delle 17:49, 28 ott 2015
(Nessuna differenza)

@@ Riga 244: / Riga 244: @@
 {| class="wikitable"
 ! Report name !! Content !! Access
 |-
@@ Riga 256: / Riga 250: @@
 |-
 |Change per service - volume || A pie containing the split of ''[[Glossary|changes]] ''per ''[[Glossary|service]]''. || Service managers and technical team members.
 |}

@@ Riga 230: / Riga 230: @@
 |-
-|A ''[[Glossary|deployment change ]]''is closed || The ''[[Glossary|deployment change]] ''owner, the ''[[glossary|release]]'' owner, the deployment team, the release team, the supervising team || Alert that the ''[[Glossary|change]]'' has been closed.
+|A ''[[Glossary|deployment change ]]''is closed || The ''[[Glossary|deployment change]] ''owner, the ''[[glossary|release]]'' owner, the deployment team, the release team, the supervising team || Alert that the ''[[Glossary|deployment change]]'' has been closed.
 |-
-|A ''[[Glossary|deployment change]] ''is cancelled || The ''[[Glossary|deployment change]] ''owner, the ''[[glossary|release]] ''owner, the deployment team, the release team, the supervising team || Alert that the ''[[Glossary|change]]'' has been cancelled.
+|A ''[[Glossary|deployment change]] ''is cancelled || The ''[[Glossary|deployment change]] ''owner, the ''[[glossary|release]] ''owner, the deployment team, the release team, the supervising team || Alert that the ''[[Glossary|deployment hange]]'' has been cancelled.
 |}
 == Reporting ==
-A set of standard reports are made available for the ''[[Glossary|change management]]'' process. It is not required to have the [[Glossary|REP]] ''[[Glossary|module]]'' to use them, however the [[Glossary|''module'']] is required if new or changed reports are needed. The available reports are placed under '''''Change/Reporting''''' menu.
+A set of standard reports are made available for the ''[[Glossary|deployment change management]]'' process. It is not required to have the [[Glossary|REP]] ''[[Glossary|module]]'' to use them, however the [[Glossary|''module'']] is required if new or changed reports are needed. The available reports are placed under '''''Deployment/Reporting''''' menu.
 The following table lists the reports available by default and their visibility:

@@ Riga 234: / Riga 234: @@
 |-
 |A ''[[Glossary|change]] ''is cancelled || The ''[[Glossary|change]] ''creator, the requester, the service manager, the change owner || Alert that the ''[[Glossary|change]]'' has been cancelled.
 |}