Product Committee on the 19th, there were three things we said we’d follow up on email. I know the following is a bit dense, please do review and respond to this email with comments. I will be out of office until Jan 10th so make sure to respond to the listserv so Sam and others can field/incorporate your comments.
Topics to follow up on
Update on the decision for how to address issues related to sending data from the report and requisition into stock cards (within the stock management service)
Reviewing and prioritizing Malawi new feature requests.
Approach to redesign emergency requisitions.
Number 1: First, we understand it is challenging to understand the details raised around the current challenge with connecting the services (outlined
here). As a recap, the problem is when Report and Requisitions (R&R) are approved out of order (upon approval the stocking information is sent to stock cards as a physical inventory). Our phased approach to solve this issue is to move forward with option 1B (Allow Physical Inventory without requiring reasons for the entire quantity change) first and then begin work to support the reversal functionality. We recommend implementers to monitor reporting rates and encourage users to approve R&Rs in order. I know this entire scenario is challenging to follow. Please do not hesitate to reach out with questions or comments. We can continue to discuss this during the next product committee meeting.
Number 2: Following up from the PC meeting, I am requesting folks to review the tickets and let me know if you think these are project specific and not globally applicable. From my review, I believe OLMIS-3793 and 3702 are globally applicable and would bring value to the core. I believe OLMIS-3796 and OLMIS-3794 need a bit more refinement and information before determining if they are globally applicable. I WELCOME input from others so that we have input from a wide variety of members.
In addition, could someone on the Malawi team please review the list of requests and provide information on the following:
Are there any time sensitives around these requests?
Is there bandwidth on the Malawi team to work on these and submit a pull request?
Are the current priorities accurately reflecting your priorities? Currently OLMIS-3794 is critical.
If possible, please update the descriptions of the ticket to highlight the end user value. I created a user story for OLMIS-3702 which I’d like review of to ensure I captured the need/value
What next? Currently most resources are out on holidays. In the new year, we need to prioritize these requests. Currently I believe they will fall into the following based on level of effort, priority and resources.
Label OLMIS-3793 to the “quick win” category that developers can pick up in spare time since it is an easy/straight forward ticket.
OLMIS-3702 I will try schedule prior to the 3.3 release.
OLMIS-3796 needs more research and can be folded into the Gap Analysis project given the needs around notifications (see
Notifications – Push Reminders spec).
OLMIS-3794 I left some questions for Nuran.
We can provide an update on the upcoming product committee meeting.
Number 3: Sam will send an update on the current approach next. Please review once it is sent.