Differenze tra le versioni di "Release and Deployment Management"

Da itm wiki.
(→‎Operational model)
(Etichetta: visualeditor)
(→‎Views)
(Etichetta: visualeditor)
 
(44 versioni intermedie di un altro utente non mostrate)
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.
 
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 ==
 
== Operational model ==
 
The preconfigured process has the objective to facilitate and support the effective and efficient execution of ''[[Glossary|releases]]''. 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|releases]]''. 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]]
+
[[File:Release Management Operational Model v1.0.JPG|centre|thumb|800x800px|Release Management operational model]]
−
The requester, a service manager, a  authorizedmember of the ''[[Glossary|service desk]]'' or of a technical team (e.g. one of the development teams) or the [[Glossary|''change Management'']] process require a new release. The release manager takes in charge it and assigns an owner who coordinates all the tasks needed to fulfil the ''[[Glossary|release]]''. If necessary, the owner requests the ''[[Glossary|releasee]]'' authorization to the ''[[Glossary|change authority]]'', if needed. Finally he/she activates the deployment change process in order to complete the installation of the release in the target environment.
+
The requester, a service manager, an authorized member of the ''[[Glossary|service desk]]'' or a technical team member (e.g. a developer) or the [[Glossary|''change Management'']] process requires a new ''[[Glossary|release]]''. The release manager takes in charge it and assigns an owner who coordinates all the tasks needed to fulfil the ''[[Glossary|release]]''. If necessary, the owner requests the ''[[Glossary|releasee]]'' authorizations to the ''[[Glossary|change authority]]''. Finally, he/she activates the ''[[Glossary|deployment change]]'' process in order to complete the installation of the ''[[Glossary|release]]'' in a target environment (e.g. test, production).
  
 
== Roles ==
 
== Roles ==
Riga 18: Riga 18:
 
|-
 
|-
 
|Requester ||  
 
|Requester ||  
−
* Opens ''[[Glossary|requests for change]]'' on behalf of himself/herself or for a third party
+
* Opens requests for ''[[Glossary|releases]]'' on behalf of himself/herself or for a third party
 
||  This role is mapped on:
 
||  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";
+
* service managers (see after);
−
* 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");
−
* service desk members (system ''[[Glossary|resources]] ''with ''[[Glossary|user]] ''of ''[[Glossary|user type]] ''"Resource"; the login identifier of this ''[[Glossary|user]] ''is "SDSpecialist";
 
 
* technical team members (see after).
 
* technical team members (see after).
 +
 +
|-
 +
|Release Manager ||
 +
* Receives and evaluates release requests
 +
* Assigns a release owner
 +
* May act as a release owner
 +
||  This role is mapped on the service manager(r) of the ''[[glossary|service]]'' on which the ''[[Glossary|release]]'' is requested.
 
   
 
   
 
|-
 
|-
−
| Change owner ||
+
| Release owner ||
−
* Requires ''[[Glossary|change]]'' approval to the change authority after its assessment is completed
+
* Requires ''[[Glossary|release]]'' approval to the change authority after its assessment is completed
−
* Assign tasks to be performed to complete the ''[[Glossary|change]]''
+
* Assign tasks to be performed to complete the ''[[Glossary|release]] ''(e.g. opens ''[[glossary|deployment changes]]'')
−
*  Watches over and monitors the ''[[Glossary|change]] ''along all its life cycle ensuring target service levels are achieved
+
*  Watches over and monitors the ''[[Glossary|release]] ''along all its life cycle ensuring target service levels are achieved
 
* Activates escalation/ routing/ requests
 
* Activates escalation/ routing/ requests
 
* Manages all the communications with the requester
 
* Manages all the communications with the requester
−
* Checks the implementation and sets the ''[[Glossary|change]] ''to to completed
+
* Checks the implementation and sets the ''[[Glossary|releasee]] ''to completed
−
* Closes the ''[[Glossary|change]] ''after completing the final checks
+
* Closes the ''[[Glossary|release]] ''after completing the final checks
−
|| Role assigned by the service manager to himself/herself or to a technical team member.   
+
|| This role is assigned to the manager of the ''[[glossary|group]]'' "Release Management"; the login identifier of this ''[[glossary|user]]''  is "ReleaseManager".   
 
   
 
   
 
|-
 
|-
−
| Technical team member  ||  
+
| Technical team member  ||A technical team member may first of all be a requester (see before). However he/she may play an active role in the preparation and installation of the release. In detail
−
* He/she receives the notification on the assignment of an activity concerning a ''[[Glossary|change]] ''(e.g. conducting the assessment or designing/implementing it)
+
 
 +
* He/she receives the notification on the assignment of an activity concerning a ''[[Glossary|release]] ''(e.g. conducting the assessment or designing/implementing it)
  
 
* Carries out the assigned tasks
 
* Carries out the assigned tasks
Riga 68: Riga 75:
 
|-
 
|-
 
| Technical team manager ||  
 
| Technical team manager ||  
−
* Receives the notification about the assignment of the ''[[Glossary|change]] ''to his/her team in order to implement it
+
* Receives the notification about the assignment of the ''[[Glossary|release]] ''to his/her team in order to implement it
 
* Assign the member of his/her team who should work on it (this can be done by setting the ''[[Glossary|ticket worker]]'' or creating and assigning ''[[Glossary|ticket activities]]'')
 
* Assign the member of his/her team who should work on it (this can be done by setting the ''[[Glossary|ticket worker]]'' or creating and assigning ''[[Glossary|ticket activities]]'')
 
* Watches over and monitors the work of his/her team
 
* Watches over and monitors the work of his/her team
Riga 91: Riga 98:
  
 
|-
 
|-
−
| Service manager ||  
+
| Service manager ||The service manager may act as a requester of a ''[[glossary|release]]'' (see before). The service manager(s) of the ''[[glossary|service]]'' on which the ''[[Glossary|release]]'' is managed acts as the release manager(s).
−
* Takes in charge and assigns the change owner
+
|| There are different service managers configured for specific ''[[Glossary|services]]''. See [[Incident Management#Services|Services]] section in this page for further information.  
−
* 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.  
 
  
 
|-
 
|-
 
| Change authority ||  
 
| Change authority ||  
−
* Approves the ''[[Glossary|change]]'' implementation
+
* Approves the ''[[Glossary|release]]'' implementation
−
* Approves the ''[[Glossary|change]]'' deployment
+
* Approves the ''[[Glossary|releasee]]'' deployment
−
|| This role is mapped based on the required authorization and ''[[Glossary|change]]'' classification.
+
|| This role is mapped based on the required authorization and ''[[Glossary|release]]'' classification.
  
−
For ''[[Glossary|change]]'' implementation authorization:
+
For ''[[Glossary|release]]'' implementation authorization:
 
{| class="wikitable"
 
{| class="wikitable"
−
! <u>Change Type</u> !! ''<u>Change Category</u> '' !! ''Change authority''
+
! <u>Release Type</u> !! ''Change authority''
−
 
 
−
|-
 
−
|"Emergency" ||  || Service manager
 
  
 
|-
 
|-
−
|"Normal" || "Minor" || Service manager
+
|"Emergency" || Service manager
  
 
|-
 
|-
−
|"Normal" || "Significant" || CAB
+
|"Minor" || Service manager
  
 
|-
 
|-
−
|"Standard" || || Change owner
+
|"Major" || CAB
 
   
 
   
 
|}
 
|}
 
The CAB is mapped on a ''[[Glossary|group]]'': "CAB".
 
The CAB is mapped on a ''[[Glossary|group]]'': "CAB".
  
−
For ''[[Glossary|change]]'' deployment authorization:   
+
For ''[[Glossary|release]]'' deployment authorization:   
 
{| class="wikitable"
 
{| class="wikitable"
−
! <u>Change Type</u> !! ''<u>Change Category</u> '' !! ''Change authority''
+
! <u>Change Type</u> !! ''Change authority''
−
 
 
−
|-
 
−
|"Emergency" ||  || Service manager
 
  
 
|-
 
|-
−
|"Normal" || "Minor" || Change owner
+
|"Emergency" || Service manager
  
 
|-
 
|-
−
|"Normal" || "Significant" || Service manager
+
|"Minor" || Release manager
  
 
|-
 
|-
−
|"Standard" || || Change owner
+
|"Major" || Service manager
 
   
 
   
 
|}
 
|}
Riga 142: Riga 141:
  
 
== Process ==
 
== Process ==
−
As for all ''[[Glossary|workflows]]'', new ''[[Glossary|changes]]'' can be created by using the ''[[Glossary|self service portal]]'', accessible by means of '''''Self Service''''' menu.  
+
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|change management]]'' process are configured and available to all organizational roles in the ''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"
 
{| class="wikitable sortable"
Riga 150: Riga 149:
  
 
|-
 
|-
−
| "Applications" || "itmCLOUD" || "Change" (open a ''[[Glossary|change]]'') ||Requesters
+
| "Applications" || "Application Management" || "Release" (open a ''[[Glossary|release]]'') ||Requesters
−
 
 
−
|-
 
−
| "Personal Devices" || "Personal Computers" || "Change" (open a ''[[Glossary|change]]'') ||Requesters
 
−
 
 
−
|-
 
−
| "Personal Devices" || "Peripherals" || "Change" (open a ''[[Glossary|change]]'') ||Requesters
 
−
 
 
−
|-
 
−
| "Personal Devices" || "Telephony" || "Change" (open a ''[[Glossary|change]]'') ||Requesters
 
−
 
 
−
|-
 
−
| "Network" || "Networking Management" || "Change" (open a ''[[Glossary|change]]'') ||Requesters
 
−
 
 
−
|-
 
−
| "Technical Services" || "Server Management" || "Change" (open a ''[[Glossary|change]]'') ||Requesters
 
  
 
|}
 
|}
  
