Release and Deployment Management - Cronologia

Francesco.bertuletti: /* Views */

2017-04-27T10:15:41Z

‎Views

Maxime.sottini il 17:54, 28 ott 2015

2015-10-28T17:54:47Z

Maxime.sottini il 15:06, 23 ott 2015

2015-10-23T15:06:33Z

Maxime.sottini: Maxime.sottini moved page Release Management to Release and Deployment Management

2015-10-23T15:01:28Z

Maxime.sottini moved page Release Management to Release and Deployment Management

Maxime.sottini: Maxime.sottini moved page DRelease Management to Release Management without leaving a redirect

2015-10-22T15:06:02Z

Maxime.sottini moved page DRelease Management to Release Management without leaving a redirect

Maxime.sottini: /* Create and request a new release as a final user */

2015-10-22T14:05:08Z

‎Create and request a new release as a final user

Maxime.sottini: /* Create and request a new release as a final user */

2015-10-22T14:04:27Z

‎Create and request a new release as a final user

Maxime.sottini: /* Reporting */

2015-10-22T14:03:33Z

‎Reporting

Maxime.sottini: /* Notifications */

2015-10-22T13:57:34Z

‎Notifications

Maxime.sottini: /* Notifications */

2015-10-22T13:00:35Z

‎Notifications

@@ Riga 481: / Riga 481: @@
 |-
-| Releases to review || ''[[Glossary|Releasess]]'' in status "Completed" where <u>Releasee Type</u> is "Emergency" or where "Major".    ||  || X
+| Releases to review || ''[[Glossary|Releases]]'' in status "Completed" where <u>Release Type</u> is "Emergency" or where "Major".    ||  || X
 ||  ||X || ||X

@@ Riga 34: / Riga 34: @@
 | Release owner ||
 * Requires ''[[Glossary|release]]'' approval to the change authority after its assessment is completed
-* Assign tasks to be performed to complete the ''[[Glossary|release]] ''(e.g. opens deployment changes)
+* Assign tasks to be performed to complete the ''[[Glossary|release]] ''(e.g. opens ''[[glossary|deployment changes]]'')
 *  Watches over and monitors the ''[[Glossary|release]] ''along all its life cycle ensuring target service levels are achieved
 * Activates escalation/ routing/ requests

