compliance with statutory requirements (e.g. • occupational health and safety, data protection) contractual issues resolved and recorded • 2.3 Have all the stakeholder issues progress reports completed detailing resolution of • been addressed? issues, and circulated as part of the communication plan for stakeholder information 2.4 Are all testing and commissioning/testing team with relevant skills • commissioning/ acceptance (or and experience transition) procedures commissioning/testing plans, results and analyses • complete? of products and/or services against acceptance criteria ratified test reports and logs • confirmed testing, including changed • ‘end-to-end’ or new business processes testing, taking into account future modules or • deliveries there are missing or incomplete items; agreed • corrective action is documented for IT-enabled projects, information assurance • tests 2.5 Have all parties accepted the evidence of acceptance of procedures and • commissioning/test results and results by supplier and agency any required action plans? 2.6 Are there workable and tested a fully documented approach with timetables, for • contingency and back-out plans key aspects and events, for example, IT components for roll-out, implementation and decisions about roll-out and operation? decision-makers should be informed and clearly • identified in the documentation roles and responsibilities listed; resources allocated • and staff trained commissioning/testing represented the expected • scenario(s) plans for the transition to new ways of working, • where applicable for handover to facilities management, where • applicable training and relevant supporting material, if • required 2.7 Have the supplier and all all required plans in the contract • internal and external parties all parties, or their representatives, are aware of • agreed on the implementation their responsibilities and have agreed to them plans? These could include: management of change • migration and data transfer •
• compliance with statutory requirements (e.g. occupational health and safety, data protection) • contractual issues resolved and recorded 2.3 Have all the stakeholder issues been addressed? • progress reports completed detailing resolution of issues, and circulated as part of the communication plan for stakeholder information 2.4 Are all testing and commissioning/ acceptance (or transition) procedures complete? • commissioning/testing team with relevant skills and experience • commissioning/testing plans, results and analyses of products and/or services against acceptance criteria • ratified test reports and logs • confirmed ‘end-to-end’ testing, including changed or new business processes • testing, taking into account future modules or deliveries • there are missing or incomplete items; agreed corrective action is documented • for IT-enabled projects, information assurance tests 2.5 Have all parties accepted the commissioning/test results and any required action plans? • evidence of acceptance of procedures and results by supplier and agency 2.6 Are there workable and tested contingency and back-out plans for roll-out, implementation and operation? • a fully documented approach with timetables, for key aspects and events, for example, IT components and decisions about roll-out • decision-makers should be informed and clearly identified in the documentation • roles and responsibilities listed; resources allocated and staff trained • commissioning/testing represented the expected scenario(s) • plans for the transition to new ways of working, where applicable • for handover to facilities management, where applicable • training and relevant supporting material, if required 2.7 Have the supplier and all internal and external parties agreed on the implementation plans? These could include: • management of change • migration and data transfer • all required plans in the contract • all parties, or their representatives, are aware of their responsibilities and have agreed to them
A_Handbook_for_Conducting_Assurance_Reviews_FMR_7.docx