Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
17 views42 pages

Implementing Agile: in Pizza Delivery App (HSMCS581)

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views42 pages

Implementing Agile: in Pizza Delivery App (HSMCS581)

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 42

IMPLEMENTING AGILE

In Pizza Delivery App

Humanities- II (Industrial Project Management) (HSMCS581)

Submitted In partial fulfilment for the Degree of

Bachelor of Technology
in
Department of Computer Science and Engineering

Submitted by

NAME ROLL NO. JOB ROLE

Tirthanka Saha 158 Product Owner

Tirtha Dutta 169 Scrum Master

Rajdeep Ghosh 168 Developer

Rajdeep Biswas 160 Developer

Debmalya Das 151 Developer

Bipasha Patra 152 Tester

Koustav Das 161 Tester

Sinchan Bibar 180 Tester

Under the Guidance of


Prof. Saikat Dutt

Institute of Engineering and Management

Salt Lake, Kolkata


Index
Page

Acknowledgement

About the Website

Product Backlog

Sprint Planning

Sprint 1 & Sprint 2

Issue Log

Burndown Chart

Kanban Board

Retrospective Analysis

Agile vs Waterfall
Acknowledgement
I wish to express my heartfelt gratitude to the all the people who have
played a crucial role in the research for this project, without their active
cooperation the preparation of this project could not have been completed
within the specified time limit.
I am thankful to my project guide Prof. Saikat Dutt who supported me
throughout this project with utmost cooperation and patience and for
helping me in doing this Project.
I am also thankful to our respected Head of the Department, Prof. Dr.
Moutushi Singh, for motivating me to complete this project with complete
focus and attention.
I am thankful to my department and all my teachers for the help and
guidance provided for this work.
I extend my sincere thanks to my institute, the Institute of Engineering and
Management, Kolkata for the opportunity provided to me for the betterment of
my academics.

Date: November 13,2024


Place: IEM (Salt Lake Campus, Kolkata)

Tirthanka Saha Tirtha Dutta


_
(Product Owner) (Scrum Master)

Rajdeep Ghosh Rajdeep Biswas


_
(Developer) (Developer)

Debmalya Das Bipasha Patra


_
(Developer) (Tester)

Koustav Das Sinchan Bibar


_
(Tester) (Tester)
About the Website

“PIZZAMANIA” is more than just a pizza delivery service; it's a culinary


journey that brings the authentic taste to your doorstep. With a commitment
to quality, speed, and customer satisfaction, we've redefined the pizza
delivery experience.

The one-stop shop for delicious, piping-hot pizza delivered right to the door.
We're passionate about crafting pizzas that tantalize everyone’s taste buds.
From classic favorites to innovative creations, our menu offers something
for everyone.

Page User Interface

Sign Up Page

Log In Page

Home Page

Menu Page
Order Online Page

Reservations Page

Location & Hours Page

Cart
Product Backlog

The product backlog for our pizza delivery app “PIZZAMANIA” is a prioritized list
of features and tasks that need to be completed to develop and maintain the app. It
serves as a roadmap for the development team, outlining the work to be done and
the order in which it should be tackled.

Here's breakdown of items that are included in our pizza delivery app's product
backlog:
Sprint Planning
1 Implementable User Story Estimate = 89

Description As an admin, customer, or Tasks


delivery personnel, I want → Design and
to be able to log in to the implement a login
PizzaMania platform, so interface for each
that I can access my user role.
respective dashboard and → Develop
perform my tasks authentication and
session management
logic.
→Redirect each user
role to their specific
dashboard post-login.
→Add error handling
for incorrect login
attempts.
→Test login
functionality for each
role.

Acceptance - The new user should


Criteria have access to a
registration page.
- The system should
require essential details
such as name, email,
phone number, and
password.
- Passwords should be
encrypted for security.
- The user should receive
a confirmation email upon
successful registration.
- The user should be
redirected to the login
page after registration.

Note -None
2 Implementable_User Estimate = 55
Story

Description As a new user, I want to Tasks → Design and


