Kynetx Operational Acceptance Checklist

From KynetxDocs

All services promoted to production must meet both general and project specific acceptance criteria. This document sets out the general acceptance criteria and gives guidelines for the project creating specific acceptance criteria.

Contents 1 General Acceptance Criteria 1.1 Testing 1.2 Resources 1.3 Contracts and agreements 1.4 Documentation and training 1.5 Scheduling 2 Project Specific Criteria

General Acceptance Criteria

Testing

1. The production platform, including hardware, software, databases and network connections must be deployed and successfully tested prior to the start of any Operations Acceptance Testing (OAT).
2. All system testing and site testing has been completed and passed without any major deficiencies.
3. All discrepancies between expected results and actual results are identified, prioritized and assigned for resolution.
4. All open issues going into OAT have been identified, assigned a Severity (Class) code that is agreed upon by all impacted organizations, and no Severity 1 issues are open.
5. All process validation test cases have been successfully completed, with no outstanding Severity (Class) 1 issues pending. (See Incident Escalation for more detail on severity levels.) All other lower Class issues will have accepted workarounds identified and agreed to before acceptance of OAT.
6. All Support Plan scenarios have been tested for completeness and alarm resolution directions.

Resources

1. All necessary trouble tracking and knowledge management systems are functional.
2. All e-mail response and phone resources are in place.

Contracts and agreements

1. All applicable vendor contracts including escalation documentation are signed and in place.
2. All maintenance contracts are agreed to and in place.
3. All interface agreements/escalation procedures are agreed upon and in place.

Documentation and training

1. All documentation, including Support Plan(s) and Security Plan(s) is available to appropriate personnel in the agreed to format and presentation method.
2. All related application/service dependencies have been documented and mapped.
3. All related system configuration and architecture diagrams and documentation are in place, and have been authorized via review by the appropriate groups
4. All essential training of personnel including system support Subject Matter Experts (SMEs) has been completed prior to implementation of the product/service, and any additional or supplemental training schedules are agreed to and in place.
5. Any additional training or documentation requirements have been identified and agreed to, and arrangements have been made for their delivery.
6. Product owner contact information is documented and an escalation matrix outlining severities and contact SLAs is created.

Scheduling

1. All release/change dates and times have been communicated to individuals and teams impacted.
2. Change Management has been informed of the pending change/release, and has given Kynetx approval.

Project Specific Criteria

Any major project or product shall develop acceptance criteria that go beyond the general criteria.