Global - October 15 2019

Software Development Update

Roadmap: Living Product Roadmap 

Current sprint: Backlog Grooming Sprint 135

Upcoming sprint: Backlog Grooming Sprint 136

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: 

Open

@Wesley Brown, @Sebastian Brudziński (5 min)

3.7 Release Update

• Phase 1 of the release process testing is completed

• Phase 2 is underway, should be completed in the next day or two

Implementer Meeting Feedback

@Wesley Brown (5 min)

Meeting Notes: Implementers - October 1 2019

Highlights:

• Feedback on feature requests

  • https://openlmis.atlassian.net/browse/OLMIS-6599

  • https://openlmis.atlassian.net/browse/OLMIS-4556

OpenLMIS Private Health (Proposed Sustainability Prototype)

@Wesley Brown (10 min)

Google Presentation: https://docs.google.com/presentation/d/1VhKQyGmsCcGD-gnn3j-0v-_n_QZkcaWQXs_vpKE7Q8o/edit#slide=id.p

Feedback:

• Simon - Work similar to this is already ongoing in Angola (Primavera, AppySaude). Need to expand the operations-side of thing; things like real-time support. May need to find local partners to help actually provide this. Applications that currently exist tend to be "square peg in round hole." A dashboard on the landing page could be helpful

• Sebastian - Dashboard: Different roles would want to see very different data on a dashboard.

• Dercio - Adding a role-based dashboard could be a good new feature for core OpenLMIS

Version 3.8

@Wesley Brown (10 min)

Feature Backlog: Feature Backlog

Proposed Features:

1. Configuration Assistant

2. Stock Management - UI Caching

If we could have only one feature, which one?

• Simon - Configuration assistant; most headaches from products (facility-approved products) and supply lines.

  • Products can now be managed directly in OLMIS (as of v3.7)

• Sebastian - Concerned that we wouldn't be able to improve the configuration much in just 3 Sprints. Perhaps just focus on a single page/configuration element. Perhaps improved visualization of user roles/access.

• Sachin - Better support for non-linear facility configuration (ie, not strictly following the level-based facility structure).

  • Certain category of products might come from a hub whereas others might come from another facility. The flow of products should be able to vary.

  • Sebastian - This might be supported already, it would depend on exactly what this configuration entails. We added support for multiple suppliers in a previous version (v3.6, I think).

  • Christine - We do have flexibility in the approval configuration, but complicated to setup and validate. Would be nice to improve this area, however this doesn't change once set up.

Next PC meeting: Topic ideas??

Additional Requests and Information: