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

Recommendations

Info

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
Chapter 6 ■ Service Transition Auth Authorize release planning Release and deployment planning Change management Auth Auth Auth Authorize build and test Authorize check-in to DML Release build and test AuthAuthAuth Authorize deployment/ transfer/retirement Review and close Postimplementation review Deployment Transfer Auth Change management authorization Retirement Figure 6-3. Four phases of release and deployment management 6.4.2.3.1 Release and Deployment Planning A good amount of planning has to go into release activities. A good plan is equivalent to half of the job being done. To ensure that the release is successful, it is critical that the architects and other experts brainstorm various possibilities, risks, and mitigations. Before the plan gets under way, the change management typically provides approval to start the planning process. However, in practice, the approval to create release and deployment plans is provided from a different body such as a transition management group or a group that governs the projects that are chartered. In principle, these bodies govern the changes made to the system, and this can be the equivalent to change management authorization to create release and deployment management plans. 6.4.2.3.2 Release Build and Test The release and deployment plans are submitted to the CAB. The plans are dissected from every possible angle to identify loopholes and vulnerabilities. Upon successfully passing the CAB and change management scrutiny, the authorization to build and test the change is provided. Building a change amounts to code development, getting hardware ready, or the prerequisites for building the change. There are various types of testing. The most popular ones are unit tests (UTs), where individual components of a change are tested in isolation. Upon successful testing, the individual components are conjoined and a system integration test (SIT) is performed. After it successfully passes, users are asked to test the function in the user’s environment to check whether the change meets the requirements that are needed. This is called user acceptance testing (UAT). The testing is deemed complete after the user provides the okay that all elements of the change meet the requirement and are good to proceed. The definitive media library (DML) is a repository where all the original codes, software licenses, and other software components are stored, physically and logically. 135
Page 1 and 2:
Become ITIL Foundation Certified in
Page 3 and 4:
Become ITIL Foundation Certified in
Page 5 and 6:
Contents at a Glance About the Auth
Page 7 and 8:
■ Contents 1.8 Internal and Exter
Page 9 and 10:
■ Contents ■Chapter ■ 4: Serv
Page 11 and 12:
■ Contents 6.4 Service Transition
Page 13 and 14:
■ Contents ■Chapter ■ 9: ITIL
Page 15 and 16:
About the Technical Reviewer Sumit
Page 17 and 18:
Preface When my first book, Communi
Page 19 and 20:
CHAPTER 1 Service Management as a P
Page 21 and 22:
Chapter 1 ■ Service Management as
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
1.9.1.2 Process Deliver Specific Re
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Chapter 2 ■ Generic Concepts Chap
Page 37 and 38:
Chapter 2 ■ Generic Concepts Tabl
Page 39 and 40:
Chapter 2 ■ Generic Concepts 2.1.
Page 41 and 42:
Chapter 2 ■ Generic Concepts 2.2.
Page 43 and 44:
Chapter 2 ■ Generic Concepts ENAB
Page 45 and 46:
Chapter 2 ■ Generic Concepts Figu
Page 47 and 48:
Chapter 2 ■ Generic Concepts rece
Page 49 and 50:
CHAPTER 3 ITIL Service Lifecycle Th
Page 51 and 52:
Chapter 3 ■ ITIL Service Lifecycl
Page 53 and 54:
Page 55 and 56:
3.2 ITIL Roles Chapter 3 ■ ITIL S
Page 57 and 58:
3.2.6 Generic Role: Process Practit
Page 59 and 60:
Page 61 and 62:
CHAPTER 4 Service Strategy A strate
Page 63 and 64:
4.1.4 Patterns Chapter 4 ■ Servic
Page 65 and 66:
Chapter 4 ■ Service Strategy Serv
Page 67 and 68:
Chapter 4 ■ Service Strategy Figu
Page 69 and 70:
4.6.1.2 Risk Analysis Chapter 4 ■
Page 71 and 72:
Chapter 4 ■ Service Strategy know
Page 73 and 74:
4.8.1.1.3 Retired Services Chapter
Page 75 and 76:
Chapter 4 ■ Service Strategy thro
Page 77 and 78:
Chapter 4 ■ Service Strategy that
Page 79 and 80:
Chapter 4 ■ Service Strategy 2. V
Page 81 and 82:
Chapter 5 ■ Service Design Some e
Page 83 and 84:
Chapter 5 ■ Service Design 5.4 Fo
Page 85 and 86:
Chapter 5 ■ Service Design 4. Pro
Page 87 and 88:
Chapter 5 ■ Service Design • Se
Page 89 and 90:
Chapter 5 ■ Service Design To sta
Page 91 and 92:
Chapter 5 ■ Service Design 5.7.1.
Page 93 and 94:
Chapter 5 ■ Service Design Jan Fe
Page 95 and 96:
Chapter 5 ■ Service Design with t
Page 97 and 98: Chapter 5 ■ Service Design Think
Page 99 and 100: Chapter 5 ■ Service Design To sta
Page 101 and 102: Chapter 5 ■ Service Design have a
Page 103 and 104: Chapter 5 ■ Service Design Polici
Page 105 and 106: Chapter 5 ■ Service Design Tradit
Page 107 and 108: Chapter 5 ■ Service Design Unlike
Page 109 and 110: Chapter 5 ■ Service Design 5.7.5
Page 111 and 112: Chapter 5 ■ Service Design For ex
Page 113 and 114: Chapter 5 ■ Service Design Anyway
Page 115 and 116: Chapter 5 ■ Service Design 5.7.5.
Page 119 and 120: Chapter 5 ■ Service Design busine
Page 121 and 122: Chapter 5 ■ Service Design 3. Agr
Page 125 and 126: Chapter 5 ■ Service Design When d
Page 127 and 128: Chapter 5 ■ Service Design 7. If
Page 129 and 130: CHAPTER 6 Service Transition Transi
Page 131 and 132: Chapter 6 ■ Service Transition
Page 133 and 134: Chapter 6 ■ Service Transition
Page 135 and 136: 6.4.1.3 Types of Change Requests Ch
Page 137 and 138: Chapter 6 ■ Service Transition Cr
Page 139 and 140: Chapter 6 ■ Service Transition It
Page 141 and 142: 6.4.1.7.1 Create a Request for Chan
Page 143 and 144: 6.4.1.7.7 Review and Change Closure
Page 145 and 146: 6.4.1.10 Change Management Interfac
Page 147: Chapter 6 ■ Service Transition fr
Page 151 and 152: Chapter 6 ■ Service Transition an
Page 153 and 154: Chapter 6 ■ Service Transition Ac
Page 155 and 156: Chapter 6 ■ Service Transition Th
Page 157 and 158: Chapter 6 ■ Service Transition 6.
Page 159 and 160: Chapter 6 ■ Service Transition WI
Page 161 and 162: Chapter 6 ■ Service Transition Co
Page 163 and 164: Chapter 6 ■ Service Transition 10
Page 165 and 166: 6.5 Practice Exercises 1. Which of
Page 167 and 168: Chapter 6 ■ Service Transition 10
Page 169 and 170: Chapter 7 ■ Service Operations I
Page 171 and 172: Chapter 7 ■ Service Operations
Page 173 and 174: Chapter 7 ■ Service Operations Yo
Page 175 and 176: Chapter 7 ■ Service Operations
Page 177 and 178: Chapter 7 ■ Service Operations Th
Page 179 and 180: Chapter 7 ■ Service Operations In
Page 181 and 182: Chapter 7 ■ Service Operations I
Page 187 and 188: Chapter 7 ■ Service Operations 7.
Page 191 and 192: Chapter 7 ■ Service Operations Mo
Page 193 and 194: Chapter 7 ■ Service Operations Th
Page 199 and 200:
Chapter 7 ■ Service Operations 7.
Page 201 and 202:
Page 203 and 204:
Chapter 7 ■ Service Operations
Page 205 and 206:
Chapter 7 ■ Service Operations No
Page 207 and 208:
Chapter 7 ■ Service Operations Th
Page 209 and 210:
Chapter 7 ■ Service Operations It
Page 211 and 212:
Chapter 7 ■ Service Operations at
Page 213 and 214:
Page 215 and 216:
Chapter 7 ■ Service Operations Ga
Page 217 and 218:
Chapter 7 ■ Service Operations Ap
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Chapter 8 ■ Continual Service Imp
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Chapter 9 ■ ITIL Foundation Exam
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Index A Access management and info
Page 257 and 258:
■ INDEX definition, 108 objective
Page 259 and 260:
■ INDEX J JAVA team, 190 K Key
Page 261 and 262:
■ INDEX Service catalog managemen
Page 263:
■ INDEX OR gate, 19 parts, 20 per
show all

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

Create successful ePaper yourself

Delete template?

Save as template?