Category:Release and Deployment Management

From IT frameworks

Jump to: navigation, search

The ITIL Map

Define a vision for your IT organisation that is aligned with the Business.Control your IT expenses!Ensure correct handling of future expectations and requirements.Provide assurance of IT services.Ensure agreement with your customer on services.Guarantee an up to date service menu.Ensure the correct capacity of your services.Ensure the correct avalability of your services.Plan for the unexpected.Ensure appropriate security for your services.Control who delivers to us.Reply to user requests in a service minded manner.Solve the unexpected in the daily operations!Detect and sort activities in your IT infrastructure.Ensure correct access to your services.Fix the unexpected in the daily operations.Reduce mistakes effecting Business.Control the changes to the IT infrastructure.Predicted performance vs. Actual performance.Change services without unexpected downtime.Assure that your service does what is intended.Keep the knowledge in your company!Keep track of how your services are interconnected.Know how to measure your services.Ensure correct analysis of your services.Standstill = Decline!Friendly and helpful single point of contact for your users.Contract between you and your customers.
About this image

A key process in the Service Transition life cycle phase.

Example of Research & Development, Validation & Testing flow chart
Example of Research & Development, Validation & Testing flow chart


Contents

Goals & Objectives

The main goals of release and deployment are to move services into production while meeting customer requirements.

Release plans, release packages and knowledge transfer must be in place.

Terminology

  • ELS - Early Life Support. ITIL recommends moving Release & deployment staff into Service Desk Function for early life support.
  • Release - New or changed CIs moving to Service Operations (live)
  • Release unit - Part of a service to be released
  • Release package - One or more structured release units
  • Big Bang v Phased - All users at once or gradual release to sets of users
  • Push v Pull - Release is pushed onto users or users must pull (download) the release
  • Automated v manual - Many releases can be automatic, especially documentation
  • V model - A model to dvisualize SAC and testing leveld before building

Roles

Scope

Activities

  • Planning
  • Preparation for building, release & deployment
  • Building & testing
  • Service testing & pilots
  • planning & preparing deployment
  • transfer, deployment and retirementverfiy deployment
  • ELS
  • Review and close

Interfaces

Inputs/Outputs

Inputs

Outputs

  • Release & deployment plans
  • Transfer, deployment, retirement of services
  • ELS

Value to the Business

  • Optimal release and deployment means lower costs for business with a faster release yet fewer risks
  • SAC over deployment carried out professionally

Implementation

Challenges to implementation

Tips for exam

References and resources

Service Transition, OGC

Articles in category "Release and Deployment Management"

There are 2 articles in this category.

R

Retrieved from "http://www.itframeworks.org/wiki/Category:Release_and_Deployment_Management"
Personal tools