Prioritized Risk List
From DaVinci
Contents |
Top 5 Risks
Highest to lowest priority.
Risk 3
There are missing detailed requirements (e.g., how to trigger one of these transformations); might have down time while additional requirements are elicited or implement in a way unsatisfactory to customer.
Risk 6
We lack experience in the core technologies (e.g., AADL, Ecore, ATL); might not be able to complete all the minimum success criteria because of underestimated learning time.
Risk 1
We don't yet know which refactoring, transformations, and optimizations we will have to implement (we do know one); might fail to complete one or more of them by August 11.
Risk 10
Build, integration, and test environment has not yet been set up; may delay implementation while it is set up.
Risk 17
We don't have regular backup of our project server; could lose our reflections and our "how to" material.
Other Risks
Highest to lowest priority.
Risk 16
The team is geographically distributed; mis-communications might go unnoticed.
Risk 2
We're not sure of the exact implementation techniques for the high-level features we have identified; wasted time, effort underestimated, go down blind alley.
Risk 13
So far our development estimates have been lower than actual; our current longer-term projections may be too low.
Risk 5
There is no way of validating the features for the deliverables of a given sprint prior to delivery; could have to rework a deliverable.
Risk 12
We have not yet agreed upon the developmental model we will use (other than that it will be iterative); might be unable to adequately assess our productivity.
Risk 8
We don't understand how complex the system we are implementing may become; take more time or reduce functionality.
Risk 9
Our team has not yet talked about how to test the final product; might spend a lot of time figuring out how to test it adequately.
Risk 19
Travel budget are dependent on Interdigital upper management; team might not get enough time together or have to spend personal funds.
Risk 4
Eclipse and OSATE are constantly evolving; the plugin code could have to be modified or updated to replace obsoleted API.
Risk 15
Two of our five members work on a different schedule than the other three; we might encounter delayed communications.
Risk 7
ATL and OSATE are still in the experimental phase (still being developed); may be bugs in these that can't be fixed quickly.
Risk 11
We don't have access to intermediate end users; tool might be cumbersome to use.
Risk 14
We don't yet know how we will implement requirements traceability; might start impementing before traceability is defined, causing backtracking.
Risk 18
We have a fixed end date; might have to change scope or drop quality.
Risk 20
20% of MSE studio teams lose a team member; we might lose a member before August.