@@ Riga 1: / Riga 1: @@
-''[[Glossary|Release 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|Release and Deployment 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.
-'''<u>IMPORTANT NOTE</u>''': the configuration below is only one of the possible configuration to deal with the ''[[Glossary|release management]]'' process. The need for a different behaviour of the process may be fulfilled by simple changes of the configuration.
+'''<u>IMPORTANT NOTE</u>''': the configuration below is only one of the possible configuration to deal with the ''[[Glossary|release and deployment management]]'' process. The need for a different behaviour of the process may be fulfilled by simple changes of the configuration.
 == Operational model ==
@@ Riga 143: / Riga 143: @@
 As for all ''[[Glossary|workflows]]'', new ''[[Glossary|releases]]'' can be created by using the ''[[Glossary|self service portal]]'', accessible by means of '''''Self Service''''' menu.
-The following ''[[Glossary|requests]]'' which trigger a new instance of the ''[[Glossary|release management]]'' process are configured and available in the ''[[glossary|self service portal]]'':
+The following ''[[Glossary|requests]]'' which trigger a new instance of the ''[[Glossary|release and deployment management]]'' process are configured and available in the ''[[glossary|self service portal]]'':
 {| class="wikitable sortable"
@@ Riga 155: / Riga 155: @@
 A ''[[Glossary|release]]'' may also be automatically opened during the execution of the ''[[Glossary|change management]]'' process.
-A ''[[Get started with itmSUITE®|workflow]]'' is configured to support the ''[[Glossary|release management]]'' process. The ''[[Glossary|workflow]]'' is characterized by ''[[Glossary|workflow statuses]]'' and ''[[Glossary|workflow transitions]]''. The figures below illustrate the process.
+A ''[[Get started with itmSUITE®|workflow]]'' is configured to support the ''[[Glossary|release and deployment management]]'' process. The ''[[Glossary|workflow]]'' is characterized by ''[[Glossary|workflow statuses]]'' and ''[[Glossary|workflow transitions]]''. The figures below illustrate the process.
 [[File:Change management Operational Model 1 of 3 v1.0 .jpg|centre|thumb|800x800px|Release management process (1 of 3).]]
 [[File:Change management Operational Model 2 of 3 v1.0 .jpg|centre|thumb|800x800px|Release management process (2 of 3).]]
@@ Riga 348: / Riga 348: @@
 === Related processes ===
-Several other ''[[Glossary|IT Service Management]]'' processes are related to the ''[[Glossary|release management]]'' one. Some basic interfaces are provided. The tab ''<u>Related Items</u>'' of the ''[[Glossary|release]]'' and, in particular, the sub tab <u>''Tickets''</u> of it allows to view all the existing relationships between the ''[[Glossary|release]]'' and other processes (managed through ''[[Glossary|tickets]]'').
+Several other ''[[Glossary|IT Service Management]]'' processes are related to the ''[[Glossary|release and deploymentmanagement]]'' one. Some basic interfaces are provided. The tab ''<u>Related Items</u>'' of the ''[[Glossary|release]]'' and, in particular, the sub tab <u>''Tickets''</u> of it allows to view all the existing relationships between the ''[[Glossary|release]]'' and other processes (managed through ''[[Glossary|tickets]]'').
 ==== Incident management ====

@@ Riga 609: / Riga 609: @@
 === Create and request a new ''[[Glossary|release]] ''as a final user ===
-# Login as "AppSpecialist" ''[[Glossary|user]]''
+# Login as "appspecialist" ''[[Glossary|user]]''
 #  Activate the '''''Self Service''''' menu
 #  Choose a ''[[Glossary|self service topic]]'', ''[[Glossary|self service category]]'' and finally "Release" as ''[[Glossary|self service request]] ''(this determines the creation of a new ''[[Glossary|release]]'')

@@ Riga 609: / Riga 609: @@
 === Create and request a new ''[[Glossary|release]] ''as a final user ===
-# Login as "finaluser" ''[[Glossary|user]]''
+# Login as "AppSpecialist" ''[[Glossary|user]]''
 #  Activate the '''''Self Service''''' menu
 #  Choose a ''[[Glossary|self service topic]]'', ''[[Glossary|self service category]]'' and finally "Release" as ''[[Glossary|self service request]] ''(this determines the creation of a new ''[[Glossary|release]]'')

← Versione meno recente	Versione delle 15:01, 23 ott 2015
(Nessuna differenza)

← Versione meno recente	Versione delle 15:06, 22 ott 2015
(Nessuna differenza)

@@ Riga 439: / Riga 439: @@
 |-
-| <u>''Management''</u> || <u> Release Owner</u> || To define who is the owner who should monitor the lifecycle of the ''[[Glossary|release]]''. ||
+| <u>''Management''</u> || <u>Release Owner</u> || To define who is the owner who should monitor the lifecycle of the ''[[Glossary|release]]''. ||
 |-
@@ Riga 597: / Riga 597: @@
 <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.
+A basic form of reporting is also provided by ''[[Glossary|views]]. ''Views basically allow to list ''[[Glossary|releases]]'' 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.
 == Examples of use ==
-In this section some examples of use of the configured'' [[Glossary|change management]]'' process are given.
+In this section some examples of use of the configured'' [[Glossary|release management]]'' process are given.
-If you get lost, any time use the '''EXPLORE WORKFLOW''' command of the ''[[Glossary|change]]'' management form. This enables to view the status of the ''[[Glossary|workflow]]'' as shown in the figure below. By clicking on a relationship between ''[[Glossary|workflow statuses]]'', ''[[Glossary|roles]]'' and ''[[Glossary|users]]'' enabled to perform it are presented.
+If you get lost, any time use the '''EXPLORE WORKFLOW''' command of the ''[[Glossary|release]]'' management form. This enables to view the status of the ''[[Glossary|workflow]]'' as shown in the figure below. By clicking on a relationship between ''[[Glossary|workflow statuses]]'', ''[[Glossary|roles]]'' and ''[[Glossary|users]]'' enabled to perform it are presented.
 [[File:Explore Workflow IM v1.0.JPG|centre|thumb|848x848px|Explore Workflow window]]
 '''<u>NOTE</u>''': the '''EXPLORE WORKFLOW '''command is available only if the ''[[Glossary|ticket]]'' is first saved.
@@ Riga 608: / Riga 608: @@
 For more information on how to use any workflows, including incident management, please refer to the [[workflow execution guide]].
-=== Create and request a new ''[[Glossary|change]] ''as a final user ===
+=== Create and request a new ''[[Glossary|release]] ''as a final user ===
 # Login as "finaluser" ''[[Glossary|user]]''
 #  Activate the '''''Self Service''''' menu
-#  Choose a ''[[Glossary|self service topic]]'', ''[[Glossary|self service category]]'' and finally "Change" as ''[[Glossary|self service request]] ''(this determines the creation of a new ''[[Glossary|change]]'')
+#  Choose a ''[[Glossary|self service topic]]'', ''[[Glossary|self service category]]'' and finally "Release" as ''[[Glossary|self service request]] ''(this determines the creation of a new ''[[Glossary|release]]'')
-#  Fill the ''[[Glossary|change]]'' form, at least with mandatory fields, and save with the '''SAVE''' command (the ''[[Glossary|change]]'' is now in ''[[Glossary|workflow status]]'' "Opened")
+#  Fill the ''[[Glossary|release]]'' form, at least with mandatory fields, and save with the '''SAVE''' command (the ''[[Glossary|release]]'' is now in ''[[Glossary|workflow status]]'' "Opened")
-# Set the ''[[Glossary|change]]'' in ''[[Glossary|workflow status]]'' "Requested" with the '''SAVE & NEXT''' command
+# Set the ''[[Glossary|release]]'' in ''[[Glossary|workflow status]]'' "Requested" with the '''SAVE & NEXT''' command
-You have now saved the ''[[Glossary|change]]'', take note of the ''[[Glossary|ticket]]'' number for further reference and use.
+You have now saved the ''[[Glossary|release]]'', take note of the ''[[Glossary|ticket]]'' number for further reference and use.
-=== Assign a ''[[Glossary|change]]'' for analysis as a service manager ===
+=== Assign a ''[[Glossary|release]]'' for analysis as a release manager ===
-#Login as "servicemanager"
+#Login as "releasemanager"
-# Open the the desired ''[[Glossary|change]]''; you can do it quickly either by
+# Open the the desired ''[[Glossary|release]]''; you can do it quickly either by
-#* Access the "Changes Requested" ''[[Glossary|view]]'' in the ''<u>Tickets</u>'' area of the home page and pick a ''[[Glossary|change]] ''
+#* Access the "Releases Requested" ''[[Glossary|view]]'' in the ''<u>Tickets</u>'' area of the home page and pick a ''[[Glossary|release]] ''
-#* Access the '''''Change/Changes active '''''menu and pick a ''[[Glossary|chanve]] ''in'' [[Glossary|workflow status]] ''"Requested"'' ''among those listed
+#* Access the '''''Release/Releases active '''''menu and pick a ''[[Glossary|release]] ''in'' [[Glossary|workflow status]] ''"Requested"'' ''among those listed
-#* Insert the reference number of a ''[[Glossary|change]]'' in ''[[Glossary|workflow status]]'' "Requested" in '''Quick Search''', after selecting the ''[[Glossary|search context]]'' "Ticket"
+#* Insert the reference number of a ''[[Glossary|release]]'' in ''[[Glossary|workflow status]]'' "Requested" in '''Quick Search''', after selecting the ''[[Glossary|search context]]'' "Ticket"
 # Assign the key roles
-#* 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>,
+#* Fill the ''[[Glossary|release]] ''form with <u>Release Owner</u>, <u>Release Team</u> and, may be, <u>Supervising Team</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".[[Incident Management|<nowiki/>]]<nowiki/>
+The ''[[Glossary|release]]'' is now in ''[[Glossary|workflow status]]'' "In Analysis".[[Incident Management|<nowiki/>]]<nowiki/>

@@ Riga 564: / Riga 564: @@
 |-
-|A ''[[Glossary|release]] ''deployment approval request has been examined || Release owner, service manager || Alert that the change authority has given a feedback on a ''[[Glossary|release]]'' deployment request.
+|A ''[[Glossary|release]] ''deployment approval request has been examined || Release owner, release manager || Alert that the change authority has given a feedback on a ''[[Glossary|release]]'' deployment request.
 |}
 == 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|release 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 '''''Release/Reporting''''' menu.
 The following table lists the reports available by default and their visibility:
@@ Riga 577: / Riga 577: @@
 |-
-|Change per category - trend || An histogram showing the ''[[Glossary|change]]'' volumes per category monthly trend. || Service managers and technical team members.
+|Release per category - trend || An histogram showing the ''[[Glossary|release]]'' volumes per category (<u>Release Type</u>)monthly trend. || Release manager, service managers and technical team members.
 |-
-|Change per category - volume || A pie containing the split of ''[[Glossary|changes]]'' per category. || Service managers and technical team members.
+|Release per category - volume || A pie containing the split of ''[[Glossary|releases]]'' per category (<u>Release Type</u>). || Release manager, service managers and technical team members.
 |-
-|Change per service - trend || An histogram showing the ''[[Glossary|change]] ''volumes per ''[[Glossary|service]]'' monthly trend. || Service managers and technical team members.
+|Release per service - trend || An histogram showing the ''[[Glossary|release]] ''volumes per ''[[Glossary|service]]'' monthly trend. || Release manager, servie managers and technical team members.
 |-
-|Change per service - volume || A pie containing the split of ''[[Glossary|changes]] ''per ''[[Glossary|service]]''. || Service managers and technical team members.
+|Release per service - volume || A pie containing the split of ''[[Glossary|releases]] ''per ''[[Glossary|service]]''. || Release manager, servie managers and technical team members.
 |-
-|Change per service/category - volume || An histogram showing the ''[[Glossary|changes]]'' volume per ''[[Glossary|service]]'' and category. || Service managers and technical team members.
+|Release per service/category - volume || An histogram showing the ''[[Glossary|releases]]'' volume per ''[[Glossary|service]]'' and category. || Release manager, service managers and technical team members.
 |-
-|Change - analysis time || A pie showing the percentage of ''[[Glossary|changes]] ''respecting the target defined for the "Analysis time"* ''[[Glossary|objective]]'' (the time elapsed from the "Requested" to the "In Analysis" ''[[Glossary|workflow status]]''. || Service managers and technical team members.
+|Release - analysis time || A pie showing the percentage of ''[[Glossary|releases]] ''respecting the target defined for the "Analysis time"* ''[[Glossary|objective]]'' (the time elapsed from the "Requested" to the "In Analysis" ''[[Glossary|workflow status]]''. || Release manager, service managers and technical team members.
 |}

@@ Riga 528: / Riga 528: @@
 |-
-|A ''[[Glossary|release]] ''is requested || Release Manager  || Alert that there is a ''[[Glossary|release]]'' to manage.
+|A ''[[Glossary|release]] ''is requested || Release manager  || Alert that there is a ''[[Glossary|release]]'' to manage.
 |-
-|A ''[[Glossary|change]] ''is assigned a owner || Change owner || Alert that the ''[[Glossary|change]]'' was assigned to him/her.
+|A ''[[Glossary|release]] ''is assigned a owner || Release owner || Alert that the ''[[Glossary|release]]'' was assigned to him/her.
 |-
-|A ''[[Glossary|solution group]] ''is assigned or changed for the ''[[Glossary|change]]'' || ''[[Glossary|Solution group manager]]'' || Alert that there are resource(s) to allocate to manage the ''[[Glossary|change]]''.
+|A release team is assigned or changed for the ''[[Glossary|release]]'' || Release team || Alert that there are resource(s) to allocate to manage the ''[[Glossary|release]]''.
 |-
-|A ''[[Glossary|change]] ''review shall be executed (the ''[[Glossary|change]]'' is in ''[[Glossary|workflow status]]'' "Change Review") || Change owner, service manager || Alert that a ''[[Glossary|change]]'' review is to be done.
+|A ''[[Glossary|release]] ''review shall be executed (the ''[[Glossary|release]]'' is in ''[[Glossary|workflow status]]'' "Release Review") || Release owner, release manager || Alert that a ''[[Glossary|release]]'' review is to be done.
 |-
-|A ''[[Glossary|change]] ''is completed || The ''[[Glossary|change]] ''creator, the requester || Alert that the ''[[Glossary|change]] ''is implemented.
+|A ''[[Glossary|release]] ''is completed || The release'' ''creator, the requester || Alert that the ''release ''is deployed.
 |-
@@ Riga 546: / Riga 546: @@
 |-
-|A ''[[Glossary|change]] ''is suspended || The ''[[Glossary|change]] ''creator, the requester, the service manager, the change owner || Alert that the ''[[Glossary|change]] ''is suspended.
+|A ''[[Glossary|release]] ''is suspended || The release'' ''creator, the requester, the service manager, the release manager, the releasee owner || Alert that the ''[[Glossary|release]] ''is suspended.
 |-
-|An ''[[Glossary|change ]]''is closed || The ''[[Glossary|change]] ''creator, the requester, the service manager, the change owner || Alert that the ''[[Glossary|change]]'' has been closed.
+|An ''[[Glossary|release ]]''is closed || The ''release ''creator, the requester, the service manager, the release manager, the change owner || Alert that the ''[[Glossary|release]]'' has been closed.
 |-
-|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.
+|A ''[[Glossary|release]] ''is cancelled || The ''release ''creator, the requester, the service manager, the release manager, the change owner || Alert that the ''[[Glossary|change]]'' has been cancelled.
 |-
-|A ''[[Glossary|change]] ''implementation approval has been requested || Change authority || Alert that a ''[[Glossary|change]]'' implementation request has to be examined.
+|A ''[[Glossary|release]] ''implementation approval has been requested || Change authority || Alert that a ''[[Glossary|release]]'' implementation request has to be examined.
 |-
-|A ''[[Glossary|change]] ''implementation approval request has been examined || Change owner, service manager || Alert that the change authority has given a feedback on a ''[[Glossary|change]]'' implementation request.
+|A ''[[Glossary|release]] ''implementation approval request has been examined || Release owner, release manager || Alert that the change authority has given a feedback on a ''[[Glossary|release]]'' implementation request.
 |-
-|A ''[[Glossary|change]] ''deployment approval has been requested || Change authority || Alert that a ''[[Glossary|change]]'' deployment request has to be examined.
+|A ''[[Glossary|release]] ''deployment approval has been requested || Change authority || Alert that a ''[[Glossary|release]]'' deployment request has to be examined.
 |-
-|A ''[[Glossary|change]] ''deployment approval request has been examined || Change owner, service manager || Alert that the change authority has given a feedback on a ''[[Glossary|change]]'' deployment request.
+|A ''[[Glossary|release]] ''deployment approval request has been examined || Release owner, service manager || Alert that the change authority has given a feedback on a ''[[Glossary|release]]'' deployment request.
 |}