Global - July 21 2020
Last Meeting Notes: Global - May 27 2020
AGENDA
Item | Lead (Time) | Notes and Updates |
|---|---|---|
Software Development Update Roadmap: Living Product Roadmap Current sprint: Backlog Grooming Sprint 151 Upcoming sprint: Backlog Grooming Sprint 152 Version 3.10:
Team stats: https://openlmis.atlassian.net/secure/Dashboard.jspa?selectPageId=12504 Velocity:
| -Velocity consistent; the last few weeks have been mostly COVID-specific sprints but now transitioning back to normal OpenLMIS -Started working on stock mgmt offline -Offline support already exists for requisitions/fulfillment. This is *intermittent offline connectivity- still need occasional connection. We are now working on this for stock movements in stock mgmt. -Offline stock mgmt 3.10 will mostly be back-end (foundational support) compatibility. Physical inventory section might be finished. Version 3.11 will include more the user facing features. So users will benefit from this after 3.11 release in mid-December -We hope to get MOST of stock mgmt done in 3.11 but likely will be completed in 3.12 Klaudia: starting with physical inventory, but don't know how far will get in 3.10; in 3.11 the other stock mgmt screens | |
| Implementer Meeting Feedback | Wesley Brown (5 min) |
|
| Product Roadmap | Wesley Brown | Start working now on offline stock mgmt as well as some bug fixes for Moz Next track is improving reporting stack and the deployment of it. We learned from Cameroon & Zim COVID implementations that it is very hard to do. COVID Edition- we are ready for Cameroon & Zim Jan 2021 the development responsibilities will start to shift to the new OpenLMIS partner Version 3.12 will be the last version that we release under the current structure With our transition- Development partner will be building on top of this version - development will continue but 'continue differently' Dianna: How does the contribution of SIGLUS figure into the Roadmap? It is responsibility of the contributing partner to adhere to design expectations/contribution processes, and participate as a partner and utilize our architecture. The role as the core team is to provide guidance and act as a gatekeeper. Steer community toward shared investment/shared benefits |
Progress Report on OpenLMIS COVID Edition | Wesley Brown / Gaurav Bhattacharya (Unlicensed) (10 min) | Development was in two areas, 1) connect it to the PCMT as a basic integration and 2) adapted the CCE service to be used for COVID-related equipment Most of the work was figuring out the product catalog; making sure the system met the requirements for each country Ongoing work that dev team will have for this project will be re: support Adapted OpenLMIS to a use case that we did not envision with very few code changes Bravo Christine on the training! How OpenLMIS generally benefited from this project: 1) PCMT integration 2) improved deployment of reporting stack 3) configuration issues were fixed Project collaborating with CHAI to manage the logistics behind COVID19 response If you are interested in possibly using the OpenLMIS COVID tool, reach out to Wes or Rebecca. Some implementation costs are covered by CHAI |
Next PC meeting: Topic ideas?? | PHMF Tiers | |
Additional Requests and Information: |
ATTENDANCE:
RECORDING:
- Wesley Brown to paste meeting link once ready
ADDITIONAL READING:
OpenLMIS: the global initiative for powerful LMIS software