−
A ''[[Glossary|change]]'' may also be automatically opened during the execution of other processes by the ''[[Glossary|resources]]'' dealing with them.  
+
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|change 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|Change management process (1 of 3).]]
+
[[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|Change management process (2 of 3).]]
+
[[File:Change management Operational Model 2 of 3 v1.0 .jpg|centre|thumb|800x800px|Release management process (2 of 3).]]
−
[[File:Change management Operational Model 3 of 3 v1.0 .jpg|centre|thumb|800x800px|Change management process (3 of 3).]]
+
[[File:Change management Operational Model 3 of 3 v1.0 .jpg|centre|thumb|800x800px|Release management process (3 of 3).]]
 
The table below explains the meaning of each ''[[Glossary|workflow status.]] ''
 
The table below explains the meaning of each ''[[Glossary|workflow status.]] ''
  
Riga 181: Riga 165:
  
 
|-
 
|-
−
| "Default" || A preliminary status which is displayed when a ''[[Glossary|change]]'' is created.  
+
| "Default" || A preliminary status which is displayed when a ''[[Glossary|release]]'' is created.  
  
 
|-
 
|-
−
| "Opened" || The ''[[Glossary|change]]'' has been recorded.  
+
| "Opened" || The ''[[Glossary|release]]'' has been recorded.  
  
 
|-
 
|-
−
| "Requested" || The ''[[Glossary|change]]'' is confirmed and has been requested (it is a ''[[Glossary|request for change]]'').  
+
| "Requested" || The ''[[Glossary|release]]'' is confirmed and has been requested.  
  
 
|-
 
|-
−
| "In Analysis" || The ''[[Glossary|change]]'' assessment and planning is ongoing.  
+
| "In Analysis" || The ''[[Glossary|release]]'' assessment and planning is ongoing.  
  
 
|-
 
|-
−
| "Implementation Approval Requested" || The ''[[Glossary|change]]'' approval request for implementation is submitted to the change authority.  
+
| "Implementation Approval Requested" || The ''[[Glossary|release]]'' approval request for implementation is submitted to the change authority.  
  
 
|-
 
|-
−
| "Approved" || The ''[[Glossary|change]]'' is approved for implementation.   
+
| "Approved" || The ''[[Glossary|release]]'' is approved for implementation.   
  
 
|-
 
|-
−
| "Not Approved" || The ''[[Glossary|change]]'' is not approved for implementation.   
+
| "Not Approved" || The ''[[Glossary|release]]'' is not approved for implementation.   
  
 
|-
 
|-
−
| "In Progress" || The ''[[Glossary|change]]'' implementation is ongoing.   
+
| "In Progress" || The ''[[Glossary|release]]'' implementation is ongoing.   
  
 
|-
 
|-
−
| "Ready for Test" || The ''[[Glossary|change]]'' is ready for testing.
+
| "Ready for Test" || The ''[[Glossary|release]]'' is ready for testing. In this status, a ''[[glossary|deployment change]]'' can be opened to install the ''[[glossary|release]]'' in a test environment.
  
 
|-
 
|-
−
| "In Test" || The ''[[Glossary|change]]'' testing is ongoing.   
+
| "In Test" || The ''[[Glossary|release]]'' testing is ongoing.   
  
 
|-
 
|-
−
| "Deployment Approval Requested" || The ''[[Glossary|change]]'' approval request for deployment is submitted to the change authority.   
+
| "Deployment Approval Requested" || The ''[[Glossary|release]]'' approval request for deployment is submitted to the change authority.   
  
 
|-
 
|-
−
| "Deployment Approved" || The ''[[Glossary|change]]'' is approved for deployment.
+
| "Deployment Approved" || The ''[[Glossary|release]]'' is approved for deployment. In this status, a ''[[glossary|deployment change]]'' can be opened to install the ''[[glossary|release]]'' in the live environment.
  
 
|-
 
|-
−
| "Completed" || The ''[[Glossary|change]]'' is completed.   
+
| "Completed" || The ''[[Glossary|release]]'' is completed.   
  
 
|-
 
|-
−
| "Change Review" || The ''[[Glossary|change]]'' review is ongoing.   
+
| "Change Review" || The ''[[Glossary|release]]'' review is ongoing.   
  
 
|-
 
|-
−
| "Cancelled" || The ''[[Glossary|change]] ''is not confirmed and, therefore, cancelled.   
+
| "Cancelled" || The ''[[Glossary|release]] ''is not confirmed and, therefore, cancelled.   
  
 
|-
 
|-
−
| "Suspended" || The ''[[Glossary|change]] ''execution is temporarily suspended. In this status ''[[Glossary|service levels]]'' calculation are suspended too.  
+
| "Suspended" || The ''[[Glossary|release]] ''execution is temporarily suspended. In this status ''[[Glossary|service levels]]'' calculation are suspended too.  
  
 
|-
 
|-
−
| "Aborted" || The ''[[Glossary|change]]'' execution is aborted.   
+
| "Aborted" || The ''[[Glossary|release]]'' execution is aborted.   
  
 
|-
 
