Deployment Readiness Assessment Template
Deployment Readiness Assessment Template
[Customer Name]
Risk Explanation
Unacceptable [Explanation of this risk decision]
High [Explanation of this risk decision]
Medium [Explanation of this risk decision]
Low [Explanation of this risk decision]
None [Explanation of this risk decision]
Testing
Task Owner Status
Is there a Promotion Candidate Snapshot (PCS)?
Has the PCS been Regression tested in QA?
Has the PCS been Performance tested in QA?
Has the PCS been Acceptance tested in QA?
Are all known issues with the solution documented?
Deployment
Task Owner Status
Is the PCS stored in a retrievable location for later
recreation in another environment (break-fix)?
Are there any environmentally sensitive EPVs in the PCS
that need to be changed once the promotion/import is
finished?
Are there step by step instructions on how to deploy File
Based Assets (FBA) not included in the snapshot?
Is there a known production level white-glove test to
confirm the deployment of each individual asset?
Are all environmentally sensitive files (property files)
scripted for automation and documented?
Are all server level customizations (OS settings, App
Page 1 of 3
IBM Risk Assessment
[Customer Name]
BPM Program
Task Owner Status
Impact to other production processes in the same
shared library identified and stakeholders notified
Check for program-level shared assets (e.g. shared
services/connectors) that are being upgraded as part of
the new deployment.
Application
Task Owner Status
Health Inspection checklist complete
Complete Playback 3 and any last minute "must have"
changes
Run book complete
Document procedures for file based assets (not included
in export)
Risk and Issue logs reviewed
Deployment environment prepared (hardware, security,
database etc)
Document production EPV values
Identify the impact to other production processes in the
same shared library
Page 2 of 3
IBM Risk Assessment
[Customer Name]
IT/Support/Technology Considerations
Task Owner Status
Identify and confirm training for Tier I & II post-
deployment support resources
Identify and allocate the resources from the Core team
(Tier III) to support the stabilization period (first 1 - 2
weeks)
Maintenance window reserved for migration
Contact list and communications plan for deployment
window complete
Change control ticket for migration submitted
Migration script/timeline completed and rehearsed
Establish go/no go criteria for deployment
Backout plan created
Support organization briefed on application
Page 3 of 3