Functions and Processes in Service Transition P1

Transition Planning and Support

Introduction

• The goals for transition planning and support include:

• Planning and coordinating resources in order to ensure that the specifications of the Service Design are realized.

• Starting with the transition phase, identify, manage and limit risks that could interrupt the service.

• The objectivesfor transition planning and support include:

• Plan and coordinate people and means within the frameworks.

• Make sure that everyone applies the same frameworks and standards.

• Report service issues.

• Provide clear and extensive plans.

• Support transition teams and others involved.

• Controlled planning of changes.

• Report issues, risks and other deviations.

• Scope

• The following activities are included in the scope of transition planning:

• Include design specifications and product requirements in the transition plans.

• Manage:

• Plans.

• Supporting activities.

• Transition progress.

• Changes.

• Issues.

• Risks.

• Deviations.

• Processes.

• Scope

• The following activities are included in the scope of transition planning:

• Manage:

• Supporting systems and tools.

• Monitor Service Transition achievements.

• Communicate with clients, users and stakeholders.

• Value for the business

• An integrated approach to planning improves the alignment of transition plans with the customer, service provider, business and change project plans.

• Basic concepts

• The Service Design Package(SDP) contains the following information required by the service transition team:

• Applicable service packages (e.g. core service package, service level package).

• Service specifications.

• Service models.

• Architectural design required to deliver the new of changed service including constraints.

• Definition and design of each release package.

• Detailed design of how the components will be assembled and integrated into a release package.

• Basic concepts

• The Service Design Package(SDP) contains the following information required by the service transition team:

• Release and deployment plans.

• Service acceptance criteria.

• In the release guidelines and policy, the following subjects are addressed:

• Naming conventions, distinguishing release types, such as: major release, minor release and emergency release.

• Roles and responsibilities.

• Release frequency, the expected frequency of each type of release.

• Basic concepts

• In the release guidelines and policy, the following subjects are addressed:

• Approach for accepting and grouping changes in to a release.

• How the configuration baseline for the release is captured and verified against the actual release contents e.g. hardware, software, documentation and knowledge.

• Entry and exit criteria and authority for acceptance of the release into each Service Transition stage and into the controlled test, training, disaster recovery and production environments.

• The criteria authorization for leaving Early Life Support (ELS) and handover to service operations.

Activities, methods and techniques

• The activities for planning and support consist of:

• 1.Set up transition strategy.

• 2.Prepare Service Transition.

• 3.Plan and coordinate Service Transition.

• 4.Support.

• 1.Set up transition strategy

• The transition strategy defines the overall approach to organizing Service Transition and allocating resources.

• Aspects that may be addressed in the transition strategy are:

• Purpose, goals and objectives.

• Context and scope.

• Applicable standards, agreements, legal, regulatory and contractual agreements.

• Organizations and stakeholders involved in the Service Transition.

• Framework for Service Transition.

• 1.Set up transition strategy

• Aspects that may be addressed in the transition strategy are:

• Criteria for success and failure.

• People; roles and responsibilities.

• Approach including transition model, plans for managing changes, assets, configurations and knowledge; transition estimation; preparation; evaluation; error handling; KPIs.

• The products (deliverables) that are the result of the transition activities such as transition plans, schedule milestones, financial requirements.

• 1.Set up transition strategy

• The SDP defines the various phases of the Service Transition. Theses may consist of:

• Acquiring and testing components.

• Testing service release.

• Service Operation ready test.

• Rollout.

• ELS.

• Review and close service transition.

• 2.Prepare Service Transition

• Preparatory activities consist of:

• Review and acceptance of inputs from other Service Lifecycle phases review and check the input deliverables e.g. SDP, Service Acceptance Criteria (SAC) and evaluation report.

• Identifying, raising and scheduling RFCs.

• Checking the configuration baselines are recorded in configuration management before the start of service transition.

• Checking transition readiness.

• 3.Plan and coordinate Service Transition

• A service transition plan describes the tasks and activities required to release and deploy a release into the test environments and into production including:

• Work environment and infrastructure.

• Schedule of milestones.

• Activities and tasks to be performed.

• Staffing, resource requirements, budgets and timescales at each stage.

• Lead times and contingency.

• 3.Plan and coordinate Service Transition

• Good integrated planning and management are essential to deploy a release across distributed environments and locations into production successfully.

• An integrated set of transition plans should be maintained that are linked to lower level plans such as release, build and test plans.

• It is a best practice to manage several releases in a program, with each significant deployment run as a project.

• 3.Plan and coordinate Service Transition

• Implement quality reviews for all Service Transition, release and deployment plans. Questions that might be asked are:

• Are the service transition plans and release plans up-to-date, authorized and are the release dates known?

• Were any risks related to impact on costs, organization and technology taken into account?

• Are new configuration items (Cls) compatible with each other and with configuration items in the target environment?

• Are the people who need to work with it sufficiently trained?

• Have potential changes in the business environment been taken into account?

• 4.Transition process support

• Service Transition advises and supportsall stakeholders.

• The planning and support team provide insight for the stakeholders regarding Service Transition processes and supporting and tools.

• In addition, the team will perform management/administrationof changes, work orders, issues, risks, communication and deployment.

• The team will also update stakeholders regarding planning and process.

• 4.Transition process support

• Finally, Service Transition activities are monitored:

• the implementation of activities is compared with the way they were intended (as formulated in the transition plan and model).

Source by : OGC