University of Edinburgh

_______________________________________________________________________________________________________

Stage: Acceptance Deployment Checklist

[PROJECT NAME]
[PROGRAMME NAME] [PROJECT CODE] [ANNUAL PLAN NUMBER]

Document Version: [x.x] Date: [dd/mm/yy]

___________________________________________________________________________________ Information Services - Template Revised May 2009

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

Contents
1 DOCUMENT MANAGEMENT........................................................................3 1.1 Contributors...........................................................................................................3 1.2 Version Control......................................................................................................3 2 DEPLOYMENT...............................................................................................4 2.1 Deployment Strategy..............................................................................................4 2.2 Dependencies..........................................................................................................4 2.3 Communication......................................................................................................4 2.4 Technical Issues......................................................................................................4 2.5 Deployment Checklist............................................................................................5 2.5.1 Application Checklist........................................................................................5 2.5.2 Infrastructure Checklist.....................................................................................7 2.5.3 Support Checklist..............................................................................................9 3 TRAINING.....................................................................................................12 3.1 Delivery.................................................................................................................12 3.2 Training Materials...............................................................................................12

___________________________________________________________________________________ Page 2 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

1 Document Management
When completing this document, please mark any section that is not required as N/A. A brief description of why the section is not required should also be included.

1.1 Contributors
Please provide details of all contributors to this document. Role Production Management Coordinator (Owner) Project Manager Business Analyst Systems Analyst Designer Technical Architect Business Area Manager Other document contributors Unit Name

1.2 Version Control

Please document all changes made to this document since initial distribution. Date Version Author Section Amendment

___________________________________________________________________________________ Page 3 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

2 DEPLOYMENT
The deployment of a new system or enhancement to an existing one is a significant milestone in the delivery of the project. It is critical however that the deployment is achieved successfully with minimal disruption to current production services. To try to ensure this it is essential that adequate preparation take place. This Deployment Checklist highlights the key elements that need to be in place before the project deliverables can be accepted for deployment via the Acceptance Sign Off Review.

2.1 Deployment Strategy

Please include details of the deployment strategy, which could include the following: Proposed deployment date The user groups involved, with reasoning for selection Staged rollouts how is the system to be released to the user community Assessment of risk to existing services and measures to mitigate these Timeframes and checkpoints Use of project plans etc Post deployment actions

2.2 Dependencies
Please identify any dependencies that could impact the deployment strategy.

2.3 Communication
Please detail how the deployment will be communicated, both to participants and to the wider community staff and students where applicable. The groups that need communicated too should be identified as part of the Deployment Strategy and the necessary communications directed to them through the options below. Service Announcement(s) [mandatory] MyEd Announcement(s) Other Business Area communication

If the system has an impact on other applications, specific communication should be made to the affected Service Owners to highlight the level of disruption and timeframes.

2.4 Technical Issues

Please revisit the Implementation Plan and note any additional issues for deployment that may need to be addresses before sign-off is possible.

___________________________________________________________________________________ Page 4 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

2.5 Deployment Checklist

Please use this checklist to ensure that required actions have been complete. Please provide links to any relevant documentation.

2.5.1 Application Checklist

Area Implementation Plan Description Feedback from previous test implementations completed and successful full implementation undertaken for UAT Ensure SSD completed and accurate. Action: The SSD must be copied to the Wiki Appropriate documentation has been produced for use by staff providing technical support for the new application. Adequate load testing has taken place and results recorded. The application has been tested against stated performance criteria. Performance has been assured by user and support staff testing. Source code has been secured with VSS or other SCM Mandatory [Y/N] Y Reviewed (Date/Pers on) Actions (What/Who)

System Support Document(SSD)

Technical Documentation

Scalability/Load Testing Performance

N Y

Source Code Source control must be checked out till go-live and checked-in after go live Configuration Management Database

The relevant details regarding new or changed infrastructure components have been added to the configuration management database ( Change Control System) A change control entry has been created for the LIVE implementation. The person who reviews this Deployment Checklist will approve the change control request.

Change Control

___________________________________________________________________________________ Page 5 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

Area Test Log Review

Description A review of the test log has taken place to ensure all required actions have been completed. If this is not the case, then confirmation on criticality of outstanding issues and action plan for resolution is required. Handover to Production Management is completed and the team are in are in position to support the application post deployment. A risk assessment has been undertaken for the Implementation Plan and selected deployment dates. (e.g. roll back) Setup Read access accounts or update current read access accounts (May requires business owner approval) InfoKeep has been updated with all relevant account details including external supplier accounts Database comparison between TEST and LIVE (might be required before and after go-live) Does the application have specific client requirements, such as JVM/JRE versions, JInitiator? If so have these requirements been raised with Desktop services Wiki pages to be updated: [1] https://www.wiki.ed.ac.uk/display/ insite/Corporate+applications+wit h+client+based+requirements [2] https://www.wiki.ed.ac.uk/display/ insite/Client+side+Java+requirem ents+for+corporate+applications Is there any new software or technologies involved?

Mandatory [Y/N] Y

Reviewed (Date/Pers on)

Actions (What/Who)

Production Management Handover

Implementation Risk Assessment

Accounts

InfoKeep

Environment comparison Client requirements

N Y

Technologies

