Top Risks
| Ranking this week | Risk | Mitigation |
| 1 | wmi install will take too long try to get benchmark items w/o wmi | develop alternate vbs not requiring wmi. |
| 2 | offline tools don't work as needed or expected | prioritize work on this. make sure we can collect feedback thoroughly from new users |
| 3 | online tools dont work as expected or as needed by eriders | get input asap re user needs, add content to easy user experience |
| 4 | unexpected differences in OS environments & language environments | get help from int'l testers. |
| 5 | insufficient testing time | get volunteer help |
| 6 | upload synchronization not sufficient | could revisit after launch |
| 7 | online usage doesn't parallel offline usage leading to cognitive disconnect | try to role more improvements int TS online development, know what features we should try to ammend |
| 8 | hurdle for localization too high | identify needed resources to localize, maybe to support efforts of others |
| 9 | quirky installation of offline tools | do best to make easy |
| 10 | Short development cycle | be ready to drop last minor features on short notice |
| still remain issues, but not actively being addressed now. | Insufficient knowledge of and input from eRider community prior to commencement of development |
I'd like to invite eriders to view/review/test application as soon as we have a stable install. getting as much as we can now. Building tools to allow flexibility later delivery and future changes to content. |
| Diversity of eRider community, especially across languages and cultures, is extreme. | Involve diverse eriders. Build with future language translations in mind. | |
| Highly diverse technical environments & operating system attributes & versions across regions. | We'll need a diverse testing environment during dev as well as during beta periods to address this. |
| Ranking this week | Ranking (7/14) | Risk | Mitigation |
| 1 | 1 | ||
| 2 | 2 | ||
| 3 | 7 | ||
| 4 | 3 | Short development cycle | scope features carefully, monitor priorities and progress closely |
| 5 | 4 | Developer is building offline tools for 1st time in this platform (VB) | Address problem areas/potential bottlenecks early in development. |
| 6 | 5 | Developer lacks 1st hand familiarity with end users. | Ric & Bill & eRiders are tapped fully. Phil will communicate re: development issues with developer eriders. |
| 7 | 6 | Project management complicated by multiple stakeholders/ project owners. | Setting clear project role lines, use project mgr to keep things on track. |
| 8 | |||
| 9 | |||
| 10 |