Method of estimating story points: Relative Sizing
Consensus model: Pointing poker.
Sprint 1
Sprint duration: 2 weeks.
Sprint Theme
Onboarding Experience.
Sprint Goal:
To streamline and enhance the new user onboarding process, ensuring it is intuitive,
informative, and engaging, thereby increasing user retention and satisfaction.
This goal will focus on simplifying the initial user journey, providing clear guidance and support,
and ensuring new users can quickly understand and utilize the key features of our platform or
service effectively.
Sprint Objectives
Allow users to securely sign up using their username and password.
Allow users to securely log in using their username and password.
Enable users to leverage popular platforms (Google and Facebook) for quicker access via
OAuth.
Provide a straightforward process for users who have forgotten their passwords to recover
or reset them.
Offer users the option to save their login credentials for future sessions, reducing the need
to re-enter details.
Ensure users can easily and securely log out of their accounts when desired.
Sprint planning
Members present: Product owner, Scrum master, and Development team.
Total sprint points: 22
Time spent: 1hr 30mins.
Sprint backlog
1. [US-101] As a new user, I want to be able to sign up for an account, so that I can create a
personal profile and gain access to exclusive platform features.
Description: Before users can log in, they need an account. The signup process provides
potential users with a method to create their unique account on the platform, which they
can later access using their chosen credentials.
Sprint Points: 3
Definition of done:
There is a visible signup form, separate from the login form, or an easily accessible
link/button labeled "Sign Up" or "Create Account" on the login page.
The signup form requires essential information such as username, password, and a
valid email address.
Password requirements are clearly specified (e.g., a minimum length, the inclusion of
numbers/special characters, etc.).
Upon successfully completing the signup form, the user is either automatically
logged in or directed to the login page with a confirmation message.
If the chosen username or email is already in use, the system displays a clear error
message prompting the user to choose another.
2. [US-102] As a Registered user, I want to enter my username and password, so that I can
access my personal.
Description: Users need a way to access their personal accounts on the platform, and a login
functionality provides them with that access using their unique credentials.
Sprint Points: 5
Definition of done:
There is a visible login form with fields for entering a username and password.
After entering valid credentials and clicking the "Login" button, the user is redirected
to their personal account page.
If the username is not recognized, the system displays a message: "Username not
found."
If the username is recognized but the password is incorrect, the system displays a
message: "Incorrect password."
3. [US-103] As a user who has accounts on other platforms (Google and Facebook), I want to
use OAuth to sign up or log in with those accounts, so that I can quickly access the
platform without creating a new account or remembering another password.
Description: Many users prefer to use existing account credentials from platforms they trust,
like Google or Facebook, instead of creating new ones. OAuth integration provides this
capability.
Story Points: 5
Definition of done:
Below or next to the standard login and signup forms, there are buttons labeled
"Login with Google", "Login with Facebook", representing different OAuth providers.
Clicking on any of these buttons redirects the user to the chosen platform's OAuth
login page.
Once authenticated through the third-party platform, the user is redirected back to
the main platform and is logged in.
4. [US-104] As a returning user, I want to have an option to "Remember Me" when I log in so
that I don't have to enter my credentials every time I access the platform.
Description: Not all users want to enter their login details every time. A "Remember Me"
option gives them the convenience of staying logged in for future sessions.
Story Points: 2
Definition of done:
There is a checkbox labeled "Remember Me" below the password field on the login
form.
If the user checks this option and logs in, their login status persists even if they close
and reopen the browser.
If the user does not check this option, their login status does not persist beyond the
current session.
5. [US-105] As a user who has forgotten my password, I want to click on a "Forgot Password"
link, so that I can receive instructions on how to reset my password and regain access to
my account.
Description: Users can forget their passwords. Instead of locking them out permanently, a
recovery mechanism should be available. This mechanism would typically involve sending
instructions to their registered email.
Story Points: 5
Definition of done:
Below the login form, there is a clearly visible link labeled "Forgot Password?"
Clicking this link directs the user to a password recovery page.
The user is prompted to enter their registered email address.
Upon entering a valid email and submitting it, the system sends password reset
instructions to that email.
6. [US-106] As a logged-in user, I want to have a clear and accessible logout button, so that I
can securely log out of my account when I'm done.
Description: For security and privacy reasons, users should have the ability to log out of
their accounts when they choose to.
Sprint Points: 2
Definition of done:
On the user's personal account page or on the main navigation bar, there is a clearly
visible button or link labeled "Logout."
Clicking "Logout" immediately logs the user out and redirects them to the platform's
login page.
After logging out, the user's session data is cleared and they would need to re-enter
their credentials to access their personal account again (unless they used the
"Remember Me" option).
Daily Scrum
ID Jevelyn Gurpreet Devrashi
1 Next 24hrs: Will start US-101 Next 24hrs: Will start US-102 Next 24hrs: Will start US-
backend. backend. 103 backend.
2 Last 24hrs: Finished US-101 Last 24hrs: Finished US-102 Last 24hrs: Finished US-
backend. backend. 103 backend.
Next 24hrs: Resume work on Next 24hrs: Resume work on Next 24hrs: Resume work
US-101, start frontend US-102, start frontend designs on US-103, start frontend
designs and functionality. and functionality. designs and functionality.
3 Last 24hrs: Started frontend Last 24hrs: Started frontend Last 24hrs: Started
designs and functionality. designs and functionality. frontend designs and
Next 24hrs: Complete US-101 Next 24hrs: Complete US-102 functionality.
frontend and write unit tests. frontend and write unit tests. Next 24hrs: Complete US-
103 frontend and write
unit tests.
4 Last 24hrs: Wrote unit tests, Last 24hrs: Wrote unit tests, Last 24hrs: Wrote unit
Had bugs in implementation. Had bugs in implementation. tests, Had bugs in
Next 24hrs: Fix bugs and Next 24hrs: Fix bugs and close implementation.
close US-101. US-102. Next 24hrs: Fix bugs and
close US-103.
5 Last 24hrs: Wrote unit test. Last 24hrs: Wrote unit test. Last 24hrs: Wrote unit
Changes were requested Changes were requested test. Changes were
during code review. during code review. requested during code
Next 24hrs: Address code Next 24hrs: Address code review.
review feedback, Close US- review feedback, Close US- Next 24hrs: Address code
101. 102. review feedback, Close
US-103.
6 Last 24hrs: Closed US-101 Last 24hrs: Closed US-102 Last 24hrs: Closed US-103
Next 24hrs: Will start US-104 Next 24hrs: Will start US-105 Next 24hrs: Will start US-
backend. backend. 106 backend.
7 Last 24hrs: Finished US-104 Last 24hrs: Finished US-105 Last 24hrs: Finished US-
backend. backend. 106 backend.
Next 24hrs: Resume work on Next 24hrs: Resume work on Next 24hrs: Resume work
US-104, start frontend US-105, start frontend designs on US-106, start frontend
designs and functionality. and functionality. designs and functionality.
8 Last 24hrs: Started frontend Last 24hrs: Started frontend Last 24hrs: Started
designs and functionality. designs and functionality. frontend designs and
Next 24hrs: Complete US-104 Next 24hrs: Complete US-105 functionality.
frontend and write unit tests. frontend and write unit tests. Next 24hrs: Complete US-
106 frontend and write
unit tests.
9 Last 24hrs: Wrote unit tests, Last 24hrs: Wrote unit tests, Last 24hrs: Wrote unit
Had bugs in implementation. Had bugs in implementation. tests, Had bugs in
Next 24hrs: Fix bugs and Next 24hrs: Fix bugs and close implementation.
close US-104. US-105. Next 24hrs: Fix bugs and
close US-106.
10 Last 24hrs: Wrote unit test. Last 24hrs: Wrote unit test. Last 24hrs: Wrote unit
Changes were requested Changes were requested test. Changes were
during code review. during code review. requested during code
Next 24hrs: Address code Next 24hrs: Address code review.
review feedback, Close US- review feedback, Close US- Next 24hrs: Address code
104. 105. review feedback, Close
US-106.
Sprint Review
Attendees: Development Team, Scrum Master, Product Owner, and Key Stakeholders.
Duration: 1hr 30 mins.
Demonstration by Development Team/ Working product:
Feedback Collection:
Stakeholders requested adding more platforms like LinkedIn and Twitter.
Some feedback was received about the aesthetics of the "Forgot Password" page –
suggesting it should align more with the platform's branding.
Stakeholders requested an additional feature: Two-Factor Authentication (2FA) for
added security.
There were concerns about the error message clarity; stakeholders suggested more
user-friendly messaging and possibly tooltips.
Sprint Retrospective
Attendees: Development Team, Scrum Master, Product Owner, and Key Stakeholders.
Duration: 1hr 30 mins.
What went well?
Aspect Observation/ Feedback
Feature Implementation OAuth integration was smooth, and the team collaborated
efficiently to troubleshoot early issues.
Team Collaboration Daily stand-ups were consistent and productive. Everyone was
engaged and contributed.
What to improve?
Aspect Observation/ Feedback Action
Task Estimations Some tasks were underestimated, Provide buffer times for tasks
leading to a bit of a crunch with unknown complexities.
towards the end. Devs should include time to
Writing unit tests did not seem to write unit tests during
be accounted for during point estimation.
estimation.
User stories were Some stories had lots of Split large stories into sub tasks.
large integrations that could have been Convert large stories to epics.
separate tasks.
Sprint Artifacts
Sprint 2
Sprint duration: 2 weeks.
Sprint Theme
Enhanced User Experience in Food Selection
Sprint Goal:
Improve the user interface and functionality of the food list, enabling easier navigation,
selection, and information access for returning users and the owner.
Sprint Objectives
Enhance user engagement through an improved interface.
Streamline the food selection and checkout process.
Empower the owner with easy content management capabilities.
Ensure the application is responsive and user-friendly across various devices.
Sprint planning
Members present: Product owner, Scrum master, and Development team.
Total sprint points: 22
Time spent: 1hr 30mins.
Sprint backlog
1. [US-107] As a returning user, I want to view the food list as cards so that I can select what I
want.
Description: Implement a card layout for the food list, allowing users to see food items in a
more organized and visually appealing manner.
Sprint Points: 3
Definition of done:
Each food item is displayed in a card format, including an image, price, and brief
description.
The card layout is responsive and maintains visual appeal across different devices
and screen sizes.
Performance metrics show that the card layout loads quickly and efficiently, without
increasing the page load time.
2. [US-108] As a returning user, I want to search in the food list so that I don't have to scroll
endlessly.
Description: Add a search feature to the food list, enabling users to quickly find specific food
items.
Sprint Points: 5
Definition of done:
Users can type keywords in a search bar, and the list updates in real-time to show
matching results.
Search results are relevant and include a highlight for the searched term within the
results.
User testing confirms the ease of use and accuracy of the search function.
3. [US-109] As an Owner, I want to add and update food information so that a user can get
updated information.
Description: Allow the owner to add new food items and update existing ones, ensuring the
menu is current and accurate.
Story Points: 5
Definition of done:
The owner has an intuitive interface to add new food items and edit existing ones,
with fields for images, descriptions, and prices.
Changes made by the owner are reflected in the user interface immediately after
saving.
A log system tracks all changes made by the owner for future reference and
accountability.
4. [US-110] As a returning user, I want to view food information so that I can decide if I want
a food item.
Description: Enable users to view detailed information about each food item to make
informed choices.
Story Points: 2
Definition of done:
Users can type keywords in a search bar, and the list updates in real time to show
matching results.
Search results are relevant and include a highlight for the searched term within the
results.
User testing confirms the ease of use and accuracy of the search function.
5. [US-111] As a returning user, I want to add food to my cart so that I can check out when
I'm ready.
Description: Provide functionality for users to add food items to their cart, streamlining the
checkout process.
Story Points: 5
Definition of done:
Users can add food items to their cart with a clear indication of the cart's contents
(e.g., item count and total price).
The cart updates in real-time, and users can modify quantities or remove items
easily.
User feedback confirms the cart addition process is intuitive and error-free.
6. [US-112] As a returning user, I want to filter the food list so that I can reduce the time
spent looking for a food item.
Description: Implement filtering options in the food list, enabling users to narrow down
choices based on criteria like cuisine, dietary restrictions, etc.
Sprint Points: 2
Definition of done:
Users can apply multiple filters (e.g., cuisine type, price range, dietary restrictions) to
the food list.
The application of filters instantly updates the food list and maintains an optimal
performance level.
User testing shows that the filter functionality is intuitive and enhances the food
selection process.
Daily Scrum
ID Jevelyn Gurpreet Devrashi
1 Next 24hrs: Will start US-107 Next 24hrs: Will start US-108 Next 24hrs: Will start US-
backend. backend. 109 backend.
2 Last 24hrs: Finished US-107 Last 24hrs: Finished US-108 Last 24hrs: Finished US-
backend. backend. 109 backend.
Next 24hrs: Resume work on Next 24hrs: Resume work on Next 24hrs: Resume work
US-107, start frontend US-108, start frontend designs on US-109, start frontend
designs and functionality. and functionality. designs and functionality.
3 Last 24hrs: Started frontend Last 24hrs: Started frontend Last 24hrs: Started
designs and functionality. designs and functionality. frontend designs and
Next 24hrs: Complete US-107 Next 24hrs: Complete US-108 functionality.
frontend and write unit tests. frontend and write unit tests. Next 24hrs: Complete US-
109 frontend and write
unit tests.
4 Last 24hrs: Wrote unit tests, Last 24hrs: Wrote unit tests, Last 24hrs: Wrote unit
Had bugs in implementation. Had bugs in implementation. tests, Had bugs in
Next 24hrs: Fix bugs and Next 24hrs: Fix bugs and close implementation.
close US-107. US-108. Next 24hrs: Fix bugs and
close US-109.
5 Last 24hrs: Wrote unit test. Last 24hrs: Wrote unit test. Last 24hrs: Wrote unit
Changes were requested Changes were requested test. Changes were
during code review. during code review. requested during code
Next 24hrs: Address code Next 24hrs: Address code review.
review feedback, Close US- review feedback, Close US- Next 24hrs: Address code
107. 108. review feedback, Close
US-109.
6 Last 24hrs: Closed US-107 Last 24hrs: Closed US-108 Last 24hrs: Closed US-109
Next 24hrs: Will start US-110 Next 24hrs: Will start US-111 Next 24hrs: Will start US-
backend. backend. 112 backend.
7 Last 24hrs: Finished US-110 Last 24hrs: Finished US-111 Last 24hrs: Finished US-
backend. backend. 112 backend.
Next 24hrs: Resume work on Next 24hrs: Resume work on Next 24hrs: Resume work
US-110, start frontend US-111, start frontend designs on US-112, start frontend
designs and functionality. and functionality. designs and functionality.
8 Last 24hrs: Started frontend Last 24hrs: Started frontend Last 24hrs: Started
designs and functionality. designs and functionality. frontend designs and
Next 24hrs: Complete US-110 Next 24hrs: Complete US-111 functionality.
frontend and write unit tests. frontend and write unit tests. Next 24hrs: Complete US-
112 frontend and write
unit tests.
9 Last 24hrs: Wrote unit tests, Last 24hrs: Wrote unit tests, Last 24hrs: Wrote unit
Had bugs in implementation. Had bugs in implementation. tests, Had bugs in
Next 24hrs: Fix bugs and Next 24hrs: Fix bugs and close implementation.
close US-110. US-111. Next 24hrs: Fix bugs and
close US-112.
10 Last 24hrs: Wrote unit test. Last 24hrs: Wrote unit test. Last 24hrs: Wrote unit
Changes were requested Changes were requested test. Changes were
during code review. during code review. requested during code
Next 24hrs: Address code Next 24hrs: Address code review.
review feedback, Close US- review feedback, Close US- Next 24hrs: Address code
110. 111. review feedback, Close
US-112.
Sprint Review
Attendees: Development Team, Scrum Master, Product Owner, and Key Stakeholders.
Duration: 1hr 30 mins.
Demonstration by Development Team/ Working product:
Feedback Collection:
Stakeholders suggested adding more interactive elements, like hover effects, to make
the user interface even more engaging.
Some feedback was received about the aesthetics of the Search feature – that it
sometimes doesn't return relevant results for certain keywords. Improving the search
algorithm could further enhance this feature.
Stakeholders suggested considering filters based on customer ratings or popularity to
further enhance user experience.
Stakeholders suggested that a 'quick view' feature on the card to see basic details
without fully opening the item could improve navigation.
Sprint Retrospective
Attendees: Development Team, Scrum Master, Product Owner, and Key Stakeholders.
Duration: 1hr 30 mins.
What went well?
Aspect Observation/ Feedback
Feature Implementation OAuth integration was smooth, and the team collaborated
efficiently to troubleshoot early issues.
Team Collaboration Daily stand-ups were consistent and productive. Everyone was
engaged and contributed.
What to improve?
Aspect Observation/ Feedback Action
Task Estimations Some tasks were underestimated, Provide buffer times for tasks
leading to a bit of a crunch with unknown complexities.
towards the end. Devs should include time to
Writing unit tests did not seem to write unit tests during
be accounted for during point estimation.
estimation.
User stories were Some stories had lots of Split large stories into sub tasks.
large integrations that could have been Convert large stories to epics.
separate tasks.
Sprint Artifacts