View Source

The agenda for this event is now being maintained here: Gap Analysis Development Project

This page will be archived.

Goals

To estimate the work and begin assigning work at a high level.

We will go deeper into the specific work areas than we did during our December 7, 2017 meeting in DC. We will have attendees from each organization so we can conduct estimation activities and so we can assign initial work items to different teams.

Agenda

Introductions
Why OpenLMIS
Recap Project Background
- News/Announcements (to provide context)
  - 3.3 release marks end of Vaccine focus
  - GAVI presentations, including OpenSRP integration, open source Reporting stack
- Quick review of Dec. 7, 2017 group kick-off outcomes
  - Team Canvas (Brandon has photos/paper canvas)
  - Budget (from slides)
  - Timeline (from slides)
  - Parking Lot (Brandon has photos/paper)
Team Composition
- Review structure diagram (also below)
- Talk through each partner's team membership and their contribution to the global services
How to Estimate
- Story Points and Epic Sizes – setting common baselines
- Can we also try to simplify and talk about how we do that? Can we also talk about how we prioritize (RACI matrix of who prioritizes)?
Gap Scope Review/Estimation
- 27 features
- 10 reports
- Discuss any other priorities not reflected or any changes to priorities the team recommends
Technical break-outs
- How we will work with committees? Technical committee and architecture decisions.
- Domains and boundaries?
- Automated testing and manual testing?
Roles and responsibilities
- See section from Dec 7 slides
How we collaborate
- See section 4 from Dec 7 slides – Brandon update it for LESS scrum and for our team structure
Fail-Fest: Past OpenLMIS lessons learned
- share lessons learned? history of forking? examples of multiple partners re-doing work or going in separate directions?
Competitive Landscape
- OpenLMIS versus our peers (Logistimo, mSupply, others?)
- Call in Jake or Kaleb to set the stage?
Next Steps
- Plan July-July Nairobi/kickoff event?
- Read-out to Product Committee, PATH/DS or Governance Committee?

Attendees

JSI: Ashraf, Elias Muluneh, Muhammad Ahmed, Visva Kandasamy (Mon. morning)
Ona: Matt Berg, Peter (Mon and Tues), Clay (Tues), Craig (remote)
VillageReach: Mary Jo Kochendorfer (Deactivated), Josh Zamor, Brandon Bowersox-Johnson

Schedule

	Mon. Jan 29	Tues. Jan 30	Wed. Jan 31
	Visva (morning), Peter	Clay, Peter
Morning 1	Introductions Why OpenLMIS Recap Project Background Agenda review Ground rules/norms Team Composition	Agenda review Gap Scope Review/Estimation (cont'd)	Agenda review Present total estimates Discuss any recommendations for changed priorities
Morning 2	How to Estimate Gap Scope Review/Estimation	Gap Scope Review/Estimation (cont'd)	How we collaborate Roles and responsibilities
Lunch	Fail Fest: Past OpenLMIS lessons learned	Competitive Landscape
Afternoon 1	Gap Scope Review/Estimation (Reports)	Technical break-outs	Parking lot discussions
Afternoon 2	Gap Scope Review/Estimation Wrap-up (what's working and what's not)	Gap Scope Review/Estimation (FINISH) Wrap-up (what's working and what's not)	Next Steps / Wrap-up
Dinner/Evening	Group Dinner aka "Feed the Gap"		Depart DC

Team Structure

Tentative team structure based on Dec. 7, 2017 meeting:

OpenLMIS > OpenLMIS Gap Planning/Estimation Meeting - Washington DC, April 11-13, 2018 > gap-team-structure-tentative.png

source: https://boardthing.com/board/5a2f5126b2d40b061d0c0e19

Background

See previous gap planning: OpenLMIS Gap Analysis Software Development Kick Off - Dec 2017 from Dec 2017; Gap Analysis Development Project from Nov 2017