Context: Uncertainties (Risks, Opportunities)
Risks are unfavorable potential occurrences, i.e., things that could go wrong.
| No. |
Risks |
| 1 |
Project will be found out to be not feasible |
| 2 |
Project participants will not be able to reach consensus |
| 3 |
Any registry may have additional future hardware/software directions given to them by their university or state health department |
| 4 |
Could be a large turnover in the development staff |
| 5 |
Biting off so much might not be able to get it done in a timely manner |
| 6 |
Incentive to continue might not be large enough or clear enough to encourage participation |
| 7 |
Current resources are not enough to support this |
| 8 |
If a registry is happy with their current system they might not be as interested in the short run |
| 9 |
The final solution might not meet the requirements that registries have from other funding sources |
| 10 |
The implemented program might not be used by some registries if it doesn't serve their needs |
| 11 |
Undue power would reside in hands of agency developing and maintaining product |
| 12 |
Central maintenance could become problematic |
Opportunities are favorable potential occurrences or circumstances, i.e., things that could go better than expected.
| No. |
Opportunities |
| 1 |
Components developed could be used beyond SEER |
| 2 |
A standardized system could encourage others to become standardized |
| 3 |
Exchange of registry information could help enhance another registry's operations - tips and ideas, etc. |
| 4 |
Could open more lines of communication between registries |
| 5 |
To create a paradigm ex: enhance expertise in environment, and others |
| 6 |
Could facilitate the dissemination of modules developed locally |
| 7 |
Take advantage of latest changes in technology |
| 8 |
Have good documentation of a system that works |
| 9 |
Participating registries will have some assurance of funding for their DP system |
|