This is a set of initial User Stories for a new restaurant reservation system. Assume this is a large restaurant and the host can’t just look around to see all the open tables. If you would like to...

The second individual part will be graded. This will be your own personal reflections on the exercise. See the attached Document.


This is a set of initial User Stories for a new restaurant reservation system. Assume this is a large restaurant and the host can’t just look around to see all the open tables. If you would like to use one of your individual business cases instead of this, you may do so as long as everyone agrees. But stick to about the same number of User Stories. Part 1 – Planning Poker Group Activity Your job as a team is to go through a Planning Poker exercise on Zoom (or similar tool) to reach a consensus on the relative level of effort for each story. If you decide some of them are Epics, make note of this but you don’t need to decompose these into more stories for separate story point estimates. Remember that each story estimate needs to address EVERYTHING needed to get to “done” – input/UX design, data base, page/program coding, test case design and FULL testing (integration and UAT not just basic unit testing). Each person should have some planning poker “cards” when you start. There are two options you can print and cut out at the end of this document. Or, keep it simple and just write down the Story Point numbers on a sheet of paper or index card to show to your team members. Display them all simultaneously – just like in a “real” planning poker session. Discuss differences, re-evaluate, and go through the display of “cards” again until you have a consensus for EACH story. US1: Check the wait for a table As a hungry person, I want to find out when a table will be available so I can decide if the wait is too long US2: Make a reservation As a future diner guest, I want to reserve a table for my party in advance, so we do not have to stand in line to eat. US3: Seating reservation diners As the restaurant host, I want to be able to confirm table reservations so I can seat reserved dining guests at their table quickly US4: Seating walk-in diners As the restaurant host, I want to know which tables are not already reserved so I I can seat walk-in diners at an available table. US5: Check reservation demand As the restaurant manager, I want to know trends in walk-in dining and dining reservations so I can adjust staffing or open hours based on typical demand. US7: Manage table availability As the restaurant manager I want to set the number of reservable tables for my restaurant so I can allow for some walk-in business and VIPs US8: Acknowledge customer leaving As the restaurant host, I want to know when diners leave so I can offer the table to another party. Part 2: Planning Poker Individual assessment After your planning poker session, each of you should write about the experience. THIS is what you will turn in for this week. Address the following items: 1. The basics: What were your group’s final Story Point estimates, and how long did it take for you to finish the exercise? 2. Group dynamics: Did your thinking about the details of the stories evolve as you discussed them as a group? Did you find stories that could be considered epics? How did the group handle different perspectives on the stories? 3. Personal Insights: Compare your initial Story Point estimates to the final group consensus. Did you tend to start with lower or higher Story Points than the others? Did this change as you went through the exercise? What did you learn about how you estimate? 4. Project Management insights: How would you compare this approach to the time/effort estimates you might do for a Traditional project? Which do you think is more effective? NOTE: The rubric for this week will not include tools and techniques, but will look at depth of thought in these items instead. ? XXL XL M S L XS Radhika Sesha2 3 40 20 13 8 5 1