SR Activity | Risk Factor | Likelihood | Mitigation |
Release planning | Produce the accurate schedule of various phases and baseline results. Release does not work as the customer expects. Due to extended timeline, requirements changes lead to problem in understanding the customer requirements. | 80% | Acceptance criteria linked to requirements assessment. Increase customer involvement throughout use version control tools. |
Designing and building a release | Release design validation against the requirement for the new or changed service offering. Selection of a suitable release mechanism for the change. Prioritize the issues and actions to ensure that they can be resolved in a timely manner test where the release package delivers the change effectively in line with requirements. | 65% | Aligned with change and configuration management. Use of automation tools. Increased stakeholder interaction through involvement or feedback. |
Release acceptance | Release meets the requirements in regard to operability, service and product. | 63% | User acceptance tests aligned with change management. |
Rollout planning | Staff reluctance to adapt changes. Less weight age over the documentation. | 30% | Sign-off documentation for each phase. Software traceability. Use of automation tools. |
Communication, preparation and training | Lack of timely training, poor & inaccurate communication. Change in business processes is not completely tended to by user training bring on unsuccessful execution. | 40% | Provide training prior to implementation. Remove employee reluctance to adapt new system by making them aware of the need of change. |
Distribution and deployment | Timely deployment. | 55% | Ensure the acceptance testing before installation. Recording any incidents, unexpected events, issues or deviations from the plans. Ready the backup plan in case emergency. |