Release and Deployment Plan
ISO/IEC 20000 Toolkit Version 7 ©CertiKit
Release and Deployment Plan
Implementation Guidance (The header page and this section must be removed from final version of the document)
Purpose of this document This document describes the deployment plan for a specific release.
Areas of the standard addressed The following areas of the ISO/IEC 20000:2011 standard are addressed by this document: 9. Control processes 9.3 Release and deployment management
General Guidance Each deployment will be different and it’s important that adequate planning is carried out in accordance with the ISO/IEC 20000 standard. You may only want to carry out this level of planning for larger, more critical releases which are likely to have been planned through the Design and Transition of New or Changed Services process; the degree of control should match the level of risk to the organisation. Evidence of testing activities including system, regression and user acceptance testing should be kept and be available for review during the certification audit.
Review Frequency We would recommend that this document is reviewed annually.
Toolkit Version Number ISO/IEC 20000 Toolkit Version 7 ©CertiKit.
Copyright notice Except for any third party works included in this document, as identified in this document, this document has been authored by CertiKit, and is © copyright CertiKit except as stated below. CertiKit is a trading name of Public I.T. Limited, a company registered in England and Wales with company number 6432088 and registered office at 5 Falcons Rise,
Version 1
Page 1 of 10
[Insert date]
Release and Deployment Plan
Belper, Derbyshire, DE56 0QN.
Licence terms This document is licensed on and subject to the standard licence terms of CertiKit, available on request, or by download from our website. All other rights are reserved. Unless you have purchased this product you only have an evaluation licence. If this product was purchased, a full licence is granted to the person identified as the licensee in the relevant purchase order. The standard licence terms include special terms relating to any third party copyright included in this document.
Disclaimer Please Note: Your use of and reliance on this document template is at your sole risk. Document templates are intended to be used as a starting point only from which you will create your own document and to which you will apply all reasonable quality checks before use. Therefore please note that it is your responsibility to ensure that the content of any document you create that is based on our templates is correct and appropriate for your needs and complies with relevant laws in your country. You should take all reasonable and proper legal and other professional advice before using this document. CertiKit makes no claims, promises, or guarantees about the accuracy, completeness, or adequacy of our document templates, assumes no duty of care to any person with respect its document templates or their contents, and expressly excludes and disclaims liability for any cost, expense, loss or damage suffered or incurred in reliance on our document templates, or in expectation of our document templates meeting your needs, including (without limitation) as a result of misstatements, errors and omissions in their contents.
Version 1
Page 2 of 10
[Insert date]
Release and Deployment Plan
[Replace with your logo]
Release and Deployment Plan for [Change Request Number] – [Name of Release]
Document Ref. Version: Dated: Document Author: Document Owner:
Version 1
Page 3 of 10
SMS-DOC-093-3 1 [Insert date]
[Insert date]
Release and Deployment Plan
Revision History Version Date
Revision Author
Summary of Changes
Distribution Name
Title
Approval Name
Version 1
Position
Signature
Page 4 of 10
Date
[Insert date]
Release and Deployment Plan
Contents 1
INTRODUCTION ....................................................................................................................................... 6
2
RELEASE AND DEPLOYMENT PLAN ................................................................................................. 7 2.1 APPROACH ................................................................................................................................................ 7 2.2 METHOD OF DEPLOYMENT ........................................................................................................................ 7 2.3 PREREQUISITES ......................................................................................................................................... 7 2.3.1 Hardware ........................................................................................................................................ 7 2.3.2 Software .......................................................................................................................................... 7 2.3.3 Licensing ......................................................................................................................................... 7 2.3.4 Other ............................................................................................................................................... 7 2.4 CONFIGURATION ITEMS ............................................................................................................................ 8 2.5 TRAINING .................................................................................................................................................. 8 2.6 ROLES AND RESPONSIBILITIES .................................................................................................................. 8 2.7 CHANGE MANAGEMENT ........................................................................................................................... 9 2.7.1 Back-out Plan ................................................................................................................................. 9 2.7.2 Testing ............................................................................................................................................ 9 2.7.3 Communication ............................................................................................................................... 9 2.8 TIMING AND TIMESCALES ......................................................................................................................... 9 2.8.1 Outline Project Plan ....................................................................................................................... 9 2.9 RISK MANAGEMENT ............................................................................................................................... 10 2.10 DOCUMENTATION .............................................................................................................................. 10 2.11 RELATED CHANGE REQUESTS, KNOWN ERRORS AND PROBLEMS ...................................................... 10
List of Tables TABLE 1 - AFFECTED CONFIGURATION ITEMS ............................................................................................................ 8 TABLE 2 - TRAINING ACTIVITIES ................................................................................................................................. 8 TABLE 3 - ROLES AND RESPONSIBILITIES .................................................................................................................... 9 TABLE 4 - OUTLINE PROJECT PLAN ............................................................................................................................ 9 TABLE 5 – DOCUMENTATION................................................................................................................................... 10 TABLE 6 - RELATED CHANGE REQUESTS, KNOWN ERRORS AND PROBLEMS ................................................................. 10
Version 1
Page 5 of 10
[Insert date]
Release and Deployment Plan
1 Introduction The purpose of creating a release and deployment plan is to ensure that the transition of a new or changed service into the live environment is carried out effectively and the risk to the business is minimised. This plan is relevant to one or more change requests that have been approved by the Change Advisory Board and should be attached to these changes within the change management system. [Summarise the background to the release and deployment plan including why it has come about and what the organisation may gain from it] The following documents are related to this release and deployment plan and should be consulted to obtain the full background to the change: • • • •
Business case Service requirements specification Service design specification Service acceptance checklist
[Reference the specific documents that are related to this plan and the change it is implementing].
Version 1
Page 6 of 10
[Insert date]
Release and Deployment Plan
2 Release and Deployment Plan 2.1
Approach
The approach that will be taken to the release and deployment of the change is as follows. [Describe the approach to be taken – is it a phased rollout or big bang? Which areas, business units or technology will it be deployed to first? Who will be involved? Will it be done in-house or via a third party etc.] 2.2
Method of Deployment
[What methods and tools will be used in the deployment e.g. software distribution tools, physical installation onsite, user install etc.] 2.3
Prerequisites
The following items must be in place before the deployment is started. 2.3.1
Hardware
[Specify minimum hardware configurations, servers that must be in place, network requirements etc.] 2.3.2
Software
[Specify minimum software version levels and components, any dependencies between versions etc.] 2.3.3
Licensing
[Explain any licensing implications – have all of the required licenses been purchased?] 2.3.4
Other
[Anything else that has to be in place before the deployment can be started.]
Version 1
Page 7 of 10
[Insert date]
Release and Deployment Plan
2.4
Configuration Items
The following configuration items will be affected by the deployment: Configuration Item
Current version
New version
Comments
Table 1 - Affected configuration items
[Include new configuration items that will be introduced and any that will be updated as part of the deployment] CMDB records will be updated as part of the configuration management process. 2.5
Training
The following training activities will take place as part of the deployment: Training activity
Recipient
Scheduled dates
Table 2 - Training activities
2.6
Roles and Responsibilities
The people that will be involved in the deployment and their responsibilities are shown in the table below. Name John Smith
Role Deployment Manager
Responsibilities Plan the deployment Liaison with users
Jane Jackson
Trainer
Steve Miller
Deployment team member
Create courses Deliver courses Pre-installation survey
Version 1
Page 8 of 10
[Insert date]
Release and Deployment Plan
Andy Baird Karen Ziller Geoff Clayton
Deployment team member Deployment team member Deployment team member
Software installation Post-installation testing
Table 3 - Roles and responsibilities
2.7
Change Management
2.7.1
Back-out Plan
[Describe how the deployment will be reversed in the event that something goes wrong.] 2.7.2
Testing
[Specify the testing that has been carried out so far and the testing that will be done once the release has been deployed to confirm its correct operation] 2.7.3
Communication
[Describe what will be communicated to whom and when as part of the deployment. This may involve the service desk, top management, customers, users and third parties] 2.8
Timing and Timescales
[Set out when the deployment will take place (date and time) – how long will it take and (if appropriate) when will service be resumed to users?] [If the deployment is lengthy outline the proposed timescale in a project plan] 2.8.1
Step
Outline Project Plan
Task 1
2
Day/Week/Month 3 4 5 6
7
1. 2. 3. 4. 5. Table 4 - Outline project plan
Version 1
Page 9 of 10
[Insert date]
8
Release and Deployment Plan
2.9
Risk Management
[List any risks associated with the deployment and how they will be addressed prior to it starting]
2.10 Documentation The following documentation will be available as part of the deployment: Document Name Release Notes User Guide Admin Guide
Description
Version
Table 5 – Documentation
2.11 Related Change Requests, Known Errors and Problems The following change requests, known errors and problems will be closed through this release: Ref. CHG2321 CHG4353 PRB00243
Type Change Change Known Error
Description Amendment to purchasing screen Bug fix in logistics module Desktop client crashes
Table 6 - Related change requests, known errors and problems
Version 1
Page 10 of 10
[Insert date]