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: April 23 2019



Lead (Time)

Notes and Updates

Software Development Update

RoadmapLiving Product Roadmap 

Current sprintBacklog Grooming Sprint 123

Upcoming sprint


  • 3.6 starting the release process on April 11 (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)

Version 3.6 Release Update

Final rounds of testing are happening today (for Malawi and Reports) and we are planning to roll out version 3.6 tomorrow!

Final rounds of testing are just finishing and planning on rolling out 3.6 release tomorrow or Thursday!

Next Sprint will be for 3.7; the team make up will be different moving forward; mostly SolDevelo with some support from VillageReach. Obviously velocity is expected to reduce

Version 3.6 WebinarRebecca Alban (Unlicensed) (5 min)

Registration URL:

Potential for future webinars in multiple languages. We are looking for community members that are willing to help lead this (Portuguese, French).

Dércio Duvane is willing to help with this! SIGLUS meeting next Friday, could discuss this at the time or plan for something in the future. Thanks Dercio!

Country-Specific Slack ChannelsWesley Brown (5 min)

Would a Portuguese-Language Slack channel be helpful for the Angola/Mozambique team? Yes! We created one: portuguese_moz_ang. This will be disseminated to others by Dercio and the rest of the Moz team

If others have channels that they want created on Slack or Discourse for country or language specific dialogue, just let the steward team know

Implementation Feedback - AngolaSimon Dean (Unlicensed) (15 min)

Provide the MoH with context for how a digitized supply chain can benefit them. There were a number of training and capacity building activities to that end

SIGLOFA is the name in Angola- Sistema Informatica de Gestao de Logistica Farmaceutica de Angola

Rollout of the initial pilot in March - Hospitals in Luwanda, another pilot in April, testing and training May-June, June-July UAT (last pilot), National launch in August (many trainings throughout the country)

Provided responsibilities within the MoH within a technical working group-foster ownership and sustainability. Lead of the group is the IT Lead with the MoH

Refined requirements and got more user feedback in 2 learning sessions, 3 days each. That included the launch of the validation instance

Established a lot of SOPs for supply chain at various levels, and an M&E plan - from scratch! Need to create an SOP that works with OLMIS as well as the fallback paper-based system.

Goals of the pilot: evaluate the system, provide training to users, install hardware, re-assess sites for readiness, re-assess inventory

Implementation Challenges:

  • Most sites have reliable(ish) power. The power still goes out 4-5 times a week for less than a couple of hours. They are currently not targeting the cold chain.
  • There were some issues completing the inventory process (meds were not the same as what was listed on National Med List).
  • SOPs needed updating to improve how they do reporting
    • Differences in how stock is counted between sites
  • Area for improvement: MoH use of GS1 standards
  • Reinforce messages from the SOPs in the roll out training since the SOPs are new, they are still not well adhered to

Technical Challenges:

  • Still working on version 3.5 due to the scheduling of 3.6 release
  • Large amount of work to get the OpenLMIS Reports set up and configured
  • Translation work has taken longer than expected
    • Built-in OpenLMIS Translations worked fine, implementation-specific changes were problematic

3.7 Feature Priorities

Wesley Brown (15 min)

Potential 3.7 Feature List Moved: 3.7 Scope Planning

Products that are used for multiple programs: if you create different product codes that can introduce issues with GS1; want to have visibility of data–if it gets updated for one program, does it update for others? Yes, if you are using the stock management  function, it would get updated for the other program. If there are different codes associated with different programs then they would be treated separately. There could be other implications here that need to be validated/thought through

Product Committee SurveyWesley Brown (5 min)

Last chance to respond to the survey!

Next PC meeting: Topic ideas??

Survey Results, Implementation Feedback

Additional Requests and Information:

ATTENDANCE: Wesley Brown Christine LenihanRebecca Alban (Unlicensed)Sebastian BrudzińskiSimon Dean (Unlicensed)Dércio DuvaneParambir S Gill (Unlicensed)Sam Im (Deactivated)Ashraf


View file