#
|
Risk Description
|
Impact
|
Impact Level
|
Likelihood
|
1
|
Requirement Risk
|
1.1
|
- Unclear Requirements: System requirements is not clearly identified, is unclear or is incorrect, leading to continuous change of requirements
|
- Project Schedule is delayed
|
High
|
Medium
|
1.2
|
- Continuous Changes of Requirements: Unforeseen change in requirements due to lack of experience or expectations towards requirements
|
- Project Schedule is delayed
|
Medium
|
High
|
2
|
Design Risk
|
2.1
|
- Technology and Learning: Project involves the use of new technology not used by members of the team prior to project or technology with inherently high level of technical complexity. This risk is extremely exposed to team members who are inexperienced, inadequately trained, or lacking in specialized skills. This leads to steep learning curve and potential personal “shortfalls” by team members, requiring long amount of time to complete tasks
|
- Project Schedule is delayed
|
High
|
Medium
|
2.2
|
- Integration of Project: The lengthened integration of all different levels due to the complexities of the front-back end integration might result in a delay in the schedule
|
- Project Schedule is delayed
|
Low
|
Medium
|
3
|
Scope Risk
|
3.1
|
- Scope Creep: Tendency to add additional functionalities and try to deliver more than agreed which will ultimately cause the team to not be able to meet deadlines
|
- Project schedule is altered and project deadline not met
|
High
|
Low
|
3.2
|
- Fresh Idea for the Industry: The team may not know what is best for the client as the idea is relatively new to the industry. Conversely, the sponsors might not have a clear idea on the deliverables of the project as well
|
- Dissatisfaction with project end-product by client / user
|
Medium
|
Low
|
4
|
Management Risk
|
4.1
|
- Scheduling: Project milestones or schedule not clearly defined
|
- Project schedule created incapable of completing project
|
High
|
Low
|
4.2
|
- Monitor & Management: There is an absence of adequate project management or there is ineffective project managers; the project progress may also not be monitored closely enough. This can be due to project managers being overworked
|
- Project schedule is not monitored and individual deadlines not met
|
High
|
Medium
|
4.3
|
- Communications: Ineffective communications is carried out by team members. This can be due to various barriers of communication.
|
- Redundancies or inefficient work occurs, leading to additional work for the team
|
High
|
Low
|
5
|
Development Risk
|
5.1
|
- Critical Bug: Application may contain a bug that crashes the whole application
|
- Development comes to a halt and project schedule is pushed backwards
|
High
|
Medium
|
5.2
|
- Versioning Software / Platform incompatibilities: Versioning software currently used goes down or encounters problems preventing the retrieval of project source codes. Unforeseen incompatibilities between various software uses may also arise
|
- Development comes to a halt and project schedule is pushed backwards
|
High
|
Low
|