...
| Risk | Discussion | Status | Approach to Mitigate | |
|---|---|---|---|---|
| 1 | Sustainability of the codebase if developer community is fragmented in knowledge | Raised by Ashraf and Craig Appl (Unlicensed). Important to consider the trade-off between velocity and cross-functional work. One team focused on component/area will achieve more than one team constantly shifting components/areas of focus. However, if the teams do not work across components we run the risk of no developers (or one team/org) understanding how to support or build on the entire OpenLMIS code base. | as of it is proposed agenda item for the first meeting | |
| 2 | Metric definition. Right now there are a ton of "Reports" with varying degree of complexity. We do not have a clear set of key metrics and why they are the key ones. | How do we get the OpenLMIS community opinionated about which metrics are priority across implementations with varying practices? Which metrics will help our implementers and drive new adoption? How do we learn from each country and organization's experiences? | Not Note yet discussed. | |
| 3 | Lack of input form Tanzania and Zambia stakeholders. Specifically on what scope of features are most important and WHY. | We understand the decision to actually upgrade is unique process/decision for each country. However, we need input from the implementations on priorities and why certain features are useful (or potentially should be redesigned). | Note yet discussed. |
Travel Budget
| Iframe | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Meetings will be held at the end of the month, prior to the check in with PATH.
<link to child-pages>
| Child pages (Children Display) |
|---|