| 01 |
Unfamiliarity with the application area |
When the system analyst is unfamiliar with the application area, there is a chance of misunderstanding the user or even missing the opportunity for improvement. Risk is greater when unfamiliar users are involved |
People |
considering working with analysts and users that are familiar to the field |
| 02 |
Inaccurate estimations |
when the project team underestimates the project requirements and resources |
people |
Including or relying on people who have best understanding on estimations |
| 03 |
Variation of the project scope |
caused from receiving frequent feedbacks from the user so this makes difficulty in sticking to the original timeframe |
Project |
|
| 04 |
project member is absent or leaves unexpectedly |
Team member might fall sick or leaves unexpectedly before the completion of the project |
people |
Assigning the tasks to several people or making the tasks aware to every team member or documenting properly the project so as to not affect the project schedule when something happens |
| 05 |
Poor engagement of the clients or stakeholders |
slow or no responses from the clients or stakeholders can affect the delivery of the project |
People |
making clear agreements with the customer/stakeholders on the response times |
| 06 |
use of new technology |
Using a new technology to implement the project can lead to delays in delivering the system |
Project |
using technology that is familiar to project members or studying the technology in depth for better understanding |
| 07 |
poor productivity of the project team |
project team members can get unproductive or producing poor outcomes and thus affecting the project |
People |
having project manager who will be directly involved and collaborates with the team members |
| 08 |
project size |
having large projects can lead to some requirements not being well understood or overlooked by the project team |
project |
breaking down the projects into separate tasks |