become-itil-foundation-certified-abhinav-kaiser(www.ebook-dl.com)

Chapter 6 ■ Service Transition
6.4.2.2 Scope of Release and Deployment Management
As mentioned earlier, all changes come under the ambit of the release and deployment
management process. I earlier mentioned that build, test, implementation, and
verification are the key activities of this process. However, it is possible that certain
activities, such as building and testing, may not be applicable for all changes, say for
hardware changes where parts get replaced. There is no build and perhaps not a lot of
testing that could be done unless the hardware is placed on the network.
In principle, the scope of release and deployment management starts at the build
stage and traverses through testing, deployment, and verification and ends when the
responsibilities are handed over to service operations for maintaining the status quo.
The set of configuration items that could possibly come under the release and
deployment management process is defined by the customer. The following set of CIs
generally figure in most implementations:
• Hardware CIs such as servers, routers, switches, and storage
• Virtual servers such as VMWare and Citrix
• Virtual storage servers
• Software and applications
• Database
• Staff training (handover to service operations) and training to users
• Documentation regarding release packages and the results of its
key activities
6.4.2.3 Four Phases of Release and Deployment Management
The release and deployment management has four major activities. These activities are
referred to as the four phases of release and deployment management:
1. Release and deployment planning
2. Release build and test
3. Deployment
4. Review and close
The four phases of release and deployment management are shown in Figure 6-3.
134