Developing and Implementing a Rollout Plan制定并实施推广计划.pptVIP

Developing and Implementing a Rollout Plan February 5, 2007 2:00pm EST, 11:00am PST George Spafford, Principal Consultant Pepperweed Consulting, LLC “Optimizing The Business Value of IT” Housekeeping Submitting questions to speaker Submit question at any time by using the “Ask a question” section located on lower left-hand side of your console. Questions about presentation content will be answered during 10 minute QA session at end of webcast. Technical difficulties? Click on “Help” button Use “Ask a question” interface Main Presentation Agenda Release Management Overview Release Plans Rollout Plans What they are Elements of Rollout Plans Getting Started Note: This presentation is available by either emailing: George at George.Spafford@P Kendra at webcasts@ What Is a Release? A collection of authorized changes to an IT service New services Modifications to an existing service Ending a service – sometimes decommissioning takes a lot of work and needs to be properly managed Can contain new and revised hardware and software in three categories – Major, Minor and Emergency Release Unit – describes the IT infrastructure portion that is released together Hardware, Software, Documentation, Media, etc. Type of Release Full, Delta, Package Why Release Management Matters 29% of projects delivered on-time with expected features, 53% were challenged and 18% outright failed outright1 The majority of the causal factors are non-technical including: Lack of project planning Poor requirements definition Correct stakeholders not involved, or not involved early enough Poor communications Insufficient management oversight “The focus of Release Management is the protection of the live environment and its services through the use of formal procedures and checks.” – ITIL Service Support Volume Release Management Provides Quality Assurance Are the correct requirements identified? Breadth and depth Are the requirements met when tested? What testing is needed? Unit, Integration,