A framework for cut-over management
The purpose of this paper is to provide a governance structure for IT-related projects in order to assure a safeguarded and timely transition to a productive environment. This transitioning, which rarely exceeds a weekend, is colloquially called ‘cut-over’, ‘rollout’ or ‘deployment’. The governance...
| Main Author: | |
|---|---|
| Format: | Article |
| Language: | English |
| Published: |
PeerJ Inc.
2015-11-01
|
| Series: | PeerJ Computer Science |
| Subjects: | |
| Online Access: | https://peerj.com/articles/cs-29.pdf |
| _version_ | 1818694490663157760 |
|---|---|
| author | Guido Nageldinger |
| author_facet | Guido Nageldinger |
| author_sort | Guido Nageldinger |
| collection | DOAJ |
| description | The purpose of this paper is to provide a governance structure for IT-related projects in order to assure a safeguarded and timely transition to a productive environment. This transitioning, which rarely exceeds a weekend, is colloquially called ‘cut-over’, ‘rollout’ or ‘deployment’. The governance structure is defined in accordance with a set of project-specific deliverables for a cascade-type procedural project-management model, which is integrated within an Information Technology Infrastructure Library (ITIL)-orientated service organization. This integration is illustrated by the use of a semi-agile release model. Due to the release model selected, which is particularly characterized by its bundling of projects for a release-specific rollout (as it is referred to in the project documentation), a new definition and interpretation of deployment from a generic ITIL perspective is required. The facilitated release model requires a distinction between a project-specific cut-over and a release-specific rollout. This separation gives rise to two types of go-live scenarios: one for each participating project and one for each release. Additionally, an interplay between cut-over planning for a project and rollout planning for a release becomes apparent. Projects should already incorporate cut-over related deliverables in the initial planning phase. Even though consulting methodologies such as ASAP (Accelerated SAP), recommend scattered, project-specific deliverables useful for cut-over planning, this publication offers an integrated approach on how to prepare systematically for a project-specific cut-over with all required deliverables. The framework provided maps out ITIL’s release and deployment process by means of IT projects; furthermore it allows IT projects to interface easily with the ITIL change-management process. |
| first_indexed | 2024-12-17T13:30:25Z |
| format | Article |
| id | doaj.art-cce7df191f934e0583c774e3d86fdc24 |
| institution | Directory Open Access Journal |
| issn | 2376-5992 |
| language | English |
| last_indexed | 2024-12-17T13:30:25Z |
| publishDate | 2015-11-01 |
| publisher | PeerJ Inc. |
| record_format | Article |
| series | PeerJ Computer Science |
| spelling | doaj.art-cce7df191f934e0583c774e3d86fdc242022-12-21T21:46:35ZengPeerJ Inc.PeerJ Computer Science2376-59922015-11-011e2910.7717/peerj-cs.29A framework for cut-over managementGuido Nageldinger0Department of Testing and Release Management, Otto (GmbH & Co KG)—A member of the otto group, Hamburg, GermanyThe purpose of this paper is to provide a governance structure for IT-related projects in order to assure a safeguarded and timely transition to a productive environment. This transitioning, which rarely exceeds a weekend, is colloquially called ‘cut-over’, ‘rollout’ or ‘deployment’. The governance structure is defined in accordance with a set of project-specific deliverables for a cascade-type procedural project-management model, which is integrated within an Information Technology Infrastructure Library (ITIL)-orientated service organization. This integration is illustrated by the use of a semi-agile release model. Due to the release model selected, which is particularly characterized by its bundling of projects for a release-specific rollout (as it is referred to in the project documentation), a new definition and interpretation of deployment from a generic ITIL perspective is required. The facilitated release model requires a distinction between a project-specific cut-over and a release-specific rollout. This separation gives rise to two types of go-live scenarios: one for each participating project and one for each release. Additionally, an interplay between cut-over planning for a project and rollout planning for a release becomes apparent. Projects should already incorporate cut-over related deliverables in the initial planning phase. Even though consulting methodologies such as ASAP (Accelerated SAP), recommend scattered, project-specific deliverables useful for cut-over planning, this publication offers an integrated approach on how to prepare systematically for a project-specific cut-over with all required deliverables. The framework provided maps out ITIL’s release and deployment process by means of IT projects; furthermore it allows IT projects to interface easily with the ITIL change-management process.https://peerj.com/articles/cs-29.pdfReleaseProject-specific cut-overRelease-specific rolloutGo-live preparationGo-liveDeployment |
| spellingShingle | Guido Nageldinger A framework for cut-over management PeerJ Computer Science Release Project-specific cut-over Release-specific rollout Go-live preparation Go-live Deployment |
| title | A framework for cut-over management |
| title_full | A framework for cut-over management |
| title_fullStr | A framework for cut-over management |
| title_full_unstemmed | A framework for cut-over management |
| title_short | A framework for cut-over management |
| title_sort | framework for cut over management |
| topic | Release Project-specific cut-over Release-specific rollout Go-live preparation Go-live Deployment |
| url | https://peerj.com/articles/cs-29.pdf |
| work_keys_str_mv | AT guidonageldinger aframeworkforcutovermanagement AT guidonageldinger frameworkforcutovermanagement |