<aside> 💡 This is work in progress

</aside>

Outcomes of this discussion to be added to

https://github.com/openfoodfoundation/product-pipe/issues/4

Background

Agreed in Product Curation Nov 30th we need to work on a process how to prioritize things in the "Needs Inception" Column to move to "Ready for Inception".

This process is partly about was formerly done by voting, but now that this list is not only fed in by wishlist (issues / problems in there do also come from other sources) we need to rework the prioritization process.

Open Questions (hopefully) to be answered

1. How to define the scope of which kind of things need wider community approval (voting), what are things that we can prioritize within the "product curation circle"

   Example: History of Invoice Changes (https://github.com/openfoodfoundation/inception-pipe/issues/11) needs community approval to be moved into the pipe, whereas Mobile UX - Usertesting (https://github.com/openfoodfoundation/inception-pipe/issues/7) can just be decided to be a priority within the product circle / product curation meeting.

   Criteria:

   • Is this related to something that is already in play? (e.g. User Testing for a Feature that is in Inception or even Dev and needs clarification, Analytics for something that is going to be released soon)
   • Are the "resources" needed currently allocated to other (prioritized) projects?
   • Does this work block or is blocked by any other work?
   • Is there information or knowledge that exists in the community around this and is it well collected?
   • Is there a reasonable connection to a priority for OFN and the community?

2. Is there a new process that works better than "voting" for the wishlist items to enter the inception pipe? Or can we simply come up with a better voting process?

3. How does the product vision & strategy work tie into / can be aligned with this prioritization?

• Product Strategy sets the theme
  • Community votes on items underneath this topic

4. Define what things we can decide on within the product circle to be worked on, what needs wider community approval? Where is the "line" between a feature and other tasks, e.g. allocating time of product & tech on Analytics tasks

Additional Questions, that could be discussed in that context:

5. How to ensure that the community can add their issues to "Need for Inception" but at the same time reduce the overhead for product circle and avoid this column to become overcrowded (re "All the things pipe")?

Who can create issues in the Inception Pipe?

Could this replace the wishlist?

Ideas:

->Grooming of this column in Product Curation Meeting (possibly better every 2nd?) to prioritize or park items.

->If Issues added by community, promote use of problem statement template and put Label “Product Check”

"WORKSHEET"