Risks and Risks/issues are being Risks/issues are being Issues proactively identified, tracked, proactively identified, tracked, updated, and escalated using a updated, and escalated based risk register and a Risk on the project’s Risk Management Plan Management Plan Appropriate team members are All project team members are involved in identifying, encouraged to identify risks and analyzing, and mitigating risks issues and issues throughout the All risks/issues that can be project’s duration handled by the Scrum Team are The project has formally incorporated into the backlog designated the roles of with a user story “risk manager” and owner” “risk The Scrum Master and PM The Risk Management Plan effectively share responsibility includes a framework to actively for maintenance and resolution evaluate risks and specifies the of all risks and issues frequency of regularly scheduled and issues are resolved meetings commensurate with their Appropriate mitigation and/or projected impact to the success contingency plans are of the project established and acted upon on a timely basis Implementation Organizational change Organizational change Readiness management is being effectively management is being effectively planned and executed (by the planned and executed (by the project team and stakeholders) project team and stakeholders) commensurate with the commensurate with the planned schedule for system release dates implementation ORA is iterative and incremental With contributions from the with lessons learned, providing business/program, the project continuous improvement has developed an Operational Knowledge transfer has been Readiness Assessment (ORA) planned and is on schedule for Knowledge transfer has been completion planned and is on schedule for Training, business process completion impacts, and communications
Risks and Issues Risks/issues are being proactively identified, tracked, updated, and escalated using a risk register and a Risk Management Plan Appropriate team members are involved in identifying, analyzing, and mitigating risks and issues throughout the project’s duration The project has formally designated the roles of “risk manager” and “risk owner” The Risk Management Plan includes a framework to actively evaluate risks and specifies the frequency of regularly scheduled meetings Appropriate mitigation and/or contingency plans are established and acted upon on a timely basis Risks/issues are being proactively identified, tracked, updated, and escalated based on the project’s Risk Management Plan All project team members are encouraged to identify risks and issues All risks/issues that can be handled by the Scrum Team are incorporated into the backlog with a user story The Scrum Master and PM effectively share responsibility for maintenance and resolution of all risks and issues and issues are resolved commensurate with their projected impact to the success of the project Implementation Readiness Organizational change management is being effectively planned and executed (by the project team and stakeholders) commensurate with the schedule for system implementation With contributions from the business/program, the project has developed an Operational Readiness Assessment (ORA) Knowledge transfer has been planned and is on schedule for completion Organizational change management is being effectively planned and executed (by the project team and stakeholders) commensurate with the planned release dates ORA is iterative and incremental with lessons learned, providing continuous improvement Knowledge transfer has been planned and is on schedule for completion Training, business process impacts, and communications
SIMM45G_2017-1205.docx