This document outlines the sprints and epics planned for a restaurant management system over three sprints from July 6 to August 13, 2015. Sprint 1 focuses on account, organization, and data creation. Epics include order creation, queue and delivery, and completion. Sprint 2 adds user creation, roles, and permissions. New features include delivery options and time tracking. Sprint 3 covers menu, restaurant, and inventory management. Reporting is added at the outlet and chain level. Complex items like raw material adjustment are deferred due to time constraints.

1. Sprint Plans
Time Period: July 6, 2015 – August 13, 2015
Sprint Duration: 2 weeks
Sprint 1
 Account creation
 Org creation
 Object and schema creation
 Dummy Data population
Epic 1: Order creation
1. as a customer: I should be able to browse through the menu and look at the various food
options available in the restaurant along with the price for each item.
2. as a customer: I should be able to select items from the menu and add them to my cart/order.
3. as a customer: I should have cart containing all the chosen items so far, accessible all the
time.
4. as a customer: I should be able to remove items from my cart or increase item count.
5. as a customer: I should be able to cancel my entire order.
6. as a customer: I should be able to view the itemized bill for my order along with the prices
for each item and the tax applied.
Epic 2: Order queue and delivery
1. as a chef: I should be able to view the current queue of orders.
2. as a chef: I should be able to accept the orders.
3. as a chef: I should be able to update the order status to ready once the order is prepared.
4. as a restaurant manager: I should be able to view the current queue of orders (in read-only
mode).
5. As an Order Manager: I should be able to view the current queue of orders (in read-only
mode).
6. as a waiter: I should be able to view the current order queue to see the ready orders for pick
up.
7. as a waiter: I should be able to mark the order as picked up on the common queue.

2. Sprint 2
 User creation
 Roles creation
 permissions
1. as a customer: I should be able to see the approximate delivery time.
2. as a customer: I should be able to see top selling items in the restaurant while choosing my
order items.
Epic 3: Order Completion
1. as a waiter: I should be able to mark the order as complete once the customer has finished
ordering.
2. as a customer: I should have an option for providing the tip after my order has been billed.
3. as a customer: I should be able to provide feedback for the service and the food.
4. as a waiter: I should be able to take payment from the customer and thus mark the order as
paid.
Epic 4: Table Management
1. as a front desk manager: I should be able to update the status of the tables in the restaurant
viz. cleaning, ready, and occupied.
2. as a front desk manager: I should be able to assign appropriate table to the customers
depending on the table availability and number of guests.
New Added Functionalities:
1. Filter for veg/non-veg items
2. Sort items according to the order in which they are placed
3. Special Offers and Bill to be fixed to screen
4. On load of the chef and waiter page get orders
5. Add delivery option to each of the items in the cart
6. Time capture on pick up & delivery
7. User interface change for Cart
8. On order modification change the order queue on chef screen

3. Sprint 3
Epic 5: Menu Management
1. as a restaurant manager: I should be able to modify the menu items, add new items, delete
items, and update descriptions.
2. as a higher management member: I should be able to view the restaurant wise menu.
Epic 6: Manage restaurant information
1. as a management member: I should be able to add, delete and update the information about
various restaurants.
2. as a restaurant manager: I should be able to update information about my restaurant.
Epic 7: Reporting per outlet
1. as a restaurant manager: I should be able to view weekly sales for my outlet.
2. as a restaurant manager: I should be able to view monthly sales for my outlet.
3. as a restaurant manager: I should be able to view quarter wise sales for my outlet.
4. as a restaurant manager: I should be able to view annual sales for my outlet.
5. as a restaurant manager: I should be able to view the most popular items ordered by the
customers, average bill and least popular items for further actions in menu management.
Epic 8: Reporting for chain
1. as a member of higher management: I should be able to view restaurant wise weekly sales.
2. as a member of higher management: I should be able to view restaurant wise monthly sales.
3. as a member of higher management: I should be able to view restaurant wise quarterly
sales.
4. as a member of higher management: I should be able to view the overall annual sales of
the restaurant.
5. as a restaurant manager: I should be able to view the most popular items ordered by the
customers, average bill and least popular items for further actions in menu management
across the chain as well as per restaurant.
Epic 9: Inventory Management for restaurant
1. as a restaurant manager: I should be able to view the current inventory position of the
restaurant.
2. as a restaurant manager: I should be able to update the inventory items.
3. as a restaurant manager: I should be able to view the forecast of items in the inventory to
be replenished.

4. ---------------------------------------------------------------------------------------------
NOTE:
1. Introduced the table management as discussed in the call in Sprint 2.
2. We have planned to show the ordered items on the kitchen screen not as per category due
to the complexity involved and the time restrictions. Instead each ordered item would be
displayed separately on the kitchen screen with its associated attributes. The kitchen staff
will accept and prepare orders according to their assigned areas.
3. Raw material reduction from inventory: We have a dine-in service where the items in the
menu have ingredients which can be altered according to the customer’s choice. For
example, a customer may not want mushrooms and corn in a particular dish, and may be
something else. Capturing this real time data and then implementing the raw material
reduction feature is very complex and we cannot incorporate this due to our time restriction.
We have all our sprints planned according to the time given to us. Also our internship
duration has been preponed by a week i.e. it ends on Aug 14, 2015. So keeping in mind the
time and complexity involved in the item that we discussed regarding the Raw Material
reduction according to the items that are ordered, we do not think it would be feasible to
accommodate that item in any of our sprints according to our current plan. But if we finish
off the committed features well before time then we will move ahead with implementing
this item.