PC: February 26 2019

Call Information

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

Last Meeting NotesPC: February 19 2019



Lead (Time)

Notes and Updates

Software Development Update

RoadmapLiving Product Roadmap 

Current sprintBacklog Grooming Sprint 119

Upcoming sprintBacklog Grooming Sprint 120


  • 3.5 Release Retrospective coming soon
  • 3.6 Aiming for the end of March
  • What to see what is in which release, check this out.

Team statshttps://openlmis.atlassian.net/secure/Dashboard.jspa?selectPageId=12504

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

Mockup for Kits

Epic:  OLMIS-1302 - Getting issue details... STATUS

UI Mockup: https://openlmis.mybalsamiq.com/projects/olmis-5987/grid

Ashraf (10 min)

Discourse Discussion: https://forum.openlmis.org/t/soliciting-feedback-mockup-for-kits/4979

2/26 update: Updates to the mockup have been made since feedback was received from Josh.

Josh: If you are able to create an unpack list, maybe you should be able to remove an unpack list.

Ashraf: Save Orderables is not currently part of the scope of kits

Wes: How do we remove a product from the kit on this screen?

Transitioning the Product Committee

  • Wes asks members what they find valuable (or not) to restructure going forward.
Wesley Brown (15 min)

Do we want to change the structure or format of the product committee meetings?

Previous Discussion

Possible Ideas:

  • No changes, keep it how it has been
  • Split up to smaller, more geographically-focused meetings
  • Switch context to be more of an implementer feedback meeting
  • Focus on new feature prioritization and design
  • Content: How do we gather content for each PC meeting agenda?

Time can be inconvenient for many of the implementers and could make it difficult for them to participate

Simon - Timing is difficult but having everyone "together" is valuable

Wes: Feedback is requested by core teams more than implementers

Amanda: Explaining the importance of the Product Committee, adding to communication/newsletter, survey existing members.

Craig: Technical working groups during implementations could discuss priorities and communicate to PC

Simon: Language is a limitation (Portuguese)

Wes: Updates from implementations as they are in progress 

Rebecca: themed meeting agendas - every month a different implementer leads, have an agenda item for an implementer/partner to share

Next PC meeting: Topic ideas??

Feature requests/priorities for version 3.7

Additional Requests and Information:


Amanda BenDor (Unlicensed)Rebecca Alban (Unlicensed)Sebastian BrudzińskiCraig Appl (Unlicensed)Simon Dean (Unlicensed)AshrafBrian TaliesinJosh ZamorRyan Freeland (Deactivated)Sam Im (Deactivated)Wesley Brown




OpenLMIS: the global initiative for powerful LMIS software