2019-01-31 Gap Governance Meeting notes

Check-in on Budget/Spending

Contracting Update

Any concerns or updates?

Double check the contract end dates.

• Contracts end 31 May 2019

Travel Requests

Please submit your USAID concurrence request to Wesley Brown. 

Important for 3.6

• DHIS2 delivery
• Kits
• Notifications
• Performance improvements 

What's not reflected?

Teams did work which wasn't a part of the original scope. Tech debt, bugs and testing improvements. Any suggestions on how we talk and account for that work so donors understand the importance and long-term value it brings?

Discussion:

• Interfaces haven't made much headway - We should reflect on.
• The reporting burn down estimates were off from the beginning
  • We didn't estimate enough time for infrastructure work
  • The majority of the work from April until September was all infrastructure and the bulk of our scope was the visualizations. The level of effort on visualizations wasn't able to get started until that infrastructure was completed.
  • The visualization work started in September through November, that helped drop epic points during that period.
• Feature work was invested in.
  • Did we adequately represent the feature work in the original scope?
• A lot of work that the teams were doing is not reflected in this burn down. This includes working on bugs, maintenance and systematic improvement.
• When we look at the final numbers, there is a lot of scope we didn't get to on the burn down chart. We need to develop a story that identifies what was worked on and how that relates to the grant.
• This gap burn down was only 3/4 of the original scope.
  • We will not get to all of this scope that we identified.
  • There are items in integrations we won't get to as well as reporting.

Ashraf Reflections

Reporting

• The field teams like the visuals.
• The field teams still want to see the "formal" reports which come out looking like (PDF exports with headers, tables and labels)
• More work needs to be done on how to sell and switch expectations from the formal reports to looking a visuals to do analysis.

Wes

• Each team organized their work differently in terms of epics and tickets. It's possible that the graph is skewed.

Mary Jo

• The original Epic Points were on two different scales. The feature work was estimated at about half of the reporting work. However, the feature work and reporting work level of effort were not necessarily at that scale. For example, there were two teams working on feature work and one on reporting. This chart suggests that much more was delivered in reporting than in feature work.
• We should review how we present this to the stakeholders at the end of the grant.

Brandon - hasn't been able to connect or figure out a way that the $600,000 could be used to support building out the gap features. Right now focused 

Can the trusted partners and community identify opportunities locally that help them address these scope gaps?

PwC does have plans to reach out to the mission around the migration.

Another potential opportunity is with the Zambia RFP (start in Oct 2019) to pitch migration and potentially funding more of the gap features.

Team Performance

Please note that performance does NOT include meetings, design work nor testing. Points do not reflect all the work completed but are the best measure at this time and help us understand where the effort is during the sprints.

Risks for 3.6

Please share if you feel there are any key risks to completing 3.6 on time and with the defined scope.

3.6 Feature List

• Report capacity meeting
  • This is a valid risk. Craig will work with Clay to begin this process
• 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
• 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.
• Notifications
  • We started later than planned so may have challenge in delivering. Will need to remove blockers asap.
• Performance improvements