For the case below do the following:

1. Write 30 user stories
2. Point the user stories
3. Place the user stories into six sprints so that they are close to equal in size (points-wise)
4. Use the attached Scrum Roadmap Template for this assignment

   Case

   Develop an integrated, multi-user App for Hospitality Industry

   Requirements:

   Develop a purchase/order platform and mobile app for catering companies that can be used for ordering quickly and efficiently.

   Make sure the ordering process from the catalog to invoicing is automated. Allow the buyer to make the order with a smartphone.

   Desired features:

1. The app must contain an option for the end-user to create a catalog of the products.

2. The user can add products to a sort of order list with the app (its own private catalog of frequently purchased items)
3. The user can take a photo of the product and relevant information such as: Add product information (such as choosing a supplier to choose from a list or add a new one), Product Code of Supplier, etc.
4. The supplier can add or import a custom product catalog from the existing ERP system on the platform.
5. The suppliers catalog is visible to end-users who add the vendor to their own list of vendors.
6. The vendor may invite end-users to download the app
7. Products from the supplier's catalog can be added to the private user's private catalog.
8. In the web application, the supplier can log in to manage their own catalog.
9. In the web application, delivery terms can be added by the supplier and may be what they are by the end-user (cafe or restaurant).
10. In the mobile app, the end-user can place an order by checking in the catalog the products to be ordered and the quantity (loose or in packing units)
11. The status of the order is visible in both the mobile app and the web application
12. The supplier has a simple 'order management system' available from which it is possible to manage an order (mini order management system). For example, if a product is out of stock, it can be communicated with the end-user, etc.
13. Provides an option to select barcode scanner products.
14. Send an e-invoice once an order has been placed and paid. An e-invoice consists of an e-mail with a pdf attachment
15. Provides the buyer with multiple options to pay directly online and pay on account.
16. Provides the buyer with a summary of purchase invoices.
17. Provides the supplier with an overview of all sales and sales invoices.
18. Provides the supplier with an efficient solution for processing invoices.
19. Offered products can be added to the supplier's catalog. These products are prominently visible.
20. In the supplier's catalog, the products that buyers often order are first visible.
21. The catalog has an 'explore' mode in which the buyer can "browse" for inspiration
22. The catalog has a search/filter function so you can sort products by group
23. The buyer/end user's catalog has labels. Labels can be added and managed by the buyer itself
24. The app has a message board where messages can be sent to connected vendors.
25. The supplier will receive an email with a link to the web application to answer the question. The buyer can also request a call me back request to call back the supplier (if this is set/activated by the supplier)
26. Also, important: the buyer can Invite the supplier to use the platform.
27. On the platform, an order list template can be created for a supplier by the buyer. This template is used to place the order with a vendor if there is no link with an ERP system
28. The supplier then receives an email or fax from the order that the buyer has made. This is sent from the system.
29. As a supplier "enters" he/she gets access to a backend system where the orders can be viewed per customer (this is the order management system)
30. Create your own user story based on the requirements above.

Read: https://blog.crisp.se/2008/02/12/mattiasskarin/1202847600000

User Stories Point the User Stories Scrum Sprints Sprint Sprint Sprint Sprint Sprint Sprint | 2 3 4 5 6 User story User story User story User story User story User story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story User Story Introduction A scrum product roadmap is an organization of the user stories and the sprints that will be used to create a product. After all the user stories are written and pointed the development team decides how to divide the stories between the sprints. A sprint is like a two-week mini project. A team will decide how many points they will be able to complete in each two-week sprint. They will then decide the order in which the stories will need to be completed. The stories will be divided along however many sprints the team thinks it will need. This set of sprints becomes the roadmap. Knowledge A visual representation of a roadmap would look like this: Sprint 1 Sprint 2 Sprint 3 Sprint 4 Save address Payment Sales report Login Import address Forum Order tracking Order form Upload photo Member bonus Logout Invite friend Email ordering Chat support A product owner will create the vision for a product. The product roadmap is the plan that the development team will use in order to bring that vision into reality. Key Points to Remember Sprints are like small two-week projects. Roadmaps show the vision of the development of a product. Test Your Knowledge Click on the next page to complete the assignment that summarizes user stories, epics, story pointing, sprints, and roadmaps