have the option to implement a registration
create an account on form that captures
PizzaMania, so that I necessary details (name,
can save my details email, phone number,
and manage my orders. password).→ Implement
form validation and error
handling.→ Set up
backend to securely store
user information and
encrypt passwords.→
Send a confirmation
email upon successful
registration.
→ Redirect users to the
login page after
registration.

Acceptance - The user should see a


Criteria registration form with
fields for name, email,
phone_number,and
password.
- Passwords must be encrypted
for security.
- The system should send a
confirmation email upon
successful registration.
- The user should be redirected
to the login page after
registration.

Note -None
3 Implementable User Estimate = 21
Story

Description As a user, I want to be Tasks


able to explore pizzas →Design a menu
and side dishes on the interface displaying
menu, so that I can all available pizzas
decide what to order. and side dishes.
→ Implement a filter
option for sorting
items by category
(e.g., pizza, sides,
drinks).
→ Enable viewing of
item details, including
ingredients, price,
and image.
→Test the menu
navigation for
usability.

Acceptance -The user should see a


Criteria list of pizzas and side
dishes
- Each item should
display an image, price,
and description.
- The user should be
able to filter items by
category.
- The menu should load
quickly and be easy to
navigate.

Note -None
4 Implementable User Estimate = 34
Story

Description As a user, I want to be Tasks


able to sort pizzas by → Implement sorting
price, so that I can view functionality
options within my on the menu page by
budget. price (low to high,
high to low).
→ Add price filters to
narrow down results.
→ Test sorting
accuracy and user
experience.

Acceptance -The user should see a


Criteria list of pizzas and side
dishes- Each item
should display an image,
price, and description.-
The user should be able
to filter items by
category.- The menu
should load quickly and
be easy to navigate.

Note -None
5 Implementable User Estimate = 21
Story

Description As a user, I want to be Tasks


able to personalize pizzas → Design a
with different toppings customization
and sizes, so that I can interface for pizzas,
create my ideal pizza. allowing users to
select size and
add/remove
toppings.
→ Implement price
adjustments based on
selected options.
→ Ensure the
customization is
reflected in
the cart and order
summary.
→Test the
customization flow
for each
available option.

Acceptance - The user should see


Criteria options to select pizza
size and add/remove
toppings.
- The total price should
adjust according to the
selected size and
toppings.
- Customized pizzas
should be saved correctly
in the cart

Note -None
6 Implementable User Estimate = 13
Story

Description As a user, I want to be Tasks


able to add products to → Implement "Add to
my shopping cart, so that Cart" functionality
I can proceed to for each menu item.
checkout with selected → Design a cart
items. interface that lists
added items and
their prices.
→ Ensure the cart
updates in real time
as items are added or
removed.
→ Test adding and
removing items for
accuracy.

Acceptance - The user should see an


Criteria "Add to Cart" option for
each item.
- Items should appear in
the cart with correct
details and prices.
- The cart should update
accurately when items
are added or removed.

Note -None
7 Implementable User Story Estimate=5

Description As a user, I want to be able Tasks


to view a summary of the → Design a cart
items in my cart, so that I summary interface
can review my order before showing item names,
proceeding to checkout. quantities, prices, and
total cost.
→ Implement
functionality to
update quantities and
remove items.
→ Ensure cart details
persist across page
refreshes.
→ Test the cart
summary view for
accuracy.

Acceptance - The user should see a cart


Criteria summary page listing
all items with prices and
total cost.
- The user should be able to
update item
quantities and remove
items.
- Changes should reflect
immediately in the cart
total.

Note -None
8 Implementable User Estimate=8
Story

Description As a user, I want to be Tasks


able to update the → Implement
contents of my cart, so functionality to
that I can adjust my order modify item
as needed before quantities in the
checkout. cart.
→ Allow users to
delete items from
the cart.
→ Ensure the cart
total updates
correctly with each
modification.
→ Test cart update
functionality for
different scenarios.

Acceptance - The user should be able


