2018-08-16 Meeting notes
Date
Attendees
Meeting link: https://zoom.us/j/620544583
Goals
- Discuss in-person meeting, we NEED to pick a location time (please come prepared with team availability)
- Review risks
Discussion items
Time | Item | Who | Notes |
---|---|---|---|
Any upcoming requests for travel? | |||
In-Person Meeting Dates
Required People:
| ALL | Craig core team members are booked between the weeks of 10 - 24. Craig's team would be available Sept 24 or October. Travel Option 1: The reporting stack cross-team capacity building, make sure all teams understand what we have and how it works. It is going to be ‘owned’ cross functionally (meaning each service is utilizing it so we need to know how it works and how we maintain it). Schedule: Can't happen till Sept 24 till early Oct. Goal: build capacity across the Gap team to understand the reporting stack and build reports. End of meeting, all teams know how to use the tools and build reports. How: Hack-a-thon Opinion:
Required People:
Option 2: Evaluate, streamline and develop reporting metrics, let’s meet in person to discuss. Clay and JSI are doing an assessment but I am sure there will be many things in September to work through in person. Goal: to evaluate the current gap metrics and content for reports. Define/prioritize the metrics which need to be built. Option Discussion: Could be done Virtually (Craig prefers virtually) or do in person (Ashraf/Matt prefers to have in person) Priority: Needs to unblock sprint 107 so would be challenging to do in person Required People:
Potential proposal
Option 3: Other ambiguous feature requirements, during our last team lead meeting around the 3.5 scope it was clear we need to be in person to work through open questions around feature requirements and how we want to build things. Currently discussing if we want to have an in-person meeting. Goal: build shared understanding on the feature requirements Opinion:
TODO: Mary Jo Kochendorfer (Deactivated) to schedule a phone call with Ashraf, Sam, Craig, Josh, Wes to have a virtual call to discuss how to define the ambiguous and what meetings/people are needed for each of the topics. | |
Risk Review | See notes on Gap Project Governance | ||
Gap Project Review Burn Down from Original Scope 3.4 Results
Team Performance Please note the following does NOT include meetings, design work nor testing. Points do not reflect all team work but are a measure and help us understand where the effort is during the sprints.
| Ashraf: can we quantify regression testing? Yes, we can. Let's explore ways to demonstrate design work and meetings. Mary Jo Kochendorfer (Deactivated) asked if folks could share ideas of how to augment the team performance tracking with more metrics and holistic context so that we can clearly communicate the value to our community and donors. We all agree design, meetings and testing are necessary and important and it is challenging to quantify and put metrics to those priorities. | ||
2019 Funding
| Mary Jo Kochendorfer (Deactivated) |
Gap Project Spend
Grant Amount | April | May | June | July (estimate) | Total |
$1,400,008.30 | $43,766.42 | $57,723.28 | $120,436.62 | $200,463.28 | $422,389.60 |
3.13% | 4.12% | 8.60% | 14.32% | 30.17% |
Action items
OpenLMIS: the global initiative for powerful LMIS software