Pre-Deployment Change Readiness & Risk Assessment

Welcome to the Change Readiness & Migration Risk Assessment. This survey takes approximately 13 minutes. Your responses will be kept confidential and reported only in aggregate to inform the go/no-go decision. There are no right or wrong answers—please respond based on current evidence and your best judgment. Participation is voluntary and you may stop at any time. If you are unsure about a question, please choose the closest option or select 'Unknown' where available.

What type of change or migration is this assessment primarily about?

• Infrastructure migration
• Application upgrade or replatform
• Data migration
• Cloud adoption
• Security or compliance change
• Process or tooling change
• Other (please specify)

How clearly defined are the scope and success criteria for this change?

<p>How ready is the <strong>infrastructure/environment</strong> for this change?</p>

<p>How ready is the <strong>application/code</strong> for this change?</p>

<p>How ready is the <strong>data/schema layer</strong> for this change?</p>

<p>How ready are <strong>security and compliance controls</strong> for this change?</p>

<p>How ready is <strong>monitoring and observability</strong> for this change?</p>

<p>How ready is <strong>documentation and runbooks</strong> for this change?</p>

How would you rate the overall level of dependency risk for this change?

If this change were executed within the next 30 days, how would you rate the overall risk?

Please describe the top risks for this change and the conditions most likely to trigger them.

Is a rollback or restore plan currently available and tested?

• Yes, tested end-to-end
• Yes, tested partially
• Draft only
• No
• Unknown

What specific prerequisites must be in place to make a rollback viable?

What is the preferred cutover window for this change?

• Business hours
• After hours (weekday)
• Weekend
• Blue-green or zero-downtime deployment
• Other (please specify)

If downtime is expected, what is the estimated total planned downtime?

• No downtime expected
• 1–15 minutes
• 16–60 minutes
• 1–4 hours
• More than 4 hours
• Unknown

<p>How thorough is <strong>functional testing</strong> coverage for this change?</p>

<p>How thorough is <strong>performance/load testing</strong> coverage for this change?</p>

<p>How thorough is <strong>security testing</strong> coverage for this change?</p>

<p>How thorough is <strong>rollback/recovery testing</strong> coverage for this change?</p>

<p>How thorough is <strong>monitoring and alerting verification</strong> for this change?</p>

Are clear go/no-go criteria defined for this change?

• Yes, documented and agreed upon
• Partially defined
• No
• Unknown

How confident are you that this change can be executed safely and on schedule?

We'd like to explore your perspective on this migration's readiness in a bit more depth. An AI moderator will ask you a couple of follow-up questions based on your earlier responses.

Based on your responses, is there anything else we should consider before the go/no-go decision?

What is your primary role?

• Software engineer
• SRE/Operations
• Security/Compliance
• Data/Analytics
• Product or Project management
• QA/Testing
• Support/Customer success
• Other (please specify)

Which team or function are you representing in this assessment?

• Platform/Infrastructure
• Application team
• Data/ML
• Security
• Networking
• Compliance/Privacy
• Customer-facing operations
• Other (please specify)

How many similar changes have you participated in over the past 2 years?

• None
• 1–2
• 3–5
• 6–10
• 11+

Thank you for completing this assessment. Your responses will be combined with those of other stakeholders to inform the go/no-go decision. If you have urgent concerns not captured here, please contact the project lead directly.