Criteria to increase or decrease
item quantities in the
cart.- The user should be
able to remove items
from the cart.- Cart total
should reflect changes
accurately.

Note -None
9 Implementable User Estimate=21
Story

Description As a user, I want to be Tasks


able to apply discount → Create an input
codes during checkout, so field for users to
that I can reduce the total enter discount codes
cost of my order if I have at checkout.
a valid code. → Validate discount
codes and apply
discounts if valid.
→ Display the
discounted price in
the order summary.
→ Test discount code
functionality for
different scenarios.

Acceptance - The user should be able


Criteria to enter a discount code
at checkout.
- Valid codes should
apply a discount and
adjust the total price.
- An error message should
appear for invalid codes.

Note -None
10 Implementable User Estimate=2
Story

Description As a user, I want to be Tasks


able to select a → Design a payment
payment method selection interface at
(either Cash or Online), checkout.
so that I can complete → Implement
my order with my functionality for
preferred payment selecting either Cash
option. or Online payment.
→ Ensure payment
selection reflects
accurately in the
order summary.
→ Test the payment
selection for both
options.

Acceptance - The user should see


Criteria options to select Cash
or Online as the
payment method.
- The selected payment
method should be
reflected in the order
summary.
- Payment options
should function
correctly for each
choice.

Note -None
11 Implementable User Estimate=89
Story

Description As a user, I want to be Tasks


able to monitor my → Design an order
order status in real status tracking
time, so that I know interface showing the
when my order will be current stage (e.g..
delivered. preparing, out for
delivery).
→ Implement backend
logic to update the
order status as it
progresses.
→ Enable real-time
status updates for
users.
→ Test tracking
functionality for
various order
scenarios.

Acceptance - The user should see an


Criteria order status page with
real-time updates.
- The status should
progress through stages
until delivery.
- Updates should be
reliable and timely.

Note -None
12 Implementable User Estimate=13
Story

Description As a user, I want to be Tasks


able to access the → Display the
location and image of location of the
the pizza outlet, so that nearest pizza outlet
I can know where my on the map.
order is coming from. → Show an image of
the pizza outlet on
the order
confirmation page.
→ Implement
backend logic to
retrieve outlet
location and
image data.
→ Test the location
and image retrieval
for various
scenarios.

Acceptance - The user should see


Criteria the location of the
nearest pizza outlet on
a map.
- An image of the
outlet should appear
on the order
confirmation page.
- Data should load
accurately for each
order.

Note -None
13 Implementable User Estimate=13
Story

Description As a user, I want to be Tasks → Implement a


able to search for review search feature
reviews of existing for restaurants in the
restaurants, so that I area.→ Design an
can make an informed interface to display
choice about where to restaurant ratings
order. and user reviews.→
Integrate sorting
options for highest
and lowest-rated
reviews.→ Test the
review search
functionality for
various queries.

Acceptance - The user should see a


Criteria search bar to look up
restaurant reviews.
- The user should be
able to sort reviews by
rating.
- Reviews should load
quickly and display
accurately.

Note -None
14 Implementable User Estimate=21
Story

Description As a user, I want to be Tasks


able to rate and review → Design a rating and
the pizza I ordered, so review interface
that I can share my post-delivery.
feedback with other → Implement
customers. backend logic to
store ratings and
reviews.
→ Display customer
reviews on the
product page for
each item.
→ Test the review
submission and
display functionality.

Acceptance - The user should be


Criteria able to rate and write a
review for the order.
- Reviews should
display under the
relevant product on the
menu.
- Ratings and reviews
should be stored
accurately in the
system.

Note -None
15 Implementable User Estimate=34
Story

Description As an admin, I want to be Tasks


able to manage menu → Develop a menu
items, so that I can add, management
update, or remove items interface for admin
as needed. use.
→ Implement
functionality to add,
update, and delete
menu items.
→ Ensure updated
items reflect
immediately on the
customer side.
→ Test the menu
management
features for different
scenarios.

Acceptance - The admin should be


