PC: March 12 2019

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)

ZOOM Link: https://zoom.us/j/573590175
Meeting Number: 573 590 175
US Phone Numbers: +1 929 436 2866 or +1 669 900 6833
International numbers available: https://zoom.us/u/bd2rGzbGl

Last Meeting Notes: PC: February 26 2019

AGENDA

Item	Lead (Time)	Notes and Updates

Item	Lead (Time)	Notes and Updates
Software Development Update Roadmap: Living Product Roadmap Current sprint: Backlog Grooming Sprint 120 Upcoming sprint: Backlog Grooming Sprint 121 Release: 3.6 Aiming for early April (Sprint 123) What to see what is in which release, check this out. Team stats: https://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 Interface - Interface with DHIS2 Requisition - Customizable notification messages the backend is implemented (still undergoing QA) and work is starting on the configuration UI. Kitting - Work is ongoing. 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 Webinar	@Rebecca 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 Suggestions	@Wesley 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: https://forum.openlmis.org/t/meeting-tomorrow-and-roadmap-ideas/858 New Feature Requests: https://openlmis.atlassian.net/issues/?filter=20548 Roadmap Epics: https://openlmis.atlassian.net/issues/?filter=20570 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: @Wesley Brown To create discourse post for features @Simon Dean (Unlicensed) To assist Wes in the creation of a simple format @Wesley Brown prepare a list of potential post-3.6 features to discuss on the next Product Committee
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:

ATTENDANCE:

@Wesley Brown
@Amanda BenDor (Unlicensed)
@Simon Dean (Unlicensed)
@Craig Appl (Unlicensed)
@Sebastian Brudziński
@Ashraf
@Rebecca Alban (Unlicensed)
@Sam Im (Deactivated)
Peter Galletta
Katherine Lew
@Parambir S Gill (Unlicensed)

RECORDING:

@Wesley Brown to paste meeting link once ready

ADDITIONAL READING: