Hello PC,
After the 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
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:
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.
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.
Ben -
I'm friendly to all the tickets except
OLMIS-3796, which I agree needs more definition to make sure the feature really meets user needs (example: we support users with no email addresses, how would they be notified of system down time?)
It would be great if you or Nuran Idris would start a new email thread and re-state the problem that OLMIS-3796, hopes to solve.
I think slowing down the development of the group email messaging feature, and working to build consensus within the community would be a great exercise for all of us.
Happy Holidays,
-- nick --
Nick Reid | nick...@villagereach.org
Software Developer, Information Systems Group
VillageReach Starting
at the Last Mile
2900 Eastlake Ave. E, Suite 230, Seattle, WA 98102, USA
CELL: +1.510.410.0020
SKYPE: nickdotreid
www.villagereach.org
Hi Ben and Product Committee,
It’s been a few weeks so I wanted to jump-start the conversation about the Malawi-requested tickets:
OLMIS-3794 – Nuran has answered Mary Jo’s last question, and I left a new question for Sebastian about the revert/undo. Overall, Mary Jo had said she wanted “more refinement and information before determining if [this is] globally applicable”.
OLMIS-3702 – Lots of questions have been answered in the comments of this ticket. Perhaps Ben could now update the ticket description to reflect all of this and to have Acceptance Criteria. Mary Jo already said this one is globally applicable and will be welcome into core.
OLMIS-3793 – I wrote some suggestions for Ben on how to flesh out this ticket. He let me know that Christine and Nuran are planning to discuss the tickets. Mary Jo also said this one is globally applicable.
OLMIS-3796 – Nuran, did you have any thoughts on Nick’s question below about a fresh explanation of what problem we are trying to solve. The Product Committee discussion offered lots of ideas, tools and alternatives.
-Brandon
Hi Product Committee,
I also wanted to provide an update on Number 1 below from December's meeting. Mary Jo stated below that the phased approach for moving forward is starting with Option 1B (Allow Physical Inventory without requiring reasons for the entire quantity change). That is now captured in this ticket: https://openlmis.atlassian.net/browse/OLMIS-3921 . Feel free to add comments on that ticket or reply if you would like this topic to have some discussion/updates at the next PC meeting.
-Brandon
From: Mary Jo Kochendorfer <MaryJo.Ko...@OpenLMIS.org>
Date: Thursday, December 21, 2017 at 5:41 PM
To: openlmis_prod...@googlegroups.com
Subject: PC follow up
Hello PC,
After the 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
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.
…(snip snip)…