Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

Call Information

  • 08:00 PDT - Seattle
  • 11:00 EDT - New York, DC
  • 17:00 CAT - Zambia/Malawi (UTC+2)
  • 18:00 EAT - Tanzania/Kenya (UTC+3)

Last Meeting NotesPC: February 26 2019



Lead (Time)

Notes and Updates

Software Development Update

RoadmapLiving Product Roadmap 

Current sprintBacklog Grooming Sprint 120

Upcoming sprintBacklog Grooming Sprint 121


  • 3.6 Aiming for early April (Sprint 123)
  • What to see what is in which release, check this out.

Team stats

Velocity: Context: Includes all four teams.  Team performance is impacted by manual testing, regression testing began in Sprint 105, released 3.4 in Sprint 106, released 3.5 in Sprint 113, Holidays impacted 114 and 115.

Wesley Brown (5 min)

3.6 Scope

3.6 Feature List

Brief update

We are proposing an additional sprint to allow teams time to properly complete the features. This will mean that the release is expected to be done during Sprint 123.

3.6 Release WebinarRebecca Alban (Unlicensed) (5 min)
  • 3.6 will be big in terms of communication
  • Webinar, brochures
  • Planned for early May (just after the release)
  • We are looking to have partners present at the Webinar (demo + slides) to help showcase new 3.6 features (contact Wes or Rebecca if interested)
Post-3.6 Feature SuggestionsWesley Brown (15 min)

Version 3.6 is the last release where we are focusing on the Gap Features and the makeup of our partner teams will be changing going forward. We are interested in hearing from the community about what features should be prioritized going forward as well as receiving input on how that prioritization is done.

Discourse Post:

New Feature Requests:

Roadmap Epics:

What is the best way to gather feedback from the community on priorities?

Sebastian: Core team prepare a list of potential features from existing list (jira, etc)

Simon: Standard format for presenting potential features, nothing overly complex but enough detail to be clear

Ashraf: Review existing RFP's to see gaps

Ashraf: Do some review/prep offline, and once it's in the better shape, bring it to the PC/GC

Potential Features:

  • More detailed Stock Management (including offline support)
  • Small package startup model (OpenLMIS-lite)
  • Brian - Barcodes

Action Items:

Transitioning the Product Committee

  • Wes asks members what they find valuable (or not) to restructure going forward.
Wesley Brown (5 min)
  •  Wesley Brown to create a survey and send out (for reals this time)

Previous Discussion

Next PC meeting: Topic ideas??

Additional Requests and Information:



View file