A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Goals | Theme | Focus | When? | Users concerned | Potential contributions from hubs | Wishlist/Discovery/ Inception | Epic/Issue | Metrics/Acceptance criteria | Lynne | Nick | Kirsten | Myriam | Enrico | Pau | Theresa | Cynthia | |||||
2 | Be a single cohesive OFN unit | Communications | A well structured and communicating global web page | 2018 - Q2 | Global website overhaul | 0 | ||||||||||||||||
3 | Be a single cohesive OFN unit | Customer Support | Ensure every user have access to a localized and up-to-date user guide | 2018 - Q1 | All | In progress, see Slack #user-guide + refresh and update Super Admin user guide | - All User Guide managers are notified when they need to update the User Guide - Any new language version can easily be set up | 0 | ||||||||||||||
4 | Be a single cohesive OFN unit | Funding | We have enough resources to support product development | 2018 - Q1 | All | Process under development, see discussion here | - Local money for Product Dev* goes into global pool (*broadly defined) - We can guarantee minimum pipe diameter for six months | 0 | ||||||||||||||
5 | Be a single cohesive OFN unit | Funding | Product dev fundings and spendings are transparent | 2018 - Q2 | All | First tool proposal | - Everyone knows where money came from and how it is spent | 0 | ||||||||||||||
6 | Be a single cohesive OFN unit | Product development process and team | Define process for product curation | 2018 - Q2 | Finalise write-up of product curation process | 0 | ||||||||||||||||
7 | Be a single cohesive OFN unit | Product development process and team | Decisions about priorities are agreed upon by the community | 2018 - Q1 | All | Discourse Process outlines https://community.openfoodnetwork.org/c/product-dev/process | - Everyone knows how to influence what is built | 0 | ||||||||||||||
8 | Be a single cohesive OFN unit | Product development process and team | Contributors works efficiently together | 2018 - Q1 | All | Github product backlog project + zenhub board + solve staging issues + testing process | - Everyone knows what to work on at any time - Everyone knows the current status of an item | 0 | ||||||||||||||
9 | Be a single cohesive OFN unit | Product development process and team | Documentation on how to contribute | 2018 - Q2 | Create v1 of contributor handbook | 0 | ||||||||||||||||
10 | Be a single cohesive OFN unit | Product development process and team | Developers don't waste precious time while developing | 2018? | All | 0 | ||||||||||||||||
11 | Be a single cohesive OFN unit | Product development process and team | Everyone knows what is being worked on now and what will be addressed later | 2018 - Q1 | All | Present document as a first trial | - Single prioritised roadmap that is built by the team | 0 | ||||||||||||||
12 | Be a single cohesive OFN unit | Single instance | Multi-currency management | Later | All | 0 | ||||||||||||||||
13 | Be a single cohesive OFN unit | Single instance | VAT overhaul | Later | All | 0 | ||||||||||||||||
14 | Be a single cohesive OFN unit | Sys Admin Standardisation | Sys Admin global team management | 2018 - Q2 | Set up a global pool of sys admins who can support any local instance | 0 | ||||||||||||||||
15 | Be a single cohesive OFN unit | Sys Admin Standardisation | Ensure accessibility of OFN platform in all operational instance | 2018 - Q2 | All | Shared process and tools between instances - audit local configs to understand and document similarities/differences | - Any sys admin can support any instance | 0 | ||||||||||||||
16 | Be a single cohesive OFN unit | Sys Admin Standardisation | Ensure accessibility of OFN platform in all operational instance | 2018 - Q2 | Background job stability | 0 | ||||||||||||||||
17 | Build the network for the OFN | Producers & hubs catalogues | Process for building our great network | 2018 - Q2 | Incept and propose a plan on implementing new network features | 0 | ||||||||||||||||
18 | Build the network for the OFN | Producers & hubs catalogues | Compound Products can be created without loosing product chain transparency | 2018 | Alterconso (Fr) | Network | - A product can be made of multiple products - A product can be split into other products | 1 | 1 | |||||||||||||
19 | Build the network for the OFN | Producers & hubs catalogues | Product chain is transparent in the OFN even if the variant of the product has changed | 2018 | Alterconso (Fr) | Network | - A hub can create their own version of a product - A hub knows when product information is changed up the chain - People are no longer creating duplicate products and producers | 1 | 1 | |||||||||||||
20 | Build the network for the OFN | Producers & hubs catalogues | Users have the appropriate permissions to build new versions of products and manage other's products versions | 2018 | Alterconso (Fr) | Network | 0 | |||||||||||||||
21 | Build the network for the OFN | Producers & hubs profiles and catalogues | Users managing multiple entreprises have automatically generated appropriate permissions | Later | ? | List, analyse and fix permissions issues | 0 | |||||||||||||||
22 | Build the network for the OFN | Producers & hubs catalogues | Stock is accurately updated through the network | 2018 | Alterconso (Fr) Epicentre (Fr) | 2 | 1 | 3 | ||||||||||||||
23 | Build the network for the OFN | Producers & hubs catalogues | Suppliers can manage the stock they allow to the hubs distributing their products. | 2018 | Epicentre (Fr) | 1 | 1 | |||||||||||||||
24 | Build the network for the OFN | Shopfront management | Hubs can define different prices for different customers for a same product. | 2018 | Alterconso (Fr) | Price differentiation | - A product can have multiple prices - Customers actually see in the hub shopfront the prices they are offered by the hub | 1 | 1 | |||||||||||||
25 | Build the network for the OFN | Shipping and Payment methods | Hubs can create and use S/P methods on multiple shops and manage permissions to who can edit those methods | Later | Fixing a UX bug so All | Create new joint table and permissions rules? | 2 | 1 | 3 | Warning here as there is a security breach... but maybe covered by spree upgrade work? | ||||||||||||
26 | Future proof the tech platform | API | Enable standalone websites to be built based on OFN | Later | Village Center (DE) | Some € here? | Reinforce API to enable standalone website to use extended OFN features | 1 | 1 | |||||||||||||
27 | Future proof the tech platform | Translations | Ensure correct translations are maintained and comprehensive | 2018 | All non English speakers | Implement https://github.com/glebm/i18n-tasks ? | 0 | |||||||||||||||
28 | Future proof the tech platform | Data consistency | Users have verified accounts | 2018 - Q2 | All | Confirmation emails, registration flow | Email confirmation | 0 | ||||||||||||||
29 | Future proof the tech platform | Data protection | Users are informed about the cookies used, for what they are used, and can opt-in our out. | 2018 - Q2 | All EU users | Create page + set up a pop-in about cookies and requesting users opt-in | EU Cookies compliance | 0 | ||||||||||||||
30 | Future proof the tech platform | Data security | Data stored on the OFN platform is secured and cannot be easily stolen by a hacker | 2018? | All | - We apply generally admitted standards on data security | 0 | |||||||||||||||
31 | Future proof the tech platform | Deletions | Entreprise users can delete information (test info or info they are not entitled to keep see GDPR) and archive info they need legally to keep but don't want to see. | 2018? | All | Enable soft deletion in OFN | 1 | 1 | 1 | 2 | 1 | 1 | 7 | |||||||||
32 | Future proof the tech platform | Deletions | Users can delete their account from the OFN | 2018? | All | Enable soft deletion in OFN | - All users appart from instance super admins can delete their account from the UI | 1 | 1 | 1 | 3 | |||||||||||
33 | Future proof the tech platform | Dependencies currency | Ensure the components we have built OFN on recent enough | 2018 - Q2 | All | Ensure software and components we depend on are maintained | e.g. Spree Upgrade | - All versions of the dependencies are maintained | 0 | |||||||||||||
34 | Future proof the tech platform | Dev efficiency | Automatic tests are formatted following the same style guide | 2018? | All | Agree on and enforce a style guide for tests | 0 | |||||||||||||||
35 | Future proof the tech platform | Dev efficiency | Ensure consistency in running tests? | 2018? | All | https://community.openfoodnetwork.org/t/enforce-consistency-between-ci-development-and-test-environments/1159 | 0 | |||||||||||||||
36 | Future proof the tech platform | Dev efficiency | Ensure consistency of endpoints reponses formats | 2018? | All | https://community.openfoodnetwork.org/t/clean-up-endpoint-responses-formats/1158 | 0 | |||||||||||||||
37 | Future proof the tech platform | Dev efficiency | Ensure bug reporting and testing is reported accurately and all stakeholders know which version they use | 2018? | All | Display software version | 1 | 1 | 2 | |||||||||||||
38 | Future proof the tech platform | Enable onboarding open source contributions | Ensure each paid OFN dev has the skills required | 2018 - Q1 | All | Certified developers process | - The paid contributors have the following required skill set: (list) | 0 | ||||||||||||||
39 | Future proof the tech platform | Enable onboarding open source contributions | Make onboarding process easy for new devs | 2018 - Q2 | All | Seed data first discussion in testing process Slack discussion | - At the end of the onboarding process the app is ready for work | 0 | ||||||||||||||
40 | Future proof the tech platform | Fraud prevention | Guarantee data inalterability | Later | All French users (legal cerificate) | - Securisation of data is ensured in a way that guarantee transactions data restitution in their original state.It can be via chaining transaction data or electronically sign them. | 0 | |||||||||||||||
41 | Future proof the tech platform | Measure Use | Enable instance managers to understand what users actually use or not in the OFN | 2018 | All | Set up Piwik (Matomo) | https://github.com/openfoodfoundation/openfoodnetwork/issues/2404 | - Each instance can see their local usage - We use usage metrics to make decisions | 1 | 1 | 2 | 2 | 6 | |||||||||
42 | Future proof the tech platform | Optimisation / Performance | Ensure load time for users are acceptable | 2018 | All | 1 | 1 | |||||||||||||||
43 | Future proof the tech platform | Optimisation / Performance | Get useful logs to improve product performance and understand issues | 2018? | All | Replace error tracking with a way to monitor cache misses | 1 | 1 | ||||||||||||||
44 | Future proof the tech platform | Optimisation / Performance | Set up a common logs tracking tool for all OFN instances | 2018? | All | Define a common strategy for exceptions logging | 1 | 1 | 2 | |||||||||||||
45 | Future proof the tech platform | Password fraud prevention | Prevent possibility of password fraud when super-admin creates a user account | 2018? | All | OFN sends a link out to validate the email address and let the user set the password at the same time | ||||||||||||||||
46 | Make what we have great | Accounting | Hubs can extract their accurate purchase data in a format that enable integration in any accounting system | Even later | Don't know yet | 1 | 1 | |||||||||||||||
47 | Make what we have great | Accounting | Users can seamlessly manage accounting for their OFN sales/purchase in an external accounting system | Even later | Expose data (API) + build integrations | 1 | 1 | |||||||||||||||
48 | Make what we have great | Accounting | Hub can extract their accurate sales data in a format that enable integration in any accounting system | 2018 | Alterconso (Fr) | Giant csv report with all data | 1 | 1 | 1 | 3 | ||||||||||||
49 | Make what we have great | All the Bugs | All the Bugs are prioritized | 2018 - Q1 | All | I think the relevant image is https://drive.google.com/drive/folders/1WalNTIqCnR_tJmtGs_qL5wonYJ36hxBO but not sure if bug process has been written up somewhere? | - We have a way to triage any bug that is raised and identify them in Github | 0 | ||||||||||||||
50 | Make what we have great | All the Bugs | The most important/urgent are included in the product dev backlog | 2018 - Q1 | All | Current epic for all S1 and S2 bugs | - We know the bugs we need to fix immediately - We have no bugs that stop users using major features | 0 | ||||||||||||||
51 | Make what we have great | Customer management | Hubs understand how their customers use OFN in order to adapt their strategy accordingly | Even later | Enable to connect some analytics tool at the level of a hub? | 0 | ||||||||||||||||
52 | Make what we have great | Customer management | Hubs can communicate easily and through appropriate messages with their potential or existing customers | Later | In the customer menu, ability to browse contacts, filter them, and copy-paste the selected contacts so that they can be integrated in an emailing tool. | 0 | ||||||||||||||||
53 | Make what we have great | Dashboard | Hubs can easily see key figures about their sales and activity | Later | Need to be specified better but first discussion here | 0 | ||||||||||||||||
54 | Make what we have great | Discovery | Improve visibility for entreprises using the same address | Later | All | Slightly separate the markers depending on the zoom level as Google Maps does? | 0 | |||||||||||||||
55 | Make what we have great | Discovery | Improve Producer visibility on OFN | Later? | All producers | Open full producer profile in pop-in from producer tab instead of fat view | 0 | |||||||||||||||
56 | Make what we have great | Invoicing | Invoices generated within OFN are legally compliant | 2018 - Q2 | All | We generate an invoice from OFN including the original order and amendments | - All amendments between orginal order and what was delivered are correctly recorded and communicated in the invoice. - It's not possible to generate two invoices with the same number and different content. - Customer can understand what the have paid for compared to what they ordered | 0 | ||||||||||||||
57 | Make what we have great | Invoicing | Users can seamlessly generate invoices for their OFN sales in an external invoicing system | Even later | Expose data (API) + build integrations | 1 | 1 | 2 | ||||||||||||||
58 | Make what we have great | Invoicing | Suppliers can easily invoice resellers for what they deliver | Even later | Alterconso (Fr) | Suppliers can easily invoice resellers for what they deliver | 0 | |||||||||||||||
59 | Make what we have great | Invoicing | Invoicing operations are smooth and easy | Later | All, Aus user priority | https://community.openfoodnetwork.org/t/multiple-order-management-index-angularised/346/1 | - All customers receive an invoice for their purchase without having to ask for it - Hub manager spend less than 5 min per order cycle to generate and send invoices to their customers - Can we include names of suppliers/producers on the invoices? (Important for hubs in Canada trying to be transparent) | 2 | 2 | 4 | ||||||||||||
60 | Make what we have great | Invoicing | Hub can facilitate invoicing operations from sellers | Later | CLFC in Canada | Hub can generate and send invoices in suppliers name | 0 | |||||||||||||||
61 | Make what we have great | Onboarding | Hubs can easily create their entreprise on OFN | Later | All | Improve entreprise creation UX | 2 | 1 | 3 | |||||||||||||
62 | Make what we have great | Orders management | Hubs can easily generate accurate packing slips | Later | Canada, some UK, poss. Aus | Hub can easily generate accurate packing slips | ||||||||||||||||
63 | Make what we have great | Orders management | Hub’s suppliers can prepare the invidual orders for the hub’s customers | Later | Epicentre (Fr) CLFC (Ca) | Hub’s suppliers can prepare the invidual orders for the hub’s customers | - Suppliers can see names of individual customers in back office and reports if hub has agreed | 0 | ||||||||||||||
64 | Make what we have great | Orders management | Enable hub to easily manage their order to the suppliers | Even later | Alterconso (Fr) | Brainstorming not done yet but box builder could be a feature candidate (needs compound products first) | 0 | |||||||||||||||
65 | Make what we have great | Orders management | Enable products dispatch per distribution location | Later | Alterconso (Fr) | Brainstorming not done yet but could be: add "location" entry in our data model and enable filtering on it. | - Hubs can get aggregated data per distribution location | 0 | ||||||||||||||
66 | Make what we have great | Orders management | Hubs can track when an order has been received by the customer | Later | All | Create a “collected” status and insert it in the order workflow | 0 | |||||||||||||||
67 | Make what we have great | Orders management | Hubs can easily manage their orders to suppliers in the most fluid and adapted way | Later | Automatically notify producers | 0 | ||||||||||||||||
68 | Make what we have great | Placing orders | Customers know clearly when their order is made | 2018? | CCC (Fr) Suteau Biosol (Fr) Epicentre (Fr) | Customers know clearly when their order is made | 1 | 1 | 1 | 3 | ||||||||||||
69 | Make what we have great | Placing orders | Hubs can customize the information they require from their customers at checkout (to make ordering as smooth as possible and max sales) | Later | Micromarché (Fr) Panier Rusé (Fr) | Checkout customization | 0 | |||||||||||||||
70 | Make what we have great | Placing orders | All customers easily go through the whole ordering process on mobile | 2018 - Q2 | (UK) Aus DorV (G) | Significant DorV (G) | Mobile UX overhaul (checkout especially) | 0 | ||||||||||||||
71 | Make what we have great | Placing orders | Customers' cart persists when they log out and log in again | Later | (UK) | Cart should save on log-out | 0 | |||||||||||||||
72 | Make what we have great | Placing orders | Managers can easily make an order on behalf of a customer | Later | All | Enable product search on the whole product name | 0 | |||||||||||||||
73 | Make what we have great | Placing orders | Customers can easily filter products in shop | 2018 | Meat only shops (Fr); Baileys Foods in Can | Enable efficient shop browsing and searching | 0 | |||||||||||||||
74 | Make what we have great | Placing orders | Customers easily go through the whole shopping process and are happy | 2018? | Customer easily go through the whole placing order process | 1 | 2 | 3 | ||||||||||||||
75 | Make what we have great | Placing orders | Customers visualize well products thanks to beautiful and consistent images | 2018? | All | Improve product images display in shop | 0 | |||||||||||||||
76 | Make what we have great | Placing orders | Customers understand clearly when their browser is too old for them to access the servive | Later | All | Clearly communicate about which browsers we support | 0 | |||||||||||||||
77 | Make what we have great | Placing orders | Hubs are legally compliant regarding sales rules | 2018? | Merchant hubs | Hubs can ask their customers to validate their own terms and conditions | 0 | |||||||||||||||
78 | Make what we have great | Point of Sale | Enable hubs to use OFN to record retail (onsite) sales | 2018 | Alterconso (Fr) Micromarché (Fr) DorV Village Cent (G) | 5 to 10K€ possibly (Fr) significant (G) | Build internal POS based on Rob's solution OR expose data and integrate with Odoo or Unicenta (pref) | - Hubs are actually using OFN to record retail (onsite) sales | 1 | 1 | 2 | 1 | 1 | 1 | 7 | |||||||
79 | Make what we have great | Point of Sale | Enable hubs to easily process payments on site | Later | Alterconso (Fr) Micromarché (Fr) | Enable hubs to easily process payments on site | 0 | |||||||||||||||
80 | Make what we have great | Point of Sale | Enable hubs to handle variable weights onsite sales | Later | Micromarché (Fr) | Enable hubs to handle variable weights onsite sales | 0 | |||||||||||||||
81 | Make what we have great | Producers catalogues | Producers can prove their product quality claims to their customers | Later | Suteau Biosol (Fr), Bailey's (Can) | Upload and display product quality certificates | - Producers are able to upload properties certificates | 0 | ||||||||||||||
82 | Make what we have great | Producers/Hubs catalogues | Hub manager is aware of the impact of the modification he makes in his products catalogues on active order cycles | Later | CCC (Fr) Suteau Biosol (Fr) | Display warning pop-up if products listed in active OC are modified? | 0 | |||||||||||||||
83 | Make what we have great | Producers/Hubs catalogues | Entreprises can easily fuel their products catalog from an existing list | 2018 - Q2 | DorV (G) several big potential users (UK) | Product import | 0 | |||||||||||||||
84 | Make what we have great | Reports | Agents can quickly access the reports they use the most | Even later | All | Users need quick access to the reports they use the most | 0 | |||||||||||||||
85 | Make what we have great | Reports | Enterprise managers can access the page of the report they want to generate | 2018 - Q2 | All | Remove page timeouts by not loading report info until filters are set | GH #2210 | - People who are on a broadband network can click on any report from "report" menu and access the given report page without experiencing timeout. | 0 | |||||||||||||
86 | Make what we have great | Reports | Existing reports are accessible for all users | 2018? | All | Existing reports are accessible for all users | GH #2099 | - People can use existing reports = people who are on a broadband network and trying to get max one year activity data don't experience timeout | 1 | 1 | ||||||||||||
87 | Make what we have great | Reports | Existing reports are enabling errorless delivery organization | 2018? | Epicentre (F) | Remove default start date? | 0 | |||||||||||||||
88 | Make what we have great | Reports | Reports are flexible and enable rich data access | Later | All | Build huge core reports + existing pre-defined reports (existing) | 0 | |||||||||||||||
89 | Make what we have great | Shopfront management | Hubs can decide who accesses their private shop | 2018? | All private shops | Remove access to a private shop to a customer | - Hubs can remove access to their private shop to any given customer they want | 2 | 3 | 1 | 6 | |||||||||||
90 | Make what we have great | Shopfront management | Hubs can use the cheapest payment gateway in their specific situation | 2018? | Alterconso (Fr) Micromarché (Fr) | Micromarché happy to pay for the payment gateway they need (the cheapest in France) | Don't know yet but Paybox direct plus could be needed for Europe | - For every hub, the cheapest payment gateway in their solution can be used through OFN to collect payments | 0 | |||||||||||||
91 | Make what we have great | Shopfront management | Hubs can facilitate direct sales from suppliers through the hub shopfront. | Even later | Big potential users (Fr) | Split payment? | - Money corresponding to product prices goes directly to the suppliers | 0 | ||||||||||||||
92 | Make what we have great | Shopfront management | Customers can set up themselves their subscriptions from the hubs website | Even later | Alterconso (Fr) | Don't know yet | 0 | |||||||||||||||
93 | Make what we have great | Shopfront management | Hubs can manage their shop easily from a mobile device | Even later | 0 | |||||||||||||||||
94 | Make what we have great | Shopfront management | Enable advance/credit management & payments | Later | Alterconso (Fr) | Alterconso could contribute financally to it? | Enable customers to pay (partially or fully) with their credits | - Customers can pre-pay future orders and use their credits to shop (given hub authorization) - Hubs can actually set up a limit under which credit payment can't be used to shop - Hubs can know whose members are running out of money (can send reminder) | 5 | 5 | ||||||||||||
95 | Make what we have great | Shopfront management | Subscriptions can be set up by a hub manager | 2018 - Q2 | Alterconso (Fr) CCC (Fr) All CSAs (UK) | In the delivery pipeline | 0 | |||||||||||||||
96 | Make what we have great | Shopfront management | Customers can set up themselves their subscriptions given hubs rules | Later | Alterconso (Fr) CCC (Fr) All CSAs (UK) | Subscriptions v1 | - Customers can set-up / modify / pause / cancel subscriptions given hub rules - Hub can set up rules under which customers can manage their subscriptions | 0 | ||||||||||||||
97 | Make what we have great | Shopfront management | Hubs manager easily manage their shopfront (navigation experience) | Later | All | Shopfront management UX review | 0 | |||||||||||||||
98 | Make what we have great | Shopfront management | Hubs managers can choose the adapted weight and measure units for their shops given their own local situation | 2018? | US | Hubs managers can choose the adapted weight and measure units for their shops given their own local situation | 1 | 1 | 1 | 3 | ||||||||||||
99 | Make what we have great | Shopfront management | Shops can require a minimum spend before customer can checkout | 2018 | All | FC? | Shops can require a minimum spend before customers can checkout | - Shops can set a minimum spend requirement so customer can't checkout with orders below this value. | 2 | 2 | 4 | |||||||||||
100 | Make what we have great | Shopfront management | Embedded shops work on mobile | 2018 | All | Embedded shops Phase 1 works on mobiles | - Embedded shops work on mobile | 1 | 1 |