【正文】 ach activity and factoring in resource availability enables the release manager to work out (for the first time) whether the release can be deployed by the required date. If the release is not possible given the available resources, it may be necessary to review other ongoing project mitments and consider changing priorities to facilitate progress on this release. Note that the release manager may need to discuss this with change management to ensure they have a full picture of the business priorities and any other changes that may be dependents or prerequisites of the release. With an agreedon project plan, the release manager can build and document a release strategy describing how to prepare the anization to accept the release, what risks it poses to the production environment, and the manner in which it can be removed from production should it fail to meet its objectives. Deploying any release into the production environment involves risks to the availability and reliability of that environment. All affected personnel need to be aware of the potential risks involved in the deployment. Recognizing this, the release manager should ensure that the appropriate managers agree on and sign off on the release strategy document before the release moves into the design and build phase. 10 Release Management To plete the release planning activities, MOF Team Model role cluster activities may need to be pleted, as described in Table 1. Table 1. Release Planning Activities by Role Cluster Role Cluster Release Planning Activities Infrastructure Provides technical expertise during the release planning activities, including identifying how the new release will interact with the existing systems and infrastructure. Operations Helps with advice and guidance on how the release can be implemented without undermining daytoday operations of the technology. Provides advice on training requirements for operations. Partner Provides input on how to acmodate thirdparty and supplierrelated releases. Also provides advice on how a release may affect an outsourced partner and identifies any actions that may need to be taken. Release Manages and is accountable for the endtoend activities taken throughout release management. Coordinates all other role clusters during planning. Security Provides advice and guidance on security issues related to the planning of a release. Service Offers advice on impact on existing service levels for affected service. Offers planning information from service catalog. Support Helps with expertise on how to ensure a release is fully supportable. Provides advice on training for the service desk and users. May also advise on logistical needs. Scope Release When an approved RFC is passed to release management, the release manager assesses the scope of the change before starting to build the release plan. This task involves looking at the RFC and the information provided by the change initiator, change manager, and others involved in the change process and determining which IT ponents and services need to be changed in order to implement the RFC. To perform this initial assessment, the release manager looks at the target of the release deployment and any associated configuration items (CIs) and services for which he or she may consult the CMDB。 the manager may also refer to information stored in Microsoft Systems Management Server (SMS), Microsoft Active Directory174。 technologies in a data center or other type of enterprise puting environment. This is one of the more than 20 SMFs defined and described in Microsoft Operations Framework (MOF). The guide assumes that the reader is familiar with the intent, background, and fundamental concepts of MOF as well as the Microsoft technologies described. An overview of MOF and its panion, Microsoft Solutions Framework (MSF), is available in the MOF Service Management Function Overview guide. This overview also provides abstracts of each of the service management functions defined within MOF. Detailed information about the concepts and principles of MOF and MSF is also available at What39。 directory service, or other relevant information systems. For example, a memory upgrade is approved for all Microsoft Windows174。s New? ........................................................................................................3 Feedback .............................................................................................................3 Release Management Overview ............................................................................ 5 Goals and Objectives ............................................................................................5 Key Definitions .....................................................................................................5 Processes and Activities ........................................................................................ 7 Process Flow Summary.........................................................................................7 Release Planning ..................................................................................................8 Scope Release ..............................................................................................10 Define and Prioritize Release ........................................................................11 Plan and Schedule Activities .........................................................................12 Determine Release Team Composition and Roles ..........................................13 Identify Training, Logistics, and Communications Requirements ....................13 Document Delivery Strategy for Release .......................................................14 Summary of Release Planning Activities ......................................................