|-
−
| "Closed" || The ''[[Glossary|change]] ''closure has been confirmed.  
+
| "Closed" || The ''[[Glossary|release]] ''closure has been confirmed.  
 
   
 
   
 
|}
 
|}
Riga 242: Riga 226:
  
 
|-
 
|-
−
| "Default" || "Opened" || Requesters ||See the ''[[Glossary|self service portal]]'' configuration previously described.
+
| "Default" || "Opened" || Requester
 +
service manager.
 +
||See the ''[[Glossary|self service portal]]'' configuration previously described.
  
 
|-
 
|-
−
| "Opened" || "Requested" || Requester, service manager. ||
+
| "Opened" || "Requested" || Requester, service manager, release manager. ||
  
  
Riga 252: Riga 238:
  
 
|-
 
|-
−
| "Requested" || "Opened" || Requester, service manager.. ||
+
| "Requested" || "Opened" || Requester, service manager, release manager. ||
  
 
|-
 
|-
−
| "Requested" || "Cancelled" || Requester, service manager, chabge owner. ||
+
| "Requested" || "Cancelled" || Requester, service manager, release manager. ||
  
 
|-
 
|-
−
| "Requested" || "In Analysis" || Service manager, change owner. ||
+
| "Requested" || "In Analysis" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Deployment Approved" || "Aborted" || Service manager, change owner. ||
+
| "Deployment Approved" || "Aborted" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In Analysis" || "Requested" || Service manager, change owner. ||
+
| "In Analysis" || "Requested" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In Analysis" || "Approval Requested" || Service manager, change owner. ||
+
| "In Analysis" || "Approval Requested" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In Analysis" || "Cancelled" || Service manager, change owner. ||
+
| "In Analysis" || "Cancelled" || Release owner, release manager. ||
  
  
 
|-
 
|-
−
| "Approval Requested" || "Approved" || Change authority. ||Depending on ''[[Glossary|change]]'' classification (see [[DChange Management|roles]] for more details).
+
| "Approval Requested" || "Approved" || Change authority. ||Depending on ''[[Glossary|release]]'' classification (see [[DChange Management|roles]] for more details).
  
 
|-
 
|-
−
| "Approval Requested" || "Not Approved" || Change authority. ||Depending on ''[[Glossary|change]] ''classification (see [[DChange Management|roles]] for more details).
+
| "Approval Requested" || "Not Approved" || Change authority. ||Depending on ''[[Glossary|release]] ''classification (see [[DChange Management|roles]] for more details).
  
 
|-
 
|-
−
| "Approval Requested" || "In Analysis" || Service manager, change owner. ||
+
| "Approval Requested" || "In Analysis" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Not Approved" || "Cancelled" || Service manager, change owner. ||
+
| "Not Approved" || "Cancelled" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Approved" || "In Progress" || Service manager, change owner, technical team member. ||
+
| "Approved" || "In Progress" || Release owner, release manager, technical team member. ||
  
 
|-
 
|-
−
| "Approved" || "Suspended" || Service manager, change owner. ||
+
| "Approved" || "Suspended" || Release owner, release manager. ||
  
  
 
|-
 
|-
−
| "Approved" || "Aborted" || Service manager, change owner. ||
+
| "Approved" || "Aborted" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Suspended" || "In Progress" || Service manager, change owner. ||
+
| "Suspended" || "In Progress" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In progress" || "Suspended" || Service manager, change owner. ||
+
| "In progress" || "Suspended" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In progress" || "Aborted" || Service manager, change owner. ||
+
| "In progress" || "Aborted" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In progress" || "Ready for Test" || Service manager, change owner, technical team member ||
+
| "In progress" || "Ready for Test" || Release owner, release manager technical team member. ||
  
 
|-
 
|-
−
| "In progress" || "In Test" || Service manager, change owner, technical team member. ||
+
| "In progress" || "In Test" || Release owner, release manager, technical team member. ||
  
 
|-
 
|-
−
| "In progress" || "Deployment Approval Requested" || Service manager, change owner. ||
+
| "In progress" || "Deployment Approval Requested" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In progress" || "Completed" || Service manager, change owner. ||Only for ''[[Glossary|changes]]'' with <u>Change Type</u> "Standard" or with Change Type "Normal" and <u>Change Category</u> "Minor".
+
| "In progress" || "Completed" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Ready for Test" || "In Test" || Service manager, change owner, technical team member. ||
+
| "Ready for Test" || "In Test" || Release owner release manager, technical team member. ||
  
 
|-
 
|-
−
| "Ready for Test" || "Suspended" || Service manager, change owner. ||
+
| "Ready for Test" || "Suspended" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Ready for Test" || "Aborted" || Service manager, change owner. ||
+
| "Ready for Test" || "Aborted" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In Test" || "Deployment Approval Requested" || Service manager, change owner. ||
+
| "In Test" || "Deployment Approval Requested" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In Test" || "Suspended" || Service manager, change owner. ||
+
| "In Test" || "Suspended" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "In Test" || "Aborted" || Service manager, change owner. ||
+
| "In Test" || "Aborted" || Release owner, release manager. ||
  
 
|-
 
|-
Riga 338: Riga 324:
  
 
|-
 
|-
−
| "Deployment Approval Requested" || "Suspended" || Service manager, change owner. ||
+
| "Deployment Approval Requested" || "Suspended" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Deployment Approval Requested" || "Aborted" || Service manager, change owner. ||
+
| "Deployment Approval Requested" || "Aborted" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Deployment Approved" || "Completed" || Service manager, change owner. ||
+
| "Deployment Approved" || "Completed" || Release owner, release manager. ||
  
  
 
|-
 
|-
−
| "Completed" || "Change Review" || Service manager, change owner. ||
+
| "Completed" || "Change Review" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Completed" || "Closed" || Service manager, change owner. ||Not allowed for ''[[Glossary|changes]]'' with <u>Change Type</u> "Emergency" and <u>Change Type</u> "Normal" and <u>Change Category</u> "Significant"
+
| "Completed" || "Closed" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Change review" || "Closed" || Service manager, change owner. ||
+
| "Change review" || "Closed" || Release owner, release manager. ||
  
 
|-
 
|-
−
| "Not Approved" || "In Analysis" || Service manager, change owner. ||
+
| "Not Approved" || "In Analysis" || Release owner, release manager. ||
  
 
|}
 
|}
  
 
=== Related processes ===
 
=== Related processes ===
−
Several other ''[[Glossary|IT Service Management]]'' processes are related to the ''[[Glossary|change management]]'' one. Some basic interfaces are provided. The tab ''<u>Related Items</u>'' of the ''[[Glossary|change]]'' and, in particular, the sub tab <u>''Tickets''</u> of it allows to view all the existing relationships between the ''[[Glossary|change]]'' 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 ====
 
