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. (Archived) 1-Wishlist Here are all the ideas, things we want to change, make better, new features we want to develop, sharing problems our users encounter, etc. 2-Discovery When proposals have the more votes, some product people are going to do discovery job : undertand 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 ! 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. 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 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.
Trace order amendments through invoice lines and generate legally compliant invoices [1-Wishlist] (10)
Make info on quantity ordered/delivered/invoiced/voided/paid accurate and improve packing operation efficiency [(Archived)] (12)