Goals
To estimate the work and begin assigning work at a high level.
...
- Introductions
Why OpenLMIS
Expand Widget Connector url https://www.youtube.com/watch?v=NBaISrhvLnQ - 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
- News/Announcements (to provide context)
- 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?
...
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