【正文】 ft Active Directory174。 Release Management Service Management Function Published: June 20xx Reformatted: January 20xx For the latest information, please see ii Release Management The information contained in this document represents the current view of Microsoft C orporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a mitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This document is for informational purposes only. MICROSOFT MAKES NO WA RRANTIES, EXPRESS, IMPLIED O R STATUTORY, A S TO THE INFORMATION IN THIS DOCUMENT. C omplying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), but only for the purposes provided in the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the example panies, anizations, products, domain names, e mail addresses, logos, people, places, and events depicted herein are fictitious, and no association with any real pany, anization, product, domain name, address, logo, person, place, or event is intended or should be inferred. ? 20xx Microsoft C orporation. A ll rights reserved. Microsoft, A ctive Directory, PowerPoint, SharePoint, V isio, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual panies and products mentioned herein may be the trademarks of their respective owners. Service Management Function iii Contents Executive Summary ............................................................................................... 1 Introduction ........................................................................................................... 3 What39。s New? This revised look at the Release Management SMF takes into account the feedback and contributions we have received from our partners and clients since the initial publication of this SMF. These include a revised and concise approach to the release planning and building process as well as considerable enhancements in the release preparation and deployment processes to include the rolloutrelated processes. The purpose of these improvements is to simplify the endtoend process of release management as embedded within change management. Feedback Please direct questions or ments about this SMF guide to . 3 Release Management Overview This chapter describes the goal and objectives of the Release Management SMF and defines the key terms used in its processes. Goals and Objectives The goals and objectives of the Release Management SMF are to: ? Plan releases in line with requirements resulting from approved changes. ? Build effective release packages for the deployment of one or many changes into production. ? Test release mechanisms to ensure minimum disruption to the production environment. ? Review preparation for the release to ensure maximum successful deployments. ? Deploy the release in line with structured implementation guidelines. Key Definitions Backout plan. A documented plan detailing how a specific change, or release, can be undone after being applied, if deemed necessary. Change advisory board (CAB). The CAB is a crossfunctional group set up to evaluate change requests for business need, priority, cost/benefit, and potential impacts to other systems or processes. Typically the CAB makes remendations for implementation, further analysis, deferment, or cancellation. Change manager. The role that has overall management responsibility for the change management process in the IT anization. Deployment. The introduction of a release into the IT environment. Release. Within the context of MOF, a release is any change, or group of changes, that must be incorporated into a managed IT environment. These changes are packaged into a single release. Release manager. The role that is responsible for managing the activities of the release management process for the IT anization. For releases with large and plex scopes, the release manager forms a team to manage the release activities. The release manager selects the team members and assigns team roles and responsibilities. Release package. The processes, tools, technologies, and documents required to move a release into production. Also, all of the ponents of the changes that are contained in the release. Request for change (RFC). The formal change request, including a description of the change, ponents affected, business need, cost estimates, risk assessment, resource requirements, and approval status. 4 Processes and Activities This chapter provides a detailed discussion of the processes and activities that occur in the Release Management SMF. Process Flow Summary Release management involves five major processes necessary to successfully plan and deploy authorized releases into an IT infrastructure. The following process flow diagram (Figure 1) identifies the major release management processes. Figure 1. Release management process flow This highlevel overview can be furthe