Software impovement

(Archived) 0- Wishlist (curation) 5-Pipe-ready The feature has been incepted, the story map is ready, the mockups are there, the community has reached to a consent on how it’s going to be done. Then an epic is created on Github (with all the stories attached) and put into the “feature backlog” in ZenHub, and the post is moved in Discourse to that “pipe-ready” category. It is ready to be put into the delivery pipe by the product curation team. 2-Discovery When proposals have the more votes, some product people are going to do discovery job : understand deeply the need, the job to be done, the legal and technical implications, brainstorm and list feature candidates, facilitate discussions around those feature candidates, build some value-ease map, ask devs T-shirt sizing estimates, until we agree on THE selected feature candidates we want to do to solve the need. 6-In delivery The feature has been put into the delivery pipeline by the curation team, devs are working on it RIGHT NOW ! 7-Done The feature has been released, let’s celebrate !<br> If it’s not fully satisfying the need, you can open a new proposal to go further 1-Voting Candidates Here are all the ideas, things we want to change, make better, new features we want to develop, sharing problems our users encounter, etc. AFTER we checked they are small enough and clear enough to vote on and prioritize. We want to make sure we understand what we prioritize. If they are not they should go back to “wishlist (curation)” section. 3-Inception-ready When the selected feature candidate is identified, the post moves to this “Inception-ready” subcategory, where the community can, again, vote to tell how much of a priority the different features are. 4-Inception The most voted feature are then properly incepted, which means there is a product owner and a tech owner assigned to the feature, they do the story map and mockups, so the feature is ready to be put into github with all the stories attached.

About the Software improvement category [Software impovement] (1)

WIKI - ordered delivery backlog (pipe-ready and in delivery) [Software impovement] (4)

This is the single source of truth for the priority list of features ready to be put in the pipe AND already in the pipe. The idea is to reorder in real time things that are in the pipe. We might have started something, …

Enable Matomo to measure backoffice and actions [1-Voting Candidates] (1)

Enable better product transparency by allowing hyperlinks in product description field [1-Voting Candidates] (6)

Limit the available order cycles to select from for tagged shoppers [0- Wishlist (curation)] (7)

An enterprise can offer different prices for different type of customers (ex: members, wholesalers, etc.) [1-Voting Candidates] (16)

Improve UX of Products page when updating price and stock level [0- Wishlist (curation)] (7)

Alphabetical ordering of products/variants in the Bulk Edit Products / Order Cycle / New Order pages [1-Voting Candidates] (6)

Hubs can block shoppers / decide who accesses their private shop [(Archived)] (16)

Provide a more flexible reporting functionality with rich data access [1-Voting Candidates] (19)

Offer a promotion when a min nb of units of a given product is added to cart [1-Voting Candidates] (8)

CSA features : understanding how CSA work and the gap with current standing orders feature [Software impovement] (6)

Trace order amendments through invoice lines and generate legally compliant invoices [1-Voting Candidates] (16)

Enable product chain tracking & hub's variants creation [2-Discovery] (3)