2019-02-21 Gap Governance Meeting notes

• We did not update the budget below because the financial person is out on holiday.
• See the table below (In Progress)
• The projections are high-level projections through the end of the grant. March may have more funding spent around the release time.
• Discussion:
  • Risk - Travel for an in-person meeting to share reporting scope

Please submit your USAID concurrence request to Wesley Brown. 

Brandon: Might be a great opportunity to bring together many different groups that are using or interested in using v3 (including implementations) to Nairobi. Would be a good chance to get devs together with implementers and others in the community

Ashaf: Agree!

Craig: Suggestion to just focus on devs with remote access for others. Possibly after the release but before Easter (April 21st) - so maybe around the week of April 8th or after Easter on the 29th. Likely could be hosted at Ona offices. As another option, could also host a number of recorded video calls.

• Wesley Brown To discuss with VR, SD, and countries and get possible numbers.

January and February (Sprints 117 &118)  -  Gap Project Review

Team Feedback:

• Across the board
  • Last two sprints have been good. Some of the story points are higher than normal because we have been encouraging the teams to include all of the work they are doing on tickets. Other things such as regression tests weren't getting captured.
  • There are contributions from every team.
  • We have made good progress even though we have still been scoping primary 3.6 features
•  Ona
  • No comments
• JSI
  • No comments
• MTG
  • Not present

3.6 Feature List

• Report capacity meeting
  • This is a valid risk. Craig and Clay have begun this process
  • We discussed this above.
• DHIS2 delivery
  • We haven't clearly defined the transportation of information from OpenLMIS to DHIS2
  • The specifics still need to be figured out
  • We need to figure out what other things we can do to work on while this is being discussed
  • Is this stuck? - No
  • Separated concerns
    • Reports from standard API ← ONA
    • Transport from OLMIS into DHIS ← In discussions with BAO
  • Working to expose the reports using a standards-based interface (FHIR or ADX)
    • Still researching which interface to base the work on (with Josh)
      • FHIR - Have to define the OLMIS resources as they are not currently defined
    • Technical research to determine if FHIR can be used is ongoing but should be done the end of the sprint
    • If FHIR is not a viable option then the DHIS feature is at risk for 3.6
• Kits
  • Suggesting a scaled-down version of this feature
  • Needs support on what the essentials are and what will be completed.
  • Wesley Brown and Ashraf work together to get a clear scope and plan in place.
  • Time is running short to start work because of delays in design
  • Orderable
    • Discussions have been occurred to get this design solidified, a discourse post has been created for the orderable portion of the kitting work.
      • Elias is already working on backend changes that are already well defined
    • Not blocked right now, but may become blocked in the near future if the UI questions are not confirmed soon
  • Stock Management
    • This is still under discussion, unclear if this should be considered an Adjustment or part of the normal stock workflow
• Notifications
  • We started later than planned so may have challenge in delivering. Will need to remove blockers asap.
• Performance improvements