Scrum
Scenario: Launching a New Mobile App for Food Delivery
Background:
Your team is tasked with building a new mobile app for food delivery. The goal is to deliver an MVP (Minimum Viable Product) that allows users
to browse restaurants, place orders, and track delivery.
1. Product Owner
Imagine you have a Product Owner who represents the stakeholders (e.g., restaurant owners, customers, delivery companies). The Product
Owner’s role is to define what features are important and prioritize them. They create the Product Backlog, a list of all features, bug fixes, and
enhancements for the app.
In this case, the Product Owner prioritizes features like:
Restaurant browsing
Food ordering
Order tracking
2. Scrum Master
A Scrum Master is responsible for ensuring the Scrum process is followed. They help remove any obstacles the team faces. For example, if
the team is stuck on a technical issue like integrating payment gateways, the Scrum Master will help resolve the problem, possibly by finding
experts or allocating resources.
3. Development Team
The Development Team includes developers, designers, and testers. They are self-organizing, meaning they decide how to best complete the
tasks assigned for each sprint.
How Scrum Works in This Scenario:
Sprint Planning (Day 1 of the Sprint)
At the start of each sprint (a short, time-boxed period of 1-4 weeks), the team sits down with the Product Owner to plan what can be
accomplished. Let’s say the team is in a 2-week sprint. They look at the Product Backlog and choose tasks they can finish in that time,
moving them to the Sprint Backlog.
For this sprint, the team decides to:
Implement a restaurant browsing feature
Create a basic ordering flow
Add a prototype for order tracking
Daily Standups (Every Day)
Every morning, the team holds a Daily Scrum (or standup) meeting for about 15 minutes. Each member answers:
What did I work on yesterday?
What will I work on today?
Are there any blockers?
For instance, one developer might say, "Yesterday, I integrated the menu system; today I’m working on the payment API. I’m blocked because I
need the credentials from the payment service."
Sprint Work (During the Sprint)
During the sprint, the team works on the tasks, constantly communicating and collaborating. If they face any issues, they can bring them up
with the Scrum Master or Product Owner. For example, the team may discover a usability issue with the order tracking feature, so they adjust
their focus based on feedback.
Sprint Review (End of the Sprint)
At the end of the sprint, the team presents the working features to the Product Owner and stakeholders in a Sprint Review. In this case, the
team might demo:
The restaurant browsing feature
A rough but functional ordering flow
An early version of order tracking
The Product Owner gives feedback and discusses what should be improved or prioritized for the next sprint.
Sprint Retrospective (After the Sprint Review)
Once the sprint is complete, the team holds a Sprint Retrospective to reflect on the process. They discuss what went well, what didn’t, and
how to improve. Maybe they realize that they didn’t test the app enough, so they decide to focus more on testing in the next sprint.
Scrum Cycle
This process repeats for each sprint until the project is complete. With each sprint, the app becomes more refined, and new features are
added, leading to a fully functional mobile app.
Key Benefits of Scrum in This Scenario:
Adaptability: After each sprint, the Product Owner can adjust priorities based on customer feedback or market changes.
Transparency: The team regularly presents their progress to stakeholders, keeping everyone in the loop.
Continuous Improvement: Through retrospectives, the team continually refines their working methods, becoming more efficient over
time.
