Operational Readiness Checklist Template



Operational Readiness ChecklistObjective: to assess or audit the Operational Readiness capability of an organisation.This is a Check-Confirm checklist: run through this when assessing or auditing.StrategyIn organisational strategy, Operational Readiness is as important a goal as customer satisfaction, usability and ROI.Cultural change programmes communicate the importance of Operational ReadinessCustomers understand the importance of operational readinessSystems are not “steamrolled” into production until operationally ready. Executives support delaying.There is a liaison function between Operations, Architecture, Projects and DevelopmentContinual improvement programme(s) includes Operational ReadinessPlanningThe Operations team are involved in all service planningOperational Readiness is a criterion of Service Portfolio decisionsThe PMO supports Operational Readiness and their project templates cover itBusiness cases include Operational Readiness costs and benefitsAchitectureService models include an Operating ModelService models include Non-Functional RequirementsArchitectural standards include Operational ReadinessDesignService added to Service CatalogueService design includes NFRs for availability, data, operations management, continuity, supplier contractsService Design specifies Operational Acceptance Criteria in conjunction with Operations function.Service Design signoff includes a readiness checklistDevelopment (Acquire/Build)Systems are developed to meet requirements for availability/performance, data integrity, operations management, and continuitySolution development (acquisition, integration and/or build) includes operational procedures and documentationOne or more operational staff are involved in developmentDevelopment includes negotiating SLAs with the customers to meet the SLTs of the NFRs…and organisational commitment to the ongoing operational funding and resources to achieve thatDevelopment includes negotiation of supplier contracts that align with and support the SLAsagreed internally that align with and support the SLAsTransitionSLAs are adjusted and renegotiated as necessary to recognise the realities of the new systemInfrastructure is improved as necessary to meet SLAsTesting includes an Operational Acceptance phaseOne or more operational staff are involved in testingOperating model is demarcated and agreed down to procedural levelRoles and accountabilities are assigned and acceptedFunctional and hierarchal escalation paths documented and agreedSupport staff are properly trainedUsers are properly trainedService Catalogue is up to date and accurateCritical service dependencies on IT components are recordedChange implementation plan (Release) approved by all business and IT stakeholdersAcceptanceOperations signoff is required to put a release into ProductionThere are defined deliverables from a release for operability, e.g. support handbookSignoff depends on adequate transfer of knowledgeAcceptance includes the project team operating the system for a warranty periodEvaluationService evaluation includes evaluating that it continues to meet readiness criteria ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download