Criteria able to add, edit, or
delete menu items.
- Changes made by the
admin should update on
the customer side
instantly.
- Menu updates should
be secure and reliable.

Note -None
16 Implementable User Estimate =21
Story

Description As a user, I want to Tasks


be able to cancel my →Implement a
order so that I have cancellation option
flexibility if I change for orders.
my mind. →Ensure proper
validation to confirm
the cancellation.
→Update order
status to "Canceled"
after confirmation.
→Add notifications to
inform users of
cancellation.

Acceptance Criteria - Users can cancel an


order before it
reaches a certain
processing stage.
- The system should
display a cancellation
confirmation.
- The order status
should update as
"Canceled."

Note -None
17 Implementable User
Story Estimate =5

Description As a user, I want to Tasks


receive a cancellation →Integrate SMS
confirmation through notification service.
SMS to confirm my →Ensure SMS is sent
order cancellation. upon order
cancellation.
→Log SMS delivery
for tracking.

Acceptance Criteria - Users receive an


SMS confirmation
when an order is
canceled.
- The SMS should
include details such
as order ID and
cancellation status.

Note -None
18 Implementable User
Story Estimate =21

Description As a user, I want to Tasks


receive a refund for →Implement refund
canceled orders via functionality for
online banking so online payments.
that I am →integrate with
compensated for banking API for
canceled orders. refunds.
→Notify users once
the refund is
processed.

Acceptance Criteria - Refunds should be


issued for eligible
canceled orders.
- Users should be
notified when the
refund is processed.
- Refund status
should be trackable.

Note -None
19 Implementable User
Story Estimate =13

Description As a user, I want to Tasks


be able to view the →Display delivery
details of the delivery person's name, photo
person, so I feel and contact details.
secure about who is →Update delivery
delivering my order. person details in
real-time on order
tracking.

Acceptance Criteria - Users can view


details of the
assigned delivery
person.
- Details are
accessible only after
the order is
dispatched.

Note -None
20 Implementable User
Story Estimate =5

Description As a user, I want to Tasks


be able to change my →Enable address
delivery address after change functionality
placing an order, in before order
case I made an error. dispatch.
→Validate new
address; notify the
delivery person of
address change if
already assigned.

Acceptance Criteria - Users can change


delivery addresses
before the order is
dispatched.
- System should
validate and confirm
the updated address..

Note -None
21 Implementable User
Story Estimate =3

Description As a user, I want to Tasks


leave ratings and →Develop a rating
reviews for pizzas, so and review system.
others can make →Display average
informed choices. ratings on product
pages.
→Moderate reviews
for inappropriate
content.

Acceptance Criteria - Users can rate and


leave reviews for
products.
- Reviews are
displayed on the
product page.

Note -None
22 Implementable User
Story Estimate =8

Description As a user, I want to Tasks


be able to rate the →Add rating system
delivery service to for delivery service.
provide feedback on →Link ratings to
delivery experiences. individual delivery
personnel.
→Ensure ratings
appear only after
delivery completion.

Acceptance Criteria - Users can rate


delivery service after
order completion.
- Ratings are visible
to the admin for
performance
tracking.

Note -None
23 Implementable User
Story Estimate =34

Description As a user, I want to Tasks


be able to save →Implement the
favorite orders for "Save Favorite"
easy reference in the feature on orders.
future. →Allow users to view
and reorder favorite
items.
→Create a dedicated
section for saved
favorites.

Acceptance Criteria - Users can save


orders as favorites.
- Saved orders are
easily accessible for
reordering.

Note -None
24 Implementable User
Story Estimate =21

Description As a user, I want to Tasks


receive suggestions →Implement
for new pizza flavors recommendation
based on past orders engine based on
so I can try order history.
something similar. →Display
personalized
suggestions on the
home page.
→Regularly update
suggestions based
on user data.

Acceptance Criteria - Users receive pizza


suggestions based
on past preferences.
- Suggestions are
relevant and updated
regularly.

Note -None
25 Implementable User
Story Estimate =13

Description As a user, I want to Tasks


