【正文】 stood releases, a release plan should contain all of the tasks and activities required to deploy the release into the production environment. For large and plex releases, however, the release plan may contain a number of tasks that simply indicate the duration and owner of a particular phase or stage, with the owner responsible for creating and resourcing a rollout plan to deliver that part of the release. If a release is to be deployed in Seattle, Cambridge, and Edinburgh, for example, the release plan may contain all of the tasks and activities required to roll out the release in Seattle, but not Edinburgh or Cambridge. The release manager may decide to delegate the task of planning and deploying the release in these two locations to locally based support staff as separate stages, since they have a detailed knowledge of the environment and can thus plan accordingly. Note that although the release manager may delegate responsibility for a part of the release to others, the release manager is still responsible for delivering the entire release, through all stages or phases, into production. In this respect, the release manager needs to agree on and then monitor the progress of all plans connected with the delivery of that release. The size and plexity of the release drives the selection of tools used to create and maintain the project plan. In planning a large and plex release, the release manager probably needs to use project management tools such as Microsoft Project, but this may not be necessary for smaller releases where a spreadsheet or simple document may be sufficient. Once the release plan is plete, the release manager may need to discuss it with the change manager and change advisory board, if appropriate, before selecting and assigning resources to specific tasks and activities. The necessity for this review depends on the size and plexity of the release, the number of resources required to implement it, and the perceived risks to the production environment. The release plan should be saved against the release reference number, and the change log for each RFC in the release should be updated to indicate that the release plan is now plete. Microsoft Project is an ideal tool for planning medium to large releases since it provides the release manager with an accurate picture of resource requirements and utilization. Its use may be inappropriate for small releases. Service Management Function 13 Determine Release Team Composition and Roles For small releases, the release manager may be the only individual required to deploy them into production. For more plex releases, the release manager may need to assemble a release team to carry out certain tasks and activities of the release plan, or the release manager may appoint phase, or rollout, managers to manage a specific part of the release process. A test manager may be appointed, for example, to manage the release during testing. If additional resources are required, the release manager identifies and selects individuals with the appropriate levels of skill and experience. In some cases, it may be necessary to obtain resources from thirdparty panies if internal resources are not available or do not have the required level of expertise. Note that release team members not under the direct control of the release manager may be s。 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 Wha