Velocity:Context: Includes all four teams. Team performance is impacted by manual testing, regression testing began in Sprint 105, released 3.4 in Sprint 106, released 3.5 in Sprint 113, Holidays impacted 114 and 115.
Summary: Google Translate Chrome plugin can cause issues in requisition calculations. Found with setup for Angola.
Had two recommendations to have Google Translate ignore our pages but neither worked. The team felt that it was not worth the additional effort to look into this further.
Discussion on Facility Suppliers:
From Sebastian (via Slack):
Can anyone confirm that my understanding is correct... 1. It is expected that there will be only one supplying facility per supervisory node and program 2. Due to the above, while converting to an order, users will always see 1 supplying depot as an option 3. We should update the convert to order UI to no longer display supplying depot as a dropdown
Is all of the above right, or am I not understanding something correctly?
If had bar codes, would be using same functionality for GTIN. Thought is that a GTIN isn't required, but could be (e.g., medical stores may have ability to assign a GTIN). Concept is larger packaging of products that can have its own GTIN.
Manufacturer may also have created a kit that is composed of different components (e.g., like a first aid kit)
As we are going forward, do we want to change the structure or format of the product committee meetings?
Simon Dean (Unlicensed) - I'm currently ok with content. Would like to know more about the development process and prioritization process. Having insight into that would be useful.
Sebastian Brudziński - easier to see and set priorities going forward. It is challenging to do this, but it would be really useful. Could limit the options. Could involve more people. Make it easier to decide on what is next.
Dercio Duvane - I do look how we set up the meetings and content. Unfortunately, we do not have the attendance we would like to have. Is there a plan to have a smaller group specific to geographies? It is hard time for their team to join.
Ryan Freeland (Deactivated) - observed that asking for input is challenging, but it would be useful to have more input from the countries. Perhaps cold calling are finding ways for more engagement because we need to hear from them. When issues are presented, it is useful to call out which country, users, context in framing the discussion and understanding what is going on.
Wesley Brown - one challenge is this committee falls in between the governance and technical committees. we cannot rely on PC to give consistent direction in a timely manner. A possible change would be to refocus this on implementers and their needs. Give another way to give feedback on the product itself. Would like to get more feedback from other individuals.
Mary Jo Kochendorfer (Deactivated) People do want transparency in the development process but the sheer number of details makes it difficult to understand within the context of this meeting. However, people do gain value from hearing about what we're doing and giving feedback on priorities. Hope that we could find a process/feedback mechanism which this community buys into. Regarding the software development process, we could do a better job of being transparent about what we're doing and how the overall process is doing. Need to figure out how to break up the information so that it is more digestible. Other communities have had success with having a specific person (or group?) champion specific features.
Key takeaway: try to create a clear evaluation framework for prioritization so folks can contribute and weigh-in consistently.