be able to ask →Implement a
questions via a chatbot feature for
chatbot for any customer inquiries.
order-related →Ensure real-time
inquiries. responses for
common queries.
→Escalate complex
issues to human
support.

Acceptance Criteria - Users can interact


with a chatbot for
assistance.
- Chatbot provides
relevant responses
for common queries.

Note -None
26 Implementable User
Story Estimate =21

Description As an admin, I want Tasks


the ability to update →Build interface for
menu options, so the menu updates.
menu remains →Allow admins to
current. add/remove items
and update prices.
→Ensure real-time
menu updates across
platforms.

Acceptance Criteria - Admins can update


the menu through a
dedicated interface.
- Menu changes are
reflected instantly for users.

Note -None
27 Implementable User
Story Estimate =5

Description As an admin, I want Tasks


to modify item prices →Create price update
to maintain profit functionality in the
margins. admin panel.
→Reflect price
updates immediately
on the user side.
→Ensure pricing
changes are recorded
in the system log.

Acceptance Criteria - Admins can modify item


prices.
- Price changes are
instantly updated across
the platform.

Note -None
28 Implementable User
Story Estimate =3

Description As an admin, I want Tasks


to be able to view →Enable order
customers' past history access for
orders to improve admins.
service. →Display details
such as date, items,
and total cost.
→Ensure data
privacy and access
control.

Acceptance Criteria - Admins can view


customer order
histories.
- Order data is displayed
accurately and securely.

Note -None
29 Implementable User
Story Estimate =2

Description As an admin, I want Tasks


to view customer →Create a feedback
feedback and reviews review interface for
to monitor admins.
satisfaction. →Sort feedback by
date and rating;
enable response
option for user
feedback.

Acceptance Criteria - Admins can access


and respond to
customer feedback.
- Feedback is
organized by
relevance.

Note -None
30 Implementable User
Story Estimate =55

Description As an admin, I want Tasks


to generate a sales →Design report
summary report so generation system
that I can track for sales data.
revenue and →Include filters for
performance. date range, item
category, and user
type.
→Generate
downloadable reports
in multiple formats.

Acceptance Criteria - Admins can


generate detailed
sales summary
reports.
- Reports include
accurate sales data and
are exportable.

Note -None
Sprint 1 & Sprint 2

The sprint backlog for our pizza delivery app “PIZZAMANIA” is a prioritized list of
tasks that our development team plans to complete within a specific sprint (2-4
weeks). It's derived from the overall product backlog, which contains all the
features and improvements needed for the website.

Here's the sprint backlog for our pizza delivery app:


Issue Log

The issue log for our pizza delivery app “PIZZAMANIA” is a centralized repository
where all reported problems, bugs, and feature requests related to the website are
documented, tracked, and resolved. It helps in maintaining transparency,
accountability, and efficient issue resolution within the development and support
teams.

Here's the issue log entries for our pizza delivery app:
Burndown Chart
Kanban Board
Retrospective Analysis
Agile vs Waterfall

Feature Agile Waterfall


Approach Iterative and incremental Sequential and linear
Planning Flexible and adaptive Detailed upfront planning
Requirements Evolving and changing Rigid and fixed
Team Roles Cross-functional and Specialized roles
collaborative
Customer Involvement Continuous and frequent Limited involvement
Delivery Frequent, small releases Single, large delivery
Risk Management Continuous risk Risk assessment upfront
assessment and
mitigation
Flexibility Adaptable to changes Less flexible to changes

For our pizza delivery app “PIZZAMANIA”, an Agile approach is generally more
suitable due to the following reasons:
• Rapid Time to Market: Agile allows for faster delivery of the app, enabling
quick entry into the market.

• Adaptability to Changing Requirements: Customer preferences and market


trends can change rapidly. Agile allows for easy adaptation to these changes.

• Continuous Improvement: Regular feedback and iterations help refine the


app and improve user experience.

• Reduced Risk of Project Failure: Agile's iterative approach minimizes the


risk of building a product that doesn't meet user needs.

You might also like