Versions Compared

Old Version 10

changes.mady.by.user Sarah Jackson

Saved on

compared with

New Version Current

changes.mady.by.user Wesley Brown

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


The purpose of the product committee is to "build the right (correct) product". Day-to-day operations related to the roadmap, requirements, and incorporation of features into the product are handled by the product manager. The Product Committee meets every two weeks to review direction, update the OpenLMIS backlog as needed, share information regarding implementations and their relevance to the OpenLMIS platform, and decide what work from implementations should be incorporated back into OpenLMIS.

The meetings occur every two weeks and are open to the public and the schedule will be shown below. The meetings are at different times to facilitate feedback given the varied time zones that we are in. Decisions are by consensus if possible. Committees will , otherwise by vote when a consensus cannot be reached.

Meeting times and technologies will always be published on this site ahead of time

openlmis_product_committee@googlegroups.com

Committee MemberOrganizationContact Information

Gaurav Bhattacharya

CHAIgbhattacharya@clintonhealthaccess.org
Kevin CussenVillageReachkevin.cussen@villagereach.org
Ashraf IslamJSIashraf_islam@jsi.com
Renee OrserThoughtworksrorser@thoughtworks.com
Brian TaliesinPATHbtaliesin@path.org

Product Manager: Kevin Cussen

Product Committee Open Questions

Open QuestionAnswerThose PresentDecision DateWhat is the best way to incorporate country input? Need a channel for feedback on current implementations. Need a way to ensure that their message is reaching the community in a way that reveals trends without putting country-specific blinders on the community.   How do we incorporate end user feedback into product design (not implementation!) prior to doing an implementation? How do we incorporate country input into the roadmap?   What documentation does the community want (around the product, roadmap, etc.)?   What documentation should come out of an implementation?   Is the emphasis of the community on customization or configurability? Said another way, flexibility through code or limiting flexibility but with an easy to use UI?   These were the features / attributes that didn’t fit cleanly into the  “in” or “not in” domain space of OpenLMIS. Which of the following are part of the OpenLMIS Domain space?
• Realms beyond health (i.e. some interest from humanitarian space)
• Being the master product list
• Mobile support
• Offline support
• usable offline - many countries need offline capability, especially where mobile challenges exist (screen size for forms, data not feasible in some places)- interface issues may be country specific
• OpenLMIS = SaaS?
• Annual Forecasting
• Facility stock management, or clients without online capability - does the mobile/offline become part of OpenLMIS?
• Offline capability is a need (this is feedback we are hearing)
• In current state - its not possible to make whole OpenLMIS offline - but certain portions i.e. the requisition process could be made offline   Which features / processes need to work with intermittent offline access?   How do we add things to the roadmap? How are they prioritized against the existing items?   How large is the roadmap / backlog? (Community support of implementation hinges on whether a feature is on the backlog, so how do we decide if a feature is high enough to be included?)   What are the “standard” best-practice LMIS reports OpenLMIS should include out of the box?   What ERPs are out there? Which should we integrate with?   Do we call (not which is it) OpenLMIS a product or a platform or something else? All committees have this question   What are the 5 things that make you glow about this product? Everyone should make this list and then we consolidate for the community. Different use cases, value proposition. Can be leveraged for messaging.   In the future, how do we establish one person as the product manager? (similar question for the technical architect or any role that needs day-to-day and long term involvement in the community. How does the committee oversee this role?   Beyond the buckets of “in core” and “not supported”, is there a “supported but not core” bucket?   How does the community support existing implementations? Does the community seek funding to help them migrate to newer releases of OpenLMIS?   How long will the re-architecture would take and how much will it cost?
Depends on scope identified by prod / tech committee   Is it possible to set-up linked issues between different Jira's? How can we compare the backlog of OpenLMIS against those of various on-going implementations?   
 

links are published on the agenda. Please visit the meeting agenda for links and times. 

Panel
titleContact and Other Info

Discourse (Forum): https://forum.openlmis.org/c/product-committee

The Product Committee meetings month on the third Tuesday of the month at 3pm UTC.

Call in information:


Panel
titleProduct Committee Membership

Membership rotates but usually there is at least one representative from the following organizations. Please see the following point people for each organization. Please contact Wesley Brown if you have any questions or would like to attend the meetings. We welcome anyone implementing or interested in using OpenLMIS.

Organization
CHAI
JSI
Ona
Chemonics (PSM)
VillageReach
SolDevelo

Technical Product Manager: Wesley Brown at wes.brown@villagereach.org


Meeting Agenda and Notes 

Child pages (Children Display)