- ITIL Basics
- ITIL - Home
- ITIL - Overview
- ITIL - Terminologies
- ITIL - Service Basics
- ITIL - Service Lifecycle
- Service Strategy
- ITIL - Service Strategy Overview
- ITIL - Service Strategy Roles
- ITIL - Strategy Generation
- ITIL - Service Portfolio Management
- Business Relationship Management
- ITIL - Demand Management
- ITIL - Financial Management
- Service Design
- ITIL - Service Design Overview
- ITIL - Service Catalogue Management
- ITIL - Service Level Management
- ITIL - Capacity Management
- ITIL - Availability Management
- ITIL - Service Continuity Management
- Information Security Management
- ITIL - Supplier Management
- Service Transition
- ITIL - Service Transition Overview
- ITIL - Project Management
- ITIL - Change Management
- Service Assets and Configuration Management
- Release and Deployment Management
- ITIL - Service and Validation Testing
- Service Operation
- ITIL - Service Operation Overview
- ITIL - Event Management
- ITIL - Incident and Request
- ITIL - Problem Management
- ITIL - Access Management
- Continual Service Improvement
- CSI Overview
- Service Reporting
- ITIL Useful Resources
- ITIL - Quick Guide
- ITIL - Useful Resources
- ITIL - Discussion
ITIL - Project Management
Transition Planning and support (Project management) deals with planning the resources to deploy major release within predicted cost, time and quality estimates.
Project manager is the process owner of this process.
Objectives
The following diagram describes the several objectives of project management process −
The Service Transition Strategy considers several aspects to organize Service Transition and allocating resources −
- Purpose, goals, and objectives of Service Transition
- Framework for Service Transition
- Context, e.g. service customers, contract portfolios
- Criteria
- Organizations and stakeholders involved in transition
- People
- Approach
- Schedule for milestones
- Financial requirements
Planning an individual Service Transition
Service Transition plans describe tasks and activities required to release and deploy a release in to the test environment. It is good practice to deploy Service Transition plan from a proven Service Transition model.
Service Transition Plan also includes −
- Issues and risks to be managed
- Activities and tasks to be performed
- Schedules of milestones, handover and delivery dates
- Staffing, resource requirements, budgets, and timescales at each stage
- Lead times and contingency
Key Points −
It is required to have integrated transition plans that are linked to lower level plans such as release, build and test plans.
It is best practice to manage several releases and deployments as a programme, with each deployment run as a project.
Reviewing the Plans
It is required to verify the plans as and ask following questions before starting release or deployment −
Have the plans been agreed and authorized by all relevant parties, e.g. customers, users, operations and support staff?
Do the plans include the release dates, and deliverables, and refer to related change requests, known errors and problems?
Has the service Design altered significantly such that it is no longer appropriate?
Have potential changes in business circumstances been identified?
Do the people who need to use it understand and have the required skills to use it?
Have the impacts on cost, organizational, technical and commercial aspects been considered?
Have the risk to overall services and operation capability been assessed?
Is the service release within the SDP and scope of what the transition model addresses?