AGENDA

Item	Lead (Time)	Notes
Software Development Update Roadmap: Living Product Roadmap Note: Requisition enhancements needed for vaccines relates to the features needed to support vaccines. Specifically it will relate to re-order or need estimate calculations. Past sprint reports: Sprints 21-Present (v3.0.1 - 3.2.0+, March- 2017) Current sprint: Backlog Grooming Sprint 32 Upcoming sprint: Backlog Grooming Sprint 33 Overall updates: Performance Testing and Improvements User permission strings and HTTP level caching (from 1 second each time to 500 milliseconds only once) - Jenkins Orderable search (10 times faster) - Jenkins Test strategy updates: Test Strategy. We can now visually show our manual test coverage: Test Metrics Dashboard. Discussion on scope and priorities for 3.3 release of vaccine features. May need to extend or review scope. We need to review and start planning out the features identified in the gap analysis effort.	Mary Jo Kochendorfer (Deactivated)	This is a feature release for 3.2 that includes pushing Cold Chain Equipment and Connecting Stock Management and Requisitions. We will be prioritizing bugs into Sprint 33. Performance Improvements Tickets You can see performance tracking in Jenkins. We want all community members to check in and see performance. Jenkins is free so the graphs can be hard to read, so if we feel as a community we need better visualization please let us know. Test Metrics to provide easy monitoring over features under development. Not much time can be spared on the Vaccine Module, roadmap might change a bit. Q&A Ashraf : How different is the OpenLMIS Test Metrics from the sonar? A: This is an additional tool that tracks manual tests
Gap Analysis Update Gap Analysis: eLMIS Tanzania & Zambia and OpenLMIS 3.x 41 features (19 recently added by Ashraf) 13 related to reporting Next Steps: Prioritization. Meeting in DC next week with USAID to discuss outcomes and features.	Amanda BenDor (Unlicensed)	Idea for how to prioritize (here) Mary Jo Kochendorfer (Deactivated): The gap analysis wrapped up last month, and then Ashraf added 19 features. We need to review them and finalize if they are all gaps. Also, some of these features are not in eLMIS or OpenLMIS but are high priority features. Most of the features have been prioritized by the countries as high. We are still cleaning up and making sure this information is accurate. We want to determine LOE with team by Friday. Next week we need to present to governance and USAID. The documents will be used as a guideline to weight priorities per country thus creating a more extensive roadmap for development. Ashraf Islam (Unlicensed): For the features currently used by countries such as Malawi, would these countries expect a downgrade? Mary Jo Kochendorfer (Deactivated): This doesn't mean we won't get features built, we just want to prioritize. Malawi has requested some similar features that were identified in the gap analysis. If we have everyone's input and some are similar, then we can look at that (Malawi, Mozambique). We will review those affected and the plan to upgrade, and then review more broadly.
Adding a date to the requisitions OLMIS-2833 - Getting issue details... STATUS		We are almost done with this feature, but need input on if it must be configurable (either defaulting to the last date in the period or user input). Gaurav Bhattacharya and Ashraf: Suggest the system keeps the default date (last day of the period) due to: Extra workload for users; Integrity of date entered by the users (will they just select the last date of the period or will they select the date they completed the count) Ashraf Islam (Unlicensed): R&R is an as of date. The SOH as reporting on ending balance should be period close date or as of date. Mary Jo: Periods could fall on a Saturday or Sunday. Malawi wants to stay with the default. When we talk about moving to transactional information you want the user input date. Its more important to have the actual date you're looking at your stock so its more accurate. The date the information was actually captured vs the period. Parambir S Gill (Unlicensed): The stock date is done on a certain day. What's the date of your physical stock card? That's the date I put on all my data. This could be mandatory or optional. Training would solve the issue of workload for users, it doesn't decrease or increase workload. Christine Lenihan: I agree with the premise and I see the value. But without having a default or configuration to turn it off, it assumes the person entering the date knows when the stock count happened. Right now the end of period is assumed for the district users in Malawi. If Stock Management isn't being used then the benefits are irrelevant. It adds an extra piece of data that the district has to enter for each program and for each facility. Parambir S Gill (Unlicensed): I agree with Christine. This is the path to going transactional. But let's keep it optional and configurable. Defaults are the last date of the reporting period. When this goes to a transactional system, then it doesn't become a burden in the workload. Then we we go to transactional the user will be required to enter the actual date. Mary Jo Kochendorfer (Deactivated): We will take a look into making this configurable.
Feature Improvement - Skipping and adding products Removing and adding products to the facility type approved product list. Discussion on the "favoriting" of products and experience of skipping and adding back products. A version of this is implemented in eLMIS and identified in the gap analysis see Requisition - R&R Product Lists Malawi would like this feature MW-340 - Getting issue details... STATUS	Mary Jo Kochendorfer (Deactivated) and would like to hear from someone on the Tanzania eLMIS team and Malawi to understand the request and desired behaviors	Will be discussed on a separate call, see next steps. Notes from the call on 24 Aug 2017 Participants: Ashraf, Parambir S Gill (Unlicensed), Christine Lenihan, Mary Jo Kochendorfer (Deactivated) Ashraf - issues with performance due to the fact of saving lineitems for products that aren't being reported on. Time-consuming. Are we saving all LineItems? Add products back via a button on the top right (not adding to more vertical real estate) (would like the search to do both the code and product name) Should we tie the skip/hide directly to the selection? Most think it isn't needed. Ashraf mentioned they may accidentally select the hide and don't meeting.
Feature Improvement - Skipping periods Skipping periods. It would be good to hear how Tanzania and Zambia used the skip period button in their implementations. Malawi would like to see a change of permissions. Currently the skip feature is only controlled by program. "In many situations, however, the ability to skip a period would potentially be limited to admins or supervisors at the facility level, so periods did not get skipped in error. The skip function, like the delete function, should have a right assignment within the Create/Submit supervisory role."	Ashraf or Alfred Mchau (Deactivated) or Alpha Nsaghurwe (Unlicensed)	Will be discussed on a separate call, see next steps. Notes from the call on 24 Aug 2017 Participants: Ashraf, Parambir S Gill (Unlicensed), Christine Lenihan, Mary Jo Kochendorfer (Deactivated) On an ad-hoc basis: A facility in-charge was on maternity leave and didn't report that month or quarter. Or perhaps they mailed the paper report but somehow it was lost ?! The skip period also needs to be enabled for the facility edition. R&R skip period is used frequently and only program. Christine: Are there ever any scenario where they accidently skipped. Ashraf will follow up with us and show us how they can 're-open' a skipped R&R. Parambir S Gill (Unlicensed) asked about what happens when the requisition&report is late (after the re-open)? Would they still Request Quantities or just fill in the Report side? Ashraf mentioned they may just do the reporting side versus doing the requisitions piece since they may have already placed an emergency requisition.
Questions on upcoming work/features: View Requisitions page enhancements: OLMIS-2700 - Getting issue details... STATUS What are the primary use cases for this page? Are users interested in viewing historical requisitions? Are there any comments on the filters and sorts?	Sam Im (Deactivated) (10 min)
Member updates? Upcoming travel or opportunities?
Administrative question - the following people have two user profiles in confluence, please let me know which one you use so I can delete/deactivate the others. It is important we are @ menting the correct one so you receive the alerts. Alfred Mchau (Deactivated) or Alfred Mchau (Unlicensed) ? Ashraf or Ashraf Islam (Unlicensed) ? Alpha Nsaghurwe (Unlicensed) or Alpha Nsaghurwe ?	Please respond via email to Mary Jo directly

ACTION ITEMS:

Mary Jo Kochendorfer (Deactivated) to schedule a future product committee meeting for a more indepth discussion around product performance tracking in Jenkins
Mary Jo Kochendorfer (Deactivated) Schedule a product committee call to discuss the tools used for tracking tests on OpenLMIS
Mary Jo Kochendorfer (Deactivated), Tenly Snow (Deactivated) Set up a meeting with Parambir S Gill (Unlicensed), Ashraf Islam (Unlicensed) and Christine Lenihan to discuss the feature improvements and solicit feedback (this week). Chifundo Chilivumbo (Deactivated) asked to join. Alfred Mchau (Deactivated) are you interested in joining the call?

ATTENDANCE:

Alfred Mchau (Deactivated), Amanda BenDor (Unlicensed), Ashraf Islam (Unlicensed), Ben Leibert, Chifundo Chilivumbo (Deactivated), Christine Lenihan, Dércio Duvane, Parambir S Gill (Unlicensed), Tenly Snow (Deactivated), Mary Jo Kochendorfer (Deactivated), Sam Im (Deactivated), Jonathan Hughes

RECORDING:

Video: OpenLMIS Product Committee Meeting-20170815 1552-1.arf (download the WebEx video player here)

ADDITIONAL READING: