Implementers - February 4 2020

Owned by Wesley Brown
Last updated: Feb 04, 2020
2 min read

Call Information

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


Last Meeting Notes: Implementers - January 7 2020

AGENDA

Item

Lead (Time)

Notes and Updates

Software Development Update

Roadmap: Living Product Roadmap 

Current sprint: Backlog Grooming Sprint 143

Upcoming sprint: Backlog Grooming Sprint 144

Version 3.9: 

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

Velocity: 

Wesley Brown, Sebastian Brudziński (5 min)

Development Update:

Global Product Committee Update

Wesley Brown 

Meeting Notes: Global - January 21 2020

  • SAVICS Partnership Update
  • Version 3.9 Update
OpenLMIS Upgrade EffortsWesley Brown
  1. (Mozambique) SIGLUS Upgrade - Underway; anticipated completion in 6 months
    1. SELV is also being upgraded; those systems will remain distinct for now but hope to integrate into the future
  2. Potential Tanzania Upgrade - Planning; goal to start that in Q2 2020 but there is no current project plan or funding

3.9 Feature Priorities

Wesley Brown (15 min)

Feature Backlog: Feature Backlog

Focus for 3.9 - Stock Management

OLMIS-6732 - Getting issue details... STATUS

  • Evaluating Stock Management Performance
  • Stock Management Bugs


Diana: How can other community members impact the backlog and priorities?

  • One way is via those meetings - the product committee
  • We often discuss the release focus right after the release
  • There's also a feature backlog (link above) - it can be reviewed and commented on

Diana: Is it too late to request a feature for the upcoming release?

  • It might be since there are only 3 development sprints remaining

Diana: It would be better for users if Stock Management was capable of working in a way that displays the products with lots breakdown, but also where it only displays the summary of the products

OpenLMIS upgrades

Diana: How do we ensure that upgrades are easy?

  • Wes: the OpenLMIS core team ensures with each release that each new release is backward compatible - therefore the effort to upgrade from one version of OpenLMIS 3 to a newer one should be very easy
  • Sebastian: OpenLMIS was designed for countries to be able to add their own features; but then features that would be beneficial for all would be incorporated into the core code. 
  • Joseph-Malawi had a few bugs that affected the performance in Malawi. Sebastian: we are running release candidates to help catch those bugs in the core; another possibility is that something is changed in OpenLMIS code and a possible need to update the overridden code (question)

Next PC meeting: Topic ideas??


Implementation/Partner Update, Feature Priorities

Possible Demo of SIGLUS (20 min)

Discuss Version 3.10 Priorities

Additional Requests and Information:



ATTENDANCE: 

Wesley Brown, Matthew Kumbuyo (Deactivated), Dércio Duvane, Rebecca Alban (Unlicensed), Sebastian Brudziński, Dianna Lourenco, Joseph Mtenje (Unlicensed)

RECORDING:


ADDITIONAL READING:

OpenLMIS: the global initiative for powerful LMIS software