Global - Sept 17 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/337028349
Meeting Number: 337 028 349
US Phone Numbers: +1 929 436 2866 or +1 669 900 6833
International numbers available: https://zoom.us/u/aeo2ylQBLh

Last Meeting Notes: PC: August 20 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 132 Upcoming sprint: Backlog Grooming Sprint 133 Version 3.7: What to see what is being worked on in this release, please see: https://openlmis.atlassian.net/projects/OLMIS/versions/12809/tab/release-report-done Team stats: https://openlmis.atlassian.net/secure/Dashboard.jspa?selectPageId=12504 Velocity:	@Wesley Brown, @Sebastian Brudziński(5 min)	3.7 Release Update
Implementer Meeting Feedback	@Wesley Brown (5 min)	Meeting Notes: Implementers - September 3 2019 Highlights: Angola Implementation Update Version 3.8 proposed features discussion
Philippines Trip Report	@Ashraf (15 min)	Great feedback on many different products. Possible quick-win to add: Barcoding Parambir: Would be helpful to setup a separate call to discuss @Wesley Brown to set up meeting to discuss this (will open to Product and Governance(?) committees)
Casper Project Demo (TZ Migration)	@Josh Zamor (Deactivated) / @Philip Garrison (Deactivated) (15 min)	Josh: This is a proof of concept of v2-v3 data migration Streaming approach so data flows through to v3 in realtime Allows us to build v3 reports that work with the v3 migrated data Only need to build the reports once, you don't have to build them now for v2 and then build them again for v3 Can also reduce the "all or nothing" cutover to OLMIS - could have some users on v2 while others are using v3. A slow rollout of OLMIS with an existing implementation of eLMIS
Version 3.8	@Wesley Brown (10 min)	Feature Backlog: Feature Backlog Proposed Features: Configuration Assistant Stock Management - UI Caching After loading stock-related information, the browser will cache the content so that it does not need to be requested again, improving performance Ashraf - Does this lead to offline support? Sebastian - Not directly, but it could help for the future development of offline support for Stock Management Parambir - When does the cache get refreshed? Never (orderables are now versioned so an update to an orderable would be considered a different entity) Christine - Interested to hear more about the Config Assistant, Stock Management perf improvement quite high on priorities, Offline support for SM would be good as well
Next PC meeting: Topic ideas??
Additional Requests and Information:

ATTENDANCE:

@Ashraf, @Josh Zamor (Deactivated), @Parambir S Gill (Unlicensed), @Rebecca Alban (Unlicensed), @Sebastian Brudziński, @Christine Lenihan, @Wesley Brown, others?

RECORDING:

@Wesley Brown to paste meeting link once ready

ADDITIONAL READING: