2018-08-10 3.5 Planning Team Discussion
Aug 10, 2018
Attendees
@Ashraf
@Mary Jo Kochendorfer (Deactivated)
@Josh Zamor (Deactivated)
@Sam Im (Deactivated)
@Craig Appl (Unlicensed)
@Wesley Brown
Discussion
Gap Selection
Not much well-defined epics left in the gap groupings.
MtG - mCSD (with Elias), Bugs/Tech Debt
Ona - Reporting (with JSI)
JSI - Reporting analysis (with Ona), Smaller Gap Features, Bugs/Tech Debt
Ashraf will discuss with core team later on smaller gap features
DHIS
(Craig) Worries about doing this without a specific target case. Building without a specific client in mind will be difficult to validate and may lead to blocks in development
(Craig) mCSD work will help more effectively manage translation of facilities from olmis to dhis
(Craig) Should start scoping out this work soon so that we can identify potential gaps in data within olmis
(Mary Jo) This needs to be discussed further and will not be worked on during the next sprint
Reporting:
Epics:
Report Analysis (24 reports)
Is information available in olmis v3?
Split up work:
Devops
Build DB Structure
Create reports?
Action Items
Need to get people together to discuss/plan future work
More business analysis is needed for most remaining gaps before development can start
OpenLMIS: the global initiative for powerful LMIS software