2018-08-16 Meeting notes

In-Person Meeting Dates

• Week of September 3
• Week of September 10
• Week of September 17
• Week of September 24

Required People:

• JSI: Ashraf, Elias, one person from Zambia and perhaps Alpha or Hassan
• SolDelevo: Sebastian and Nikodem (Nikodem may be unavailable week of Sept 17th)
• VillageReach:
  • Josh (has passport restrictions in early september and vacation week of Sept 24, available 10 and 17)
  • Chongsun (available all dates)
  • Potentially Dercio (Dercio is available the weeks of Sept 17 and 24)
  • Wes (Wes is available the weeks of Sept 3, 10 and 17)
  • Rebecca (available 10 and 17)
• Ona: Craig, Clay, Antonate
• Malawi: ?

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:

• Craig: best done in person
• MJ: agreed

Required People:

• At least one person per team 
• Team Ona

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:

• Ashraf, Mahumad, Chris (Zambia), Alpha/Alfred (TZ), Potentially Wendy Bonnet
• Ona: Clay, Craig

Potential proposal 

• Meet in Seattle the week of August 27 between Clay, Wendy, Ashraf, Craig, (Mahumad virtually)

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:

• Perhaps smaller meetings on specific topics (fly team members to each other to unblock)

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.

3.4 Results

• 210 tickets completed (across 4 teams)
• 477.5 story points

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.

• JSI: 50.5 story points (28 tickets)
• MTG: 131 story points (59 tickets)
• Ona: 102.5 story points (46 tickets)
• Parrot: 193 story points (74 tickets)

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

• Current team funding
• Potential funding
  • Notice C
  • DIAL