Scribd
Upload
5 views

Scrum_Estimation_Case_Study

This case study provides students with hands-on experience in Scrum estimation techniques using story points and Planning Poker for a hotel reservation system. Students will estimate story points for various user stories based on complexity, effort, and uncertainty, while working in small groups to reach a consensus. The document includes user stories, suggested story points, and an explanation of the Planning Poker technique to facilitate collaboration and accurate estimation.

Uploaded by

umairalih6
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
5 views

Scrum_Estimation_Case_Study

This case study provides students with hands-on experience in Scrum estimation techniques using story points and Planning Poker for a hotel reservation system. Students will estimate story points for various user stories based on complexity, effort, and uncertainty, while working in small groups to reach a consensus. The document includes user stories, suggested story points, and an explanation of the Planning Poker technique to facilitate collaboration and accurate estimation.

Uploaded by

umairalih6
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Scrum Estimation Case Study: Hotel Reservation System

Introduction
This case study exercise is designed to give students hands-on experience with Scrum
estimation techniques, specifically using story points and Planning Poker. The case study
presents a backlog for a hotel reservation system, and students are asked to estimate story
points for each item based on complexity, effort, and uncertainty.

Case Study: Hotel Reservation System


A small hotel wants to implement an online reservation system that will allow guests to
book, cancel, and modify reservations. The system will also enable hotel employees to run
reports on occupancy and revenue. As part of the team developing this system, students will
work to estimate story points for different user stories in the product backlog.

Objective
The objective is to help students practice calculating story points based on the complexity,
effort, and potential unknowns associated with each task.

Instructions
1. Divide the students into small groups (4–5 students per group).

2. Present the user stories for the hotel reservation system (provided below).

3. Each group will discuss each story and assign story points based on the following factors:
- Complexity: How difficult is the story to implement?
- Effort: How much work is involved in completing the story?
- Uncertainty: Are there unknowns or risks that could complicate the story?

4. Each group should use Planning Poker or an agreed estimation method to reach a
consensus on the story points for each story.

5. Once the groups have assigned story points to each story, they will present their
reasoning to the class.

User Stories
 User Story 1: As a guest, I want to be able to make a reservation online, so that I can
book a room at the hotel.
 User Story 2: As a guest, I want to cancel my reservation up to 24 hours before check-in,
so that I have flexibility in my travel plans.
 User Story 3: As a guest, I want to modify the dates of my reservation, so that I can
adjust my booking if my plans change.
 User Story 4: As a hotel employee, I want to be able to run a report on room occupancy,
so I can see how many rooms are booked at any given time.
 User Story 5: As a hotel manager, I want to run revenue-per-available-room (RevPAR)
reports to track financial performance.
 User Story 6: As a guest, I want to receive an email confirmation after making a
reservation, so that I have a record of my booking.
 User Story 7: As a hotel administrator, I want to improve error handling in the system,
so that it provides meaningful feedback if something goes wrong.
 User Story 8: As a guest, I want to view available rooms and prices without logging in, so
that I can quickly decide if the hotel fits my budget.

Suggested Solution Guide (for Instructor Reference)


User Story Suggested Story Points Reasoning

Make a reservation online 5 Moderate complexity with


UI design, database
integration, and payment
processing.

Cancel a reservation 3 Lower complexity, but


requires updates to
availability and refund
processing.

Modify reservation dates 5 Complexity due to checking


room availability, updating
reservation, and potentially
adjusting pricing.

Run room occupancy report 8 Requires data processing,


filtering options, and
creating a report interface.

Run RevPAR report 13 High complexity with


financial data integration
and secure access.

Email confirmation for 3 Simple functionality but


reservation needs email integration.

Improve error handling 8 Complexity in adding


meaningful feedback for
various scenarios; requires
system-wide updates.

View available rooms and 5 Moderate complexity with


prices without logging in guest access to room
availability and dynamic
pricing.

Explanation of Planning Poker


Planning Poker is an Agile estimation technique used by Scrum teams to assign story points
to backlog items. It encourages team members to discuss the complexity, risk, and effort of
each task. Here’s how it works:

1. Team members review the user story and consider its complexity, risk, and effort
required.

2. Each team member secretly selects a story point estimate (e.g., using the Fibonacci
sequence: 1, 2, 3, 5, 8, etc.).

3. All estimates are revealed at once, and if there’s a difference, the team discusses their
reasoning.

4. The team repeats the process until they reach a consensus on the story points.

Planning Poker fosters collaboration, encourages team discussion, and helps the team arrive
at accurate estimates by considering multiple perspectives. By discussing different
estimates, teams can uncover hidden complexities or risks in the tasks and make better-
informed decisions on effort and timeline.

You might also like