___________________________________________________________________________________ Page 6 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

Area Access outside University

Description By default all web based applications are accessible outside University: Wiki list If not accessible from outside University this needs to be approved by Production Management managers.

Mandatory [Y/N] Y

Reviewed (Date/Pers on)

Actions (What/Who)

2.5.2 Infrastructure Checklist

Area Technical Architecture Document(TAD) Description Documentation complete and accurately reflects the environment subjected to UAT. Action: TAD needs to be copied to Wiki Security All security requirements, e.g. SSL encryption, IP based restrictions firewall requirements have been specified, tested and implemented in LIVE All changes to certificates or new certificates for this service have to be added to the certificate master list. The certificate master list is being managed by Applications Management This includes TEST and LIVE certificates and records type of certificate and expiry dates. Ensure any new or amended infrastructure is included in regular patching. Different technologies may follow different patching strategies and ensure the new infrastructure is added to any existing processes and documents Oracle, Windows, Linux Details of any new hardware acquired as part of the project have been recorded in the Asset Register Y Mandatory [Y/N] Y Reviewed (Date/Pers on) Actions (What/Who)

Certificates

Patching

Asset Register

___________________________________________________________________________________ Page 7 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

Area Infrastructure diagrams

Description All infrastructure diagrams are updated with newest server and infrastructure details https://www.wiki.ed.ac.uk/display/ insite/Server+Layout+%28Unix %29 and https://www.wiki.ed.ac.uk/display/ insite/Server+Layout+ %28Windows%29 Are Server Startup/Shutdown scripts in place? Including startup procedure documented Has port allocation file been updated? https://www.wiki.ed.ac.uk/display/ insite/Port+Allocation+on+Unix+S ervers

Mandatory [Y/N] Y

Reviewed (Date/Pers on)

Actions (What/Who)

Start/Stop scripts

Ports

___________________________________________________________________________________ Page 8 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

2.5.3 Support Checklist

Area Support Agreement (including any charging arrangements) Description A support agreement is in place for any new applications including any hosting or support charges. Action: SLA moved to wiki: https://www.wiki.ed.ac.uk/display/ insite/SLA+repository++Applications+Management System Description Document Documentation complete and reviewed by support group Action: SDD needs to be copied to Wiki Time Recording Code Backup and Recovery A Time Recording code for the application, if required, has been confirmed and set up. All backups as noted in the TAD need to be confirmed operational. A test recovery of user data needs to be done to validate the integrity of the recovery mechanism and process. Appropriate DR/BC provision is in place and has been fully tested. Application DR/BC details have been transferred to the DR Portfolio and DR level (1, 2 or 3) has been agreed An adequate test environment has been established for the application which may be used by support to test future changes prior to implanting these in the live environment. All required licensing is in place including maintenance/support arrangements with external suppliers. Y Y Mandatory [Y/N] Y Reviewed (Date/Pers on) Actions (What/Who)

Disaster Recovery and Business Continuity

Test Environment

Hardware and Software Licensing

___________________________________________________________________________________ Page 9 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

Area Browser Compatibility

Description Browser compatibility has been tested and compatibility information updated See http://www.ed.ac.uk/schoolsdepartments/informationservices/services/computing/appli cation-development/applicationsupport/supported-webbrowsers/browser-application for details Portal compatibility, where required, has been confirmed the Portals Service Owner. The new application is recognised with the UniDesk (A business contact queue is defined where initial calls are raised with) Review of the PICCL has taken place to ensure that there are no outstanding issues that would affect deployment Appropriate documentation has been produced for users of the new application. Training material, if required, has been produced and is of an appropriate standard. Demonstration or walkthrough of the new application has taken place for other stakeholder. Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review. IS and business area resources required for deployment, including those needed for post implementation checking and sign off have been secured. Please state who (single person) manages the go-live, including:comms with service owner, ensuring go live timescales are met, managing issues araising and managing comms between teams involved in golive.

Mandatory [Y/N] Y

Reviewed (Date/Pers on)

Actions (What/Who)

Portal Compatibility Help Desk

PICCL Review

User Guide Documentation Training Material

Demonstration or Walkthrough Deployment Date

Deployment Resources

Deployment Ownership

___________________________________________________________________________________ Page 10 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

Area Service Announcement

Description A Service announcement has been raised with the agreed deployment date on the alert system: http://reports.is.ed.ac.uk/alerts/ Service announcements should be raised by Project Manager 10 days before go live, but no later than 4 days.

Mandatory [Y/N] Y

Reviewed (Date/Pers on)

Actions (What/Who)

Web Sites and Other Document Sources Deployment Resources

External and internal web site have been reviewed to ensure that all application references are present, correct and up to date. Setup Read access accounts or update current read access accounts (requires business owner approval)

___________________________________________________________________________________ Page 11 of 12

Acceptance: Deployment Plan [Version: x.x]

[Project Name]

_______________________________________________________________________________________________________

3 TRAINING 3.1 Delivery

Please detail how the training will be delivered, including the following: Type Classroom, Self Trained, On-Line etc Identification of Trainer (if required) Location of training

3.2 Training Materials

Please provide details of any training materials that will be required. E.g. User Guides, Training Booklet etc

___________________________________________________________________________________ Page 12 of 12