May 3rd 2016

Next steps on maturing our process for vetting project proposals (see memo & graphic)

• Soliciting project proposals from non-product committee members
• Responsibilities / Expectations of product committee members
  • Cross-country functionality (based on current knowledge or researched - what does "due diligence" look like in this context?)
• How are decisions made?
• On-going involvement with projects
  • What do check-ins look like?
  • Implementation team augmentation?
• Verification of global accessibility

The product committee recognizes that a clear process for vetting project proposals needs to be defined. To this end, we have recently introduced a process to review new project proposals for global requirements, to investigate cross-country demand for features, and to inform what features belong in the core OpenLMIS product.

Consider a 1-2 day in-person to make bylaws concrete if possible

2.x vs. 3.x Country Recommendations (see memo)

Round-table on prospective projects