This document provides an overview of a healthcare website project executed using scrum methodology over 4 sprints. The objective is to provide a simple and intuitive website for healthcare services. Product backlog and release planning was done in Jira, with sprints 1 and 2 focusing on high and medium priority items. Sprint planning involved estimation using planning poker. Sprint 1 focused on completing high priority tasks while sprint 2 introduced users to services. Daily meetings helped resolve issues and ensure progress. The scrum master facilitated retrospectives and found the experience valuable for learning.

1. ProjectExecution Overview-Healthcare
Website
By
SankalpSharma
ShubhamDubey
KaranPatel
AmarpreetKaurLnu
ChenyuWang
PJM6810PrinciplesofAgileProjectManagement
Prof.MohamedHefny
March4,2023

2. PROJECTOVERVIEW
• The objective of the project is to provide a website related to
healthcare services
• There are total of four sprints in this task.
• Every sprint has a duration of 1 week.
• The website should have a simple and intuitive design that
allows users to easily navigate and find the information they
are looking for.
• We have used jira to create the sprints and the project.

3. PRODUCTBACKLOGAND RELEASE
PLANNING(ScrumMaster-Sankalp Sharma)
• Product Vision :- Our home healthcare website aims to offers
user-friendly access to a range of healthcare services, tools,
and resources to help patients and their families manage their
healthcare at home and improve their quality of life.
• Road Map Creation :- We have created two sprints to show
the High, Medium and low Priorities.
• Sprint 1 :- High Priority Items
• Sprint 2 :- High priority and Medium priorities items
• Sprint 3 :- Medium and some low priority items
• Sprint 4 :- Low priority items

4. SprintBacklog Planning& Estimation(Scrum
Master- Sankalpsharma)
• In this project we created the Road map and product backlog
on Jira software.
• Sprint 1 and sprint 2 Holds the mix of high priority, Medium
priority and some low priority task which is also created in Jira
according to the product backlog
• For Estimation, We have used the planning poker method for
better results. Also, Teams decide story points based on the
quantity of labor, danger, and complexity of the job.

5. Overview OF Sprint 1
• During the first sprint, we encountered numerous high-priority
tasks, and assigning every team member with one task of high
priority, Some of them took the responsibility for two.
• Despite the challenges that arose, we all managed to
complete our assigned tasks within the designated timeframe
by helping each other in the meeting and for the task.
• we were well-prepared to take on the next sprint with a
renewed sense of focus and determination.
• Once the sprint was complete, we held a comprehensive
review to evaluate our progress and address any obstacles
that we faced. This included a thorough examination of the
tasks that were completed, the issues that we encountered,
and the strategies that we employed to overcome them

6. Overview of Sprint 2
• This sprit includes the mixture of high priority, medium
priority and some low priority tasks as well.
• The main objective of this sprint is to introduce users to the
various services that our organization offers. We want to
ensure that our users are aware of all the available options, so
they can choose the services that best fit their needs.
• We focused on providing users with a clear understanding of
the services we offer, the benefits of using our services, and
how we can support them through the entire process by
Including some pages like About us, How we Help and FAQ’s.

7. Obstacles and Solutions
• Throughout the sprint, our team was able to successfully
complete our tasks with minimal obstacles. While we did face
a few minor challenges, our team worked together to
overcome them and ensure that our progress was not
impeded.
• Daily meetings helped us maintain a smooth workflow by
encouraging open communication among team members. This
allowed us to quickly address any issues or concerns and
resolve communication errors that arose during the sprint.

8. Experience as Scrum master
• It was a great experience working as a scrum master for the
whole team as I worked closely with the team to ensure that
they have a clear understanding of the project goals and
requirements.
• I also facilitated regular retrospectives to help the team
continuously improve our processes and experiment with new
approaches to work.
• I learned a lot after this project as being a scrum master as it
was my first time doing this project as a scrum master.
• Overall, If I want to rate my experience I would love to rate 8
out of 10.

9. THANK YOU