The following is a draft of risks identified by the VR team and the Product Committee members. The purpose is to have a collective understanding of the risks associated with the re-architecture and future of OpenLMIS. Subsequently we can collectively put in place strategies to mitigate the identified risks.
ID | Severity | Likelihood | Audience experiencing that risk | Risk | Theme | Raised by | Date | Mitigation | Mitigation Owner |
---|---|---|---|---|---|---|---|---|---|
1 | Medium | Small | Implementor | New deployment before 3.0 is done. How do we support or advise implementation before 3.0 is available? | Migration | VR Team | 7/14/2016 |
| |
2 | Large | Medium | Are we building the right product for our target market.
| Market knowledge | VR Team | 7/14/2016 |
| ||
3 | Large | End Users | Solution is too complex for end users. | Adoption | VR Team | 7/14/2016 | Closer involvement of country reps, end-users during iterations | PC to monitor | |
4 | Medium | Developers | Solution is too complex for developers. | Adoption | VR Team | 7/14/2016 |
| and Tech Committee | |
5 | Large | Perception of code review as an acceptance of the story. The role of code review.
| Code Review | VR Team | 7/14/2016 | Define code review goals and workflow. Provide code review checklist. Continue to adopt practices and enforce standards. | |||
6 | Medium | OpenLMIS community fails to grow. Stays small and driven by self-interest. | Community | VR Team | 7/14/2016 |
| |||
7 | Medium | OpenLMIS community stays dependent on centralized funding from 1-2 primary sources and fails to diversify and encompass open source development principles. | Community | 7/20/16 | Under conversation
| ||||
8 | Medium | Donor expectations | VR Team | 7/14/2016 |
| ||||
9 | Demand for 3.0 to support the 2.0 feature set. | Expectations | VR Team | 7/14/2016 |
| ||||
10 | Medium | Tenly leaving for maternity leave | Community | VR Team | 7/14/2016 | Develop maternity handover document (done), and identify key members of team to support Governance committee, opportunity, and representation activities for 2 months until Tenly returns (early to mid-October) | |||
11 | Large | Too many new country requests. Distractions. Too many demands of project team. Scope creep. | Resourcing Scheduling | VR Team | 7/14/2016 |
| |||
12 | Medium | Poor branding and lack of attribution | Community | VR Team | 7/14/2016 |
|