| Changing customer requirements. |
Customer changes his requirements endangering the project's end date, or the project is carried out not comply with the customer. |
1 |
3 |
Increase cooperation and coordination with customer expectations. In addition, the development team will work flexibly so that any changes to the customer will be easy to carry out. |
Changing the program according to the new requirements, rewriting of some parts. |
| Team turnover |
Central personality can leave the project which may be a significant risk project’s ending time. |
2 |
2 |
Share information with crew. |
Redistribution of roles in the group. |
| Wrong estimation of system's size. |
The system is more complex and bigger than we thought initially. |
1 |
3 |
Requirements document, detailed design. |
Reducing customer requirements. |
| Development tools do not meet expectations. |
System that should help develop not fulfill all our expectations of them. For examples: Firebase. |
1 |
3 |
Depth overview about the development tools. |
Setting alternative development tools. |
| Standing the test of time. |
It will cause a delay in the project completion date. |
1 |
2 |
Prioritizing the customer requirements. Appoint one team member whose job was to analyze the progress. |
Reducing customer requirements. |
| Team is unfamiliar with development tools. |
Lack of familiarity with Firebase and with Angular programming language, may cause a delay at the end of the project. |
1 |
1 |
Selecting a variety team. |
Division to a few teams, where each team member knows to perform the work and is aware to tools he is going to use them. Cooperative learning. |