Software improvement
3-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. 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. 4-In delivery The feature has been put into the delivery pipeline by the curation team, devs are working on it RIGHT NOW ! 5-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 (Archived) 0- Wishlist (curation) 2-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.
WIKI - ordered delivery backlog (pipe-ready and in delivery)
[Software improvement]
(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, …
Focusing in for the first half of 2019 - a proposal for the global community
( 2 )
[Software improvement]
(21)
Alphabetical ordering of products/variants in the Bulk Edit Products / Order Cycle / New Order pages
[1-Voting Candidates]
(9)
Improve 'Shop Closed' page to provide useful information to potential shoppers
[0- Wishlist (curation)]
(7)