==== Incident management ====
−
It is possible to create a ''[[Glossary|change]]'' from the ''[[Incident Management#Problem management|incident management]]'' process or to relate an existing ''[[Glossary|change]]'' to an ''[[Glossary|incident]]'' and vice versa.The ''[[Glossary|change]]'' usually implements the resolution of an ''[[Glossary|incident]]''.
+
The relationship is indirect: a ''[[Glossary|release]]'' may be related to ''[[glossary|changes]]'' which implement the solution of ''[[Glossary|incidents]]''.  
  
 
==== Problem management ====
 
==== Problem management ====
−
It is possible to create a ''[[Glossary|change]] ''from the ''[[Incident Management#Problem management|problem management]] ''process or to relate an existing ''[[Glossary|change]] ''to a ''[[Glossary|problem]] ''and vice versa.The ''[[Glossary|change]] ''usually implements the resolution of a ''[[Glossary|problem]]''.
+
The relationship is indirect: a ''[[glossary|release]]'' may be related to ''[[glossary|changes]]'' which implement the solution of ''[[glossary|problems]]''.
  
 
==== Asset management and configuration management ====
 
==== Asset management and configuration management ====
−
It is possible to relate ''[[Glossary|configuration items]]'' to a ''[[Glossary|change]]'' by using the tab ''<u>Related Items</u>'' and, in particular, the sub tab <u>''Configuration Items''</u>. The ''[[Glossary|ASM]]'' and/or [[Glossary|''CMS'']] ''[[Glossary|modules]]'' features are made available here (e.g. view of ''[[Glossary|configuration item]]'' details, ''[[Glossary|configuration exploration]]'' or ''[[Glossary|impact analysis]]'').
+
It is possible to relate ''[[Glossary|configuration items]]'' to a ''[[Glossary|release]]'' by using the tab ''<u>Related Items</u>'' and, in particular, the sub tab <u>''Configuration Items''</u>. The ''[[Glossary|ASM]]'' and/or [[Glossary|''CMS'']] ''[[Glossary|modules]]'' features are made available here (e.g. view of ''[[Glossary|configuration item]]'' details, ''[[Glossary|configuration exploration]]'' or ''[[Glossary|impact analysis]]'').
 +
 
 +
==== Change management ====
 +
A ''[[Glossary|release]]'' may include one or more ''[[Glossary|changes]].''  The relationship between a ''[[Glossary|release]]'' and and [[Glossary|change]] can be created from the ''[[Glossary|change]]'' but is is more frequently created working from the ''[[Glossary|release]]''. In any case, the relation from the ''[[Glossary|change]]'' can be created from the ''[[Glossary|tickets]]'' tab ''<u>Related Items</u> ''and, in particular, the sub tab ''<u>Configuration Items</u>'' by using the '''ADD EXISTING''' or '''SELF SERVICE''' commands.  
  
−
==== Release and deployment management ====
+
==== Deployment Change ====
−
A ''[[Glossary|release]]'' may include one or more ''[[Glossary|changes]].''  The relationship between a ''[[Glossary|release]]'' and and [[Glossary|change]] can be created from the ''[[Glossary|change]]'' but is is more frequently created working from the ''[[Glossary|release]]''. In any case, the relation from the ''[[Glossary|change]]'' can be created from the ''[[Glossary|tickets]]'' tab ''<u>Related Items</u> ''and, in particular, the sub tab ''<u>Configuration Items</u>'' by using the '''ADD EXISTING''' or '''SELF SERVICE''' commands. <nowiki/>
+
A ''[[glossary|deployment change]]'' may be opened automatically, by means of a command button and only in specific statuses (see the workflow statuses table above), in specific statuses of the ''[[glossary|release]]''. Once opened, the ''[[glossary|deployment change]]'' is kept linked to the ''[[glossary|release]]''.   <nowiki/>
  
 
== Services ==
 
== Services ==
−
Different ''[[Get started with itmSUITE®|services]]'' are configured for different ''[[Glossary|change]]'' domain areas as illustrated in the following table.
+
Different ''[[Get started with itmSUITE®|services]]'' are configured for different ''[[Glossary|release]]'' domain areas as illustrated in the following table.
  
 
{| class="wikitable"
 
{| class="wikitable"
−
! ''[[Glossary|Incidents]]'' domain areas !! ''[[Glossary|Service]]'' !! ''[[Glossary|Service manager]]''
+
! ''[[Glossary|Releases]]'' domain areas !! ''[[Glossary|Service]]'' !! ''[[Glossary|Service manager]]''
  
 
|-
 
|-
Riga 397: Riga 386:
  
 
== Management information ==
 
== Management information ==
−
Many management information are available as fields in the ''[[Glossary|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|release]]'' 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"
 
{| class="wikitable sortable"
Riga 403: Riga 392:
  
 
|-
 
|-
−
| <u>''General Information''</u> || <u>Ticket Op Status</u> || To show the operational status of the ''[[Glossary|change]]'', see ''[[Glossary|workflow statuses]]'' in [[Incident Management#Process|Process]] section of this page. ||Status changes are performed by means of the '''Save&Next''' command.
+
| <u>''General Information''</u> || <u>Project/Service</u> || The ''[[Glossary|project]]'' or ''[[Glossary|service]]'' on which the ''[[Glossary|release]]'' is being managed. ||This is set at open time and cannot be changed later.
−
 
 
−
|-
 
−
| ''<u>General Information</u>'' || <u>Request Name</u> ||  To show the ''[[Glossary|SRCS]]''[[Glossary| ''request'']] invoked
 
−
||
 
  
 
|-
 
|-
−
| ''<u>General Information</u>'' || <u>Short Description</u> || To provide a short description of the ''[[Glossary|change]]''. ||Always visible.
+
| ''<u>General Information</u>'' || <u>Short Description</u> || To provide a short description of the ''[[Glossary|release]]''. ||Always visible.
  
−
|-
 
−
| <u>''General Information''</u> || <u>Requester</u> || To identify the name of the requester (who has requested the ''[[Glossary|change]]''). ||A list is presented, influenced by.... TBC
 
  
 
|-
 
|-
−
| <u>''General Information''</u> || <u>Creation Date</u> || To show the date and time the ''[[Glossary|change]]'' was created. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u>'' tab for more detailed tracking information.
+
| <u>''General Information''</u> || <u>Creation Date</u> || To show the date and time the ''[[Glossary|release]]'' was created. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u>'' tab for more detailed tracking information.
  
 
|-
 
|-
−
| <u>''General Information''</u> || <u>Edit Date</u> || To show the date and time the ''[[Glossary|change]] ''was last updated. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u> ''tab for more detailed tracking information.
+
| <u>''General Information''</u> || <u>Last Update</u> || To show the date and time the ''[[Glossary|release]] ''was last updated. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u> ''tab for more detailed tracking information.
  
 
|-
 
|-
−
| <u>''General Information''</u> || <u>Creation User</u> || To show the ''[[Glossary|user]]'' who created the ''[[Glossary|change]]''. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u> ''tab for more detailed tracking information.
+
| <u>''General Information''</u> || <u>Creation User</u> || To show the ''[[Glossary|user]]'' who created the ''[[Glossary|release]]''. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u> ''tab for more detailed tracking information.
  
 
|-
 
|-
−
| <u>''General Information''</u> || <u>Edit User</u> || To show the ''[[Glossary|user]]'' who updated the ''[[Glossary|change]]'' last. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u> ''tab for more detailed tracking information.
+
| <u>''General Information''</u> || <u>Update User</u> || To show the ''[[Glossary|user]]'' who updated the ''[[Glossary|release]]'' last. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u> ''tab for more detailed tracking information.
  
 
|-
 
|-
−
| <u>''Ticket Classification''</u> || <u>Project/Service</u> || To show the ''[[Glossary|service]]'' (or [[Glossary|''project'']]) to which the ''[[Glossary|change]]'' is related. ||This is automatically set at open time and can't be modified.
+
| ''<u>Release Classification</u>'' || <u>Ticket Type</u> || To show the type of ''[[Glossary|workflow]]'' executed. ||This is automatically set at open time and can't be modified''.''
  
 
|-
 
|-
−
| ''<u>Ticket Classification</u>'' || <u>Ticket Type</u> || To show the type of ''[[Glossary|workflow]]'' executed. ||This is automatically set at open time and can't be modified''.''
+
| <u>''Release Classification''</u> || <u>Ticket Op Status</u> || To show the operational status of the ''[[Glossary|release]]'', see ''[[Glossary|workflow statuses]]'' in [[Release Management#Process|Process]] section of this page. ||Status changes are performed by means of the '''Save&Next''' command.
  
 
|-
 
|-
−
| ''<u>Ticket Classification</u>'' || <u>Chage Area</u> <u>Change Objective</u> <u>Change Type</u> <u>Change Categor</u>y
+
| ''<u>Release Classification</u>'' || <u>Product</u> || This field allow to select one or more products which are released.
−
|| To set the ''[[Glossary|change]]'' key classification information.This is used for statistic reasons but the <u>Change Category</u> may also be configured to drive the ''[[Glossary|change]]'' authorization. ||<u>Change Area</u>, <u>Change Objective</u> and <u>Change Type</u> are independent fields. <u>Change Category</u> is available only if <u>Change Type</u> is set to "Normal": In such a case, its value is influenced by the ''[[Glossary|change]]'' assessment fields (see below). The classification information initially provided can be changed.
+
||
  
 
|-
 
|-
−
| ''<u>Ticket Classification</u>'' || <u>Change Scope</u>  
+
| ''<u>Release Classification</u>'' || <u>Target Environment</u> || This field allows to define the target environment where the ''[[Glossary|release]]'' is to be installed.
−
|| To set the ''[[Glossary|change]]'' scope.This is typically used for statistic reasons. ||The classification information initially provided can be changed.
+
||There could be more than one installation of the ''[[glossary|release]]'' in different environments (test, acceptance, live) managed with the ''[[glossary|deployment change]]'' process.
  
 
|-
 
|-
−
| ''<u>Ticket Classification</u>'' || <u>Service impact</u> <u>Capacity impact</u> <u>Security impact</u> <u>Cost estimation</u> <u>Performance impact</u>
+
| ''<u>Release Classification</u>'' || <u>Release Type</u> || This is the type of the release.  
−
|| These fields are the ''[[Glossary|change]]'' assessment elements. The values given will influence the <u>Change Category</u> value. ||The classification information initially provided (number and content of fields) as well as the rules to influence the <u>Change Category</u> can be changed.
+
||
  
 
|-
 
|-
−
| <u>''Prioritisation & Planning''</u> || <u>Required Solution Date</u> || To provide the date of ''[[Glossary|change]]'' implementation required by the <u>Requester</u>. ||  
+
| ''<u>Release Classification</u>'' || <u>Release Number</u> || The number of the release.
 +
||
  
 
|-
 
|-
−
| <u>''Prioritisation & Planning''</u> || <u>User Priority</u> || To provide the priority given to the ''[[Glossary|change]]'' by the <u>Requester</u>. ||A four level scale is set but it can be changed. 
+
| <u>''Management''</u> || <u>Supervising Team</u> || This field allows to define the supervising team for the release. ||
  
 
|-
 
|-
−
| <u>''Prioritisation & Planning''</u> || <u>Forecasted Solution Date</u> || To provide the date of ''[[Glossary|change]] ''implementation forecasted. ||
+
| <u>''Management''</u> || <u>Release Team</u> || To define the team to which the'' [[Glossary|release]]'' is assigned for execution. ||
  
 
|-
 
|-
−
| <u>''Prioritisation & Planning''</u> || <u>Forecasted Solution Date</u> || To set the forecasted resolution date and time for the ''[[Glossary|change]]''. ||
+
| <u>''Management''</u> || <u>Release Owner</u> || To define who is the owner who should monitor the lifecycle of the ''[[Glossary|release]]''. ||
  
 
|-
 
|-
−
| <u>''Ownership and Groups''</u> || <u>Master SG</u> || To define the supervising team. ||This is set by the service manager and mandatory from the <u>Ticket Op Status</u> "In Analysis".
+
| <u>''Release Details''</u> || <u>Description</u> || To provide a more detailed description of the ''[[Glossary|release]]''. ||An auto tracking field is used enabling to view the ''[[Glossary|user]]'' who has updated.
  
 
|-
 
|-
−
| <u>''Ownership and Groups''</u> || <u>Solution Group</u> || To define the team to which the'' [[Glossary|change]]'' is assigned for analysis and/or implementation. ||This is set by the service manager and mandatory from the <u>Ticket Op Status </u>"Approval Requested".
+
| <u>''Release Details''</u> || <u>Comments</u> || To provide helpful comments. ||An auto tracking field is used enabling to view the ''[[Glossary|user]] ''who has updated.
−
 
 
−
|-
 
−
| <u>''Ownership and Groups''</u> || <u>Owner</u> || To define who is the ''[[Glossary|change]]'' owner who should monitor the lifecycle of the ''[[Glossary|change]]''. ||This is set by the service manager and mandatory from the <u>Ticket Op Status</u> "In Analysis". He/she can be changed by the service manager and the <u>Owner</u> him/herseilf.
 
−
 
 
−
|-
 
−
| <u>''Ticket Details''</u> || <u>Description</u> || To provide a more detailed description of the ''[[Glossary|change]]''. ||An auto tracking field is used enabling to view the ''[[Glossary|user]]'' who has updated.
 
−
 
 
−
|-
 
−
| <u>''Ticket Details''</u> || <u>Analysis</u> || To provide a detailed analysis of the assessment of the ''[[Glossary|change]]''. ||An auto tracking field is used enabling to view the ''[[Glossary|user]] ''who has updated.
 
−
 
 
−
|-
 
−
| <u>''Ticket Details''</u> || <u>Solution</u> || To describe the required implementation for the ''[[Glossary|change]]''. ||An auto tracking field is used enabling to view the ''[[Glossary|user]] ''who has updated.
 
−
 
 
−
|-
 
−
| <u>''Ticket Details''</u> || <u>Comments</u> || To provide helpful comments. ||An auto tracking field is used enabling to view the ''[[Glossary|user]] ''who has updated.
 
  
 
|}
 
|}
  
−
Fields can be mandatory to save the ''[[Glossary|change]]'' in some [[Glossary|''workflow statuses'']]. These fields are highlighted with a red asterisk.
+
Fields can be mandatory to save the ''[[Glossary|release]]'' in some [[Glossary|''workflow statuses'']]. These fields are highlighted with a red asterisk.
  
 
== Views ==
 
== Views ==
Riga 486: Riga 455:
  
 
{| class="wikitable"
 
{| class="wikitable"
−
! View !! Content !! Requester !! Change owner !! Technical team !! Service manager !! Change authority
+
! View !! Content !! Requester !! Release owner !! Technical team !! Service manager !! Change authority !! Release Manager
  
 
|-
 
|-
−
| Changes completed || ''[[Glossary|Changes]]'' in statuses "Completed", "In Review".  || X ||  || || ||  
+
| Releases completed || ''[[Glossary|Releases]]'' in statuses "Completed", "In Review".  || X ||  || || X
 +
|| ||
  
 
|-
 
|-
−
| Changes requested || ''[[Glossary|Changes]]'' in status "Requested".  ||  ||   
+
| Releass requested || ''[[Glossary|Releases]]'' in status "Requested".  ||  X
−
|| ||X ||
+
||   
 +
|| ||X || ||X
  
 
|-
 
|-
−
| Changes owned || ''[[Glossary|Changes]] ''in all the statuses but "Opened", "Cancelled", "Aborted", "Closed" where <u>Owner</u> is the logged ''[[Glossary|resource]].''  ||  ||  X || || ||
+
| Releases owned || ''[[Glossary|Releases]] ''in all the statuses but "Opened", "Cancelled", "Aborted", "Closed" where <u>Owner</u> is the logged ''[[Glossary|resource]].''  ||  ||  X || || || ||
  
 
|-
 
|-
−
| Changes routed to my team || ''[[Glossary|Changes]]'' in all the statuses but "Opened", "Cancelled", "Aborted", "Closed" where <u>Solution Group</u> is the ''[[Glossary|solution group]]'' to which the logged ''[[Glossary|resource]]'' belongs to.    ||  || || X || ||
+
| Releases routed to my team || ''[[Glossary|Releases]]'' in all the statuses but "Opened", "Cancelled", "Aborted", "Closed" where the <u>Release Team</u> is the group to which the logged ''[[Glossary|resource]]'' belongs to.    ||  || || X || || ||
  
 
|-
 
|-
−
| Changes assigned to me || ''[[Glossary|Changes]]'' in all the statuses but "Opened", "Cancelled", "Aborted", "Closed" where the <u>Ticket Worker</u> is the logged ''[[Glossary|resource]]''.    ||  ||  
+
| Releases assigned to me || ''[[Glossary|Releases]]'' in all the statuses but "Opened", "Cancelled", "Aborted", "Closed" where the <u>Ticket Worker</u> is the logged ''[[Glossary|resource]]''.    ||  ||  
−
|| X || ||
+
|| X || || ||
  
 
|-
 
|-
−
| Changes suspended || ''[[Glossary|Changes]]'' in status "Suspended".    ||  || X
+
| Releases suspended || ''[[Glossary|Releases]]'' in status "Suspended".    ||  || X
−
||  ||X ||
+
||  ||X || ||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
+
| Releases to review || ''[[Glossary|Releases]]'' in status "Completed" where <u>Release Type</u> is "Emergency" or where "Major".    ||  || X
−
||  ||X ||
+
||  ||X || ||X
  
 
|-
 
|-
−
| Changes to authorize for implementation || ''[[Glossary|Changes]]'' in status "Implementation Approval Requested".    ||  ||  ||  || ||X
+
| Releases to authorize for implementation || ''[[Glossary|Releases]]'' in status "Implementation Approval Requested".    ||  ||  ||  || ||X ||
  
 
|-
 
|-
−
| Changes to authorize for deployment || ''[[Glossary|Changes]]'' in status "Deployment Approval Requested".    ||  ||  
+
| Releases to authorize for deployment || ''[[Glossary|Releases]]'' in status "Deployment Approval Requested".    ||  ||  
−
||  || ||X
+
||  || ||X ||
  
 
|-
 
|-
−
| Changes evaluated by Change Authority || ''[[Glossary|Changes]]'' in status "Approved" or "Not Approved".    ||  || X
+
| Releases evaluated by Change Authority || ''[[Glossary|Releases]]'' in status "Approved" or "Not Approved".    ||  || X
 
||  || X
 
||  || X
−
||
+
|| ||X
  
 
|-
 
|-
−
| Changes approved for deployment || ''[[Glossary|Chnages]]'' in status "Deployment Approved".    ||  || X
+
| Changes approved for deployment || ''[[Glossary|Releases]]'' in status "Deployment Approved".    ||  || X
 
||  || X
 
||  || X
−
||
+
|| ||X
−
 
 
  
 
|}
 
|}
  
−
Additionally, the following ''[[Glossary|views]]'' are made available in the '''''Change''''' menu for all the organizational roles:
+
Additionally, the following ''[[Glossary|views]]'' are made available in the '''''Release''''' menu for all the organizational roles:
  
 
{| class="wikitable"
 
{| class="wikitable"
Riga 539: Riga 509:
  
 
|-
 
|-
−
| Changes active || ''[[Glossary|Changes]] ''in all the statuses but "Cancelled", "Aborted", "Suspended", "Closed"
+
| Releases active || ''[[Glossary|Releases]] ''in all the statuses but "Cancelled", "Aborted", "Suspended", "Closed"
  
 
|-
 
|-
−
| Changes suspended || ''[[Glossary|Changes]]'' in status "Suspended
+
| Releases suspended || ''[[Glossary|Releases]]'' in status "Suspended
  
 
|-
 
|-
−
| Changes closed || ''[[Glossary|Changes]]'' in status "Closed"
+
| Releases closed || ''[[Glossary|Releases]]'' in status "Closed"
  
 
|-
 
|-
−
| Changes cancelled || ''[[Glossary|Changes]]'' in status "Cancelled"
+
| Releases cancelled || ''[[Glossary|Releases]]'' in status "Cancelled"
  
 
|}
 
|}
Riga 558: Riga 528:
  
 
|-
 
|-
−
|A ''[[Glossary|change]] ''is requested || Service manager || Alert that there is a ''[[Glossary|change]]'' 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 576: 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, release manager || Alert that the change authority has given a feedback on a ''[[Glossary|release]]'' deployment request.
  
 
|}
 
|}
  
 
== Reporting ==
 
== 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:
 
The following table lists the reports available by default and their visibility:
Riga 607: 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.
  
 
|}
 
|}
 
<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.
+
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 ==
 
== 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]]
 
[[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.
 
'''<u>NOTE</u>''': the '''EXPLORE WORKFLOW '''command is available only if the ''[[Glossary|ticket]]'' is first saved.
Riga 638: Riga 608:
 
For more information on how to use any workflows, including incident management, please refer to the [[workflow execution guide]].
 
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]]''
+
# Login as "appspecialist" ''[[Glossary|user]]''
 
#  Activate the '''''Self Service''''' menu
 
#  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  
 
# 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]] ''
 
#*  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/>

Versione attuale delle 10:15, 27 apr 2017

Release and Deployment Management process is supported by a SM workflow cartridge that enables the execution of the process according to the ITIL and ISO/IEC 20000 guidelines.

Of course the preconfigured process (the workflow cartridge) is just an accelerator and the tuning / completion of the initial configuration will still be required. To this aim, the Workflow Engine guide may be useful.

IMPORTANT NOTE: the configuration below is only one of the possible configuration to deal with the 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

The preconfigured process has the objective to facilitate and support the effective and efficient execution of releases. At the core of the process configuration is the following operational model.

Release Management operational model

The requester, a service manager, an authorized member of the service desk or a technical team member (e.g. a developer) or the change Management process requires a new release. The release manager takes in charge it and assigns an owner who coordinates all the tasks needed to fulfil the release. If necessary, the owner requests the releasee authorizations to the change authority. Finally, he/she activates the deployment change process in order to complete the installation of the release in a target environment (e.g. test, production).

Roles

For this process, the following organizational roles are defined:

Organizational role Description itmSUITE® role mapping
Requester
  • Opens requests for releases on behalf of himself/herself or for a third party
 This role is mapped on:
  • service managers (see after);
  • service desk members (system resources with user of user type "Resource"; the login identifier of this user is "SDSpecialist");
  • technical team members (see after).
Release Manager
  • Receives and evaluates release requests
  • Assigns a release owner
  • May act as a release owner
 This role is mapped on the service manager(r) of the service on which the release is requested.
Release owner
  • Requires release approval to the change authority after its assessment is completed
  • Assign tasks to be performed to complete the release (e.g. opens deployment changes)
  • Watches over and monitors the release along all its life cycle ensuring target service levels are achieved
  • Activates escalation/ routing/ requests
  • Manages all the communications with the requester
  • Checks the implementation and sets the releasee to completed
  • Closes the release after completing the final checks
 This role is assigned to the manager of the group "Release Management"; the login identifier of this user is "ReleaseManager".
Technical team member A technical team member may first of all be a requester (see before). However he/she may play an active role in the preparation and installation of the release. In detail
  • He/she receives the notification on the assignment of an activity concerning a release (e.g. conducting the assessment or designing/implementing it)
  • Carries out the assigned tasks
  • Notices when completed or unable to complete
 There are several technical teams predefined for different domains. The following table shows which users are members of each team.
Domain Group Member

users

Application management "Application Management" "AppManager"

"AppSpecialist"

Personal devices management "Personal Management" "PersonalManager"

"PersonalSpecialist"

Network management "Network Management" "NetManager"

"NetSpecialist"

Server management "Server Management" "ServerManager"

"ServerSpecialist"

Technical team manager
  • Receives the notification about the assignment of the release to his/her team in order to implement it
  • Assign the member of his/her team who should work on it (this can be done by setting the ticket worker or creating and assigning ticket activities)
  • Watches over and monitors the work of his/her team
 There are several technical teams predefined for different domains. The following table shows which users are set as solution group manager for each domain.
Domain Group Group manager
Application management "Application Management" User "AppManager".
Personal devices management "Personal Management" User "Personal Manager".
Network management "Network Management" User "NetManager".
Server management "Server Management" User "ServerManager".
Service manager The service manager may act as a requester of a release (see before). The service manager(s) of the service on which the release is managed acts as the release manager(s). There are different service managers configured for specific services. See Services section in this page for further information.
Change authority This role is mapped based on the required authorization and release classification.

For release implementation authorization:

Release Type Change authority
"Emergency" Service manager
"Minor" Service manager
"Major" CAB

The CAB is mapped on a group: "CAB".

For release deployment authorization:

Change Type Change authority
"Emergency" Service manager
"Minor" Release manager
"Major" Service manager

Process

As for all workflows, new releases can be created by using the self service portal, accessible by means of Self Service menu.

The following requests which trigger a new instance of the release and deployment management process are configured and available in the self service portal:

Self service topic Self service category Self service request Authorized roles
"Applications" "Application Management" "Release" (open a release) Requesters

A release may also be automatically opened during the execution of the change management process.

A workflow is configured to support the release and deployment management process. The workflow is characterized by workflow statuses and workflow transitions. The figures below illustrate the process.

Release management process (1 of 3).
Release management process (2 of 3).
Release management process (3 of 3).

The table below explains the meaning of each workflow status.

Workflow status Description
"Default" A preliminary status which is displayed when a release is created.
"Opened" The release has been recorded.
"Requested" The release is confirmed and has been requested.
"In Analysis" The release assessment and planning is ongoing.
"Implementation Approval Requested" The release approval request for implementation is submitted to the change authority.
"Approved" The release is approved for implementation.
"Not Approved" The release is not approved for implementation.
"In Progress" The release implementation is ongoing.
"Ready for Test" The release is ready for testing. In this status, a deployment change can be opened to install the release in a test environment.
"In Test" The release testing is ongoing.
"Deployment Approval Requested" The release approval request for deployment is submitted to the change authority.
"Deployment Approved" The release is approved for deployment. In this status, a deployment change can be opened to install the release in the live environment.
"Completed" The release is completed.
"Change Review" The release review is ongoing.
"Cancelled" The release is not confirmed and, therefore, cancelled.
"Suspended" The release execution is temporarily suspended. In this status service levels calculation are suspended too.
"Aborted" The release execution is aborted.
"Closed" The release closure has been confirmed.

And finally the table below explains the roles authorized to execute the workflow transitions.

Source status Destination status Authorized executors Comment
"Default" "Opened" Requester

service manager.

See the self service portal configuration previously described.
"Opened" "Requested" Requester, service manager, release manager.


"Opened" "Cancelled" Requester, service manager.
"Requested" "Opened" Requester, service manager, release manager.
"Requested" "Cancelled" Requester, service manager, release manager.
"Requested" "In Analysis" Release owner, release manager.
"Deployment Approved" "Aborted" Release owner, release manager.
"In Analysis" "Requested" Release owner, release manager.
"In Analysis" "Approval Requested" Release owner, release manager.
"In Analysis" "Cancelled" Release owner, release manager.


"Approval Requested" "Approved" Change authority. Depending on release classification (see roles for more details).
"Approval Requested" "Not Approved" Change authority. Depending on release classification (see roles for more details).
"Approval Requested" "In Analysis" Release owner, release manager.
"Not Approved" "Cancelled" Release owner, release manager.
"Approved" "In Progress" Release owner, release manager, technical team member.
"Approved" "Suspended" Release owner, release manager.


"Approved" "Aborted" Release owner, release manager.
"Suspended" "In Progress" Release owner, release manager.
"In progress" "Suspended" Release owner, release manager.
"In progress" "Aborted" Release owner, release manager.
"In progress" "Ready for Test" Release owner, release manager technical team member.
"In progress" "In Test" Release owner, release manager, technical team member.
"In progress" "Deployment Approval Requested" Release owner, release manager.
"In progress" "Completed" Release owner, release manager.
"Ready for Test" "In Test" Release owner release manager, technical team member.
"Ready for Test" "Suspended" Release owner, release manager.
"Ready for Test" "Aborted" Release owner, release manager.
"In Test" "Deployment Approval Requested" Release owner, release manager.
"In Test" "Suspended" Release owner, release manager.
"In Test" "Aborted" Release owner, release manager.
"Deployment Approval Requested" "Deployment Approved" Change authority.
"Deployment Approval Requested" "Suspended" Release owner, release manager.
"Deployment Approval Requested" "Aborted" Release owner, release manager.
"Deployment Approved" "Completed" Release owner, release manager.


"Completed" "Change Review" Release owner, release manager.
"Completed" "Closed" Release owner, release manager.
"Change review" "Closed" Release owner, release manager.
"Not Approved" "In Analysis" Release owner, release manager.

Related processes

Several other IT Service Management processes are related to the release and deploymentmanagement one. Some basic interfaces are provided. The tab Related Items of the release and, in particular, the sub tab Tickets of it allows to view all the existing relationships between the release and other processes (managed through tickets).

Incident management

The relationship is indirect: a release may be related to changes which implement the solution of incidents.

Problem management

The relationship is indirect: a release may be related to changes which implement the solution of problems.

Asset management and configuration management

It is possible to relate configuration items to a release by using the tab Related Items and, in particular, the sub tab Configuration Items. The ASM and/or CMS modules features are made available here (e.g. view of configuration item details, configuration exploration or impact analysis).

Change management

A release may include one or more changes. The relationship between a release and and change can be created from the change but is is more frequently created working from the release. In any case, the relation from the change can be created from the tickets tab Related Items and, in particular, the sub tab Configuration Items by using the ADD EXISTING or SELF SERVICE commands.

Deployment Change

A deployment change may be opened automatically, by means of a command button and only in specific statuses (see the workflow statuses table above), in specific statuses of the release. Once opened, the deployment change is kept linked to the release.

Services

Different services are configured for different release domain areas as illustrated in the following table.

Releases domain areas Service Service manager
Application management Only one application, and the related service ("itmCLOUD") is configured. The user "servicemanager" is configured as service manager.
Personal devices management "Personal Device Management". The user "personalmanager" is configured as service manager.
Network management "Network Management" The user "netmanager" is configured as service manager.
Server management "Server Management" The user "servermanager" is configured as service manager.

Management information

Many management information are available as fields in the release management configured form. The following table illustrates the intended use of key information and its behaviour. NOTE: 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.

Information group or tab Field Purpose Comments
General Information Project/Service The project or service on which the release is being managed. This is set at open time and cannot be changed later.
General Information Short Description To provide a short description of the release. Always visible.


General Information Creation Date To show the date and time the release was created. This information is automatically recorded and cannot be manually changed. See History tab for more detailed tracking information.
General Information Last Update To show the date and time the release was last updated. This information is automatically recorded and cannot be manually changed. See History tab for more detailed tracking information.
General Information Creation User To show the user who created the release. This information is automatically recorded and cannot be manually changed. See History tab for more detailed tracking information.
General Information Update User To show the user who updated the release last. This information is automatically recorded and cannot be manually changed. See History tab for more detailed tracking information.
Release Classification Ticket Type To show the type of workflow executed. This is automatically set at open time and can't be modified.
Release Classification Ticket Op Status To show the operational status of the release, see workflow statuses in Process section of this page. Status changes are performed by means of the Save&Next command.
Release Classification Product This field allow to select one or more products which are released.
Release Classification Target Environment This field allows to define the target environment where the release is to be installed. There could be more than one installation of the release in different environments (test, acceptance, live) managed with the deployment change process.
Release Classification Release Type This is the type of the release.
Release Classification Release Number The number of the release.
Management Supervising Team This field allows to define the supervising team for the release.
Management Release Team To define the team to which the release is assigned for execution.
Management Release Owner To define who is the owner who should monitor the lifecycle of the release.
Release Details Description To provide a more detailed description of the release. An auto tracking field is used enabling to view the user who has updated.
Release Details Comments To provide helpful comments. An auto tracking field is used enabling to view the user who has updated.

Fields can be mandatory to save the release in some workflow statuses. These fields are highlighted with a red asterisk.

Views

The following views are made available in the Tickets area of the home page:

View Content Requester Release owner Technical team Service manager Change authority Release Manager
Releases completed Releases in statuses "Completed", "In Review". X X
Releass requested Releases in status "Requested". X X X
Releases owned Releases in all the statuses but "Opened", "Cancelled", "Aborted", "Closed" where Owner is the logged resource. X
Releases routed to my team Releases in all the statuses but "Opened", "Cancelled", "Aborted", "Closed" where the Release Team is the group to which the logged resource belongs to. X
Releases assigned to me Releases in all the statuses but "Opened", "Cancelled", "Aborted", "Closed" where the Ticket Worker is the logged resource. X
Releases suspended Releases in status "Suspended". X X X
Releases to review Releases in status "Completed" where Release Type is "Emergency" or where "Major". X X X
Releases to authorize for implementation Releases in status "Implementation Approval Requested". X
Releases to authorize for deployment Releases in status "Deployment Approval Requested". X
Releases evaluated by Change Authority Releases in status "Approved" or "Not Approved". X X X
Changes approved for deployment Releases in status "Deployment Approved". X X X

Additionally, the following views are made available in the Release menu for all the organizational roles:

View Content
Releases active Releases in all the statuses but "Cancelled", "Aborted", "Suspended", "Closed"
Releases suspended Releases in status "Suspended
Releases closed Releases in status "Closed"
Releases cancelled Releases in status "Cancelled"

Notifications

The following notifications are configured:

Trigger Recipients Purpose
A release is requested Release manager Alert that there is a release to manage.
A release is assigned a owner Release owner Alert that the release was assigned to him/her.
A release team is assigned or changed for the release Release team Alert that there are resource(s) to allocate to manage the release.
A release review shall be executed (the release is in workflow status "Release Review") Release owner, release manager Alert that a release review is to be done.
A release is completed The release creator, the requester Alert that the release is deployed.
A ticket worker is assigned The assigned ticket worker Alert that there is work to be done.
A release is suspended The release creator, the requester, the service manager, the release manager, the releasee owner Alert that the release is suspended.
An release is closed The release creator, the requester, the service manager, the release manager, the change owner Alert that the release has been closed.
A release is cancelled The release creator, the requester, the service manager, the release manager, the change owner Alert that the change has been cancelled.
A release implementation approval has been requested Change authority Alert that a release implementation request has to be examined.
A release implementation approval request has been examined Release owner, release manager Alert that the change authority has given a feedback on a release implementation request.
A release deployment approval has been requested Change authority Alert that a release deployment request has to be examined.
A release deployment approval request has been examined Release owner, release manager Alert that the change authority has given a feedback on a release deployment request.

Reporting

A set of standard reports are made available for the release management process. It is not required to have the REP module to use them, however the 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:

Report name Content Access
Release per category - trend An histogram showing the release volumes per category (Release Type)monthly trend. Release manager, service managers and technical team members.
Release per category - volume A pie containing the split of releases per category (Release Type). Release manager, service managers and technical team members.
Release per service - trend An histogram showing the release volumes per service monthly trend. Release manager, servie managers and technical team members.
Release per service - volume A pie containing the split of releases per service. Release manager, servie managers and technical team members.
Release per service/category - volume An histogram showing the releases volume per service and category. Release manager, service managers and technical team members.
Release - analysis time A pie showing the percentage of releases respecting the target defined for the "Analysis time"* objective (the time elapsed from the "Requested" to the "In Analysis" workflow status. Release manager, service managers and technical team members.

* "Analysis time" is defined within the OCE module.

A basic form of reporting is also provided by views. Views basically allow to list releases and their attributes but may also be configured to calculates sums, averages on some of them. The available views are illustrated in the dedicated section of this page.

Examples of use

In this section some examples of use of the configured release management process are given.

If you get lost, any time use the EXPLORE WORKFLOW command of the release management form. This enables to view the status of the workflow as shown in the figure below. By clicking on a relationship between workflow statuses, roles and users enabled to perform it are presented.

Explore Workflow window

NOTE: the EXPLORE WORKFLOW command is available only if the ticket is first saved.

For more information on how to use any workflows, including incident management, please refer to the workflow execution guide.

Create and request a new release as a final user

  1. Login as "appspecialist" user
  2. Activate the Self Service menu
  3. Choose a self service topic, self service category and finally "Release" as self service request (this determines the creation of a new release)
  4. Fill the release form, at least with mandatory fields, and save with the SAVE command (the release is now in workflow status "Opened")
  5. Set the release in workflow status "Requested" with the SAVE & NEXT command

You have now saved the release, take note of the ticket number for further reference and use.

Assign a release for analysis as a release manager

  1. Login as "releasemanager"
  2. Open the the desired release; you can do it quickly either by
  3. Assign the key roles
    • Fill the release form with Release Owner, Release Team and, may be, Supervising Team
    • Pressing the SAVE & NEXT command, choose the "1. Assign ticket" workflow transition

The release is now in workflow status "In Analysis".

Estratto da "http://wiki.itmsuite.eu/index.php?title=Release_and_Deployment_Management&oldid=3010"