1

Conduct Sprint 2

Haoran Xu, Nayan Dipakkumar Parmar, Parul Mathur,

and Pratiksha Sudarshan Rawat

Project Management, College of Professional Studies, Northeastern University

PJM 6810: Principles of Project Agile Management

Dr. Sarmann I Kennedyd

October 24, 2021

Table of Contents

Executive Summary.....................................................................................................................................3
Sprint Goal and Outcome...........................................................................................................................4
Sprint Retrospective.....................................................................................................................................4
Sprint Planning............................................................................................................................................5
Sprint (Jira) Execution...............................................................................................................................6
References.....................................................................................................................................................8
3

Conduct Sprint 2

Executive Summary

The primary spectrum of sprint 2 is comprised of the retrospective findings from sprint 1.

The group's initial step was to prioritize possible enhancements during sprint planning. Increased

session regularity, adjusted meeting duration, rationalized Jira tracking, and documents

generating for sprint 2 are all highlighted as procedures that would benefit the group's

effectiveness and performance.

Because the tasks were less as closely tied as they were the previous sprint, fewer issue

connections were formed in Jira, allowing the team more flexibility in task prioritizing. As a

consequence, numerous tasks were found to be suitable for a simultaneous strategy and began at

the same time.

The project manager was in charge of developing and carrying out the session agenda,

and also documenting and producing minutes of meeting so that the group had a checklist of

activities with precise needs. The PM was also responsible for putting together the retrospective

approach and organizing the meeting.

The scrum master oversaw the sprint's development, ensuring that tasks were begun and

completed according to the sprint plan, and recording the sprint 2 changes found at the

retrospective meeting.

The product owner checked that the user stories as well as acceptance criteria met the

sprint’s objective and the customer's needs. During the initial day of consequence, the PO

additionally conveyed the enhancement activities to the group, ensuring that there were no

conflicts between the retrospective objective and the current task implementation.
4

The QA was in charge of overseeing the accuracy of the Jira work, spotting any

methodological flaws, verifying the meaning of DONE, and ultimately having the last say over

the document's ultimate modification. He additionally managed all of the group's requests for

modifications during the sprint's implementation, verifying such requests with the sprint plan.

Sprint Goal and Outcome

The team worked on sprint 2 as part of week 5, where we had conducted a sprint planning

meeting to finalize the sprint goals. The 2nd sprint was focused on high-priority and medium

priority backlogs items that are shown in the image below.

Following a fundamental grasp of what to anticipate from the website from the first sprint, the

second sprint mainly focus on the services that help users to understand more about the website

For example- knowing the information regarding the staff and partnership of the healthcare

service, getting queries from the FAQ and online forum so they get an idea how they may profit

from them. Furthermore, customers can see the video regarding the services healthcare provides

them

Sprint 2 Objectives:

• Follow the scrum principles and ground rules as outlined in the Team charter.

• Sprint 2 Organizing

• Backlogging the Sprint

• Decide the sprint start and end dates

• Dividing the team’s roles

• Creating tasks for the user stories

• Jira has been updated:

https://adityagangar.atlassian.net/jira/software/projects/HHPG/boards/3/backlog

• To overcome obstacles the team faced in sprint 1

• Hold a sprint 2 review and retrospective meeting.

• Complete sprint 2 by decided deadline

Sprint Retrospective

Prior scheduling for the following sprint, the sprint retrospective is a check-and-adapt

process (Rubin, 2013). It is a timed event that is conducted by the Scrum Master or a Scrum team

mate (Ozoli, 2018). It is one of the most important Scrum practices, as it aids in determining

what is and is not functioning with the sprint and associated technological approaches (Rubin,
6

2013). Its goal is to enhance team members' bonds and promote prospective cooperation; as a

result, the team must be honest, inclusive, and show respect (Ozoli, 2018). This exercise

generates procedure enhancement measures that the group should implement in the following

sprint.

The group had a Sprint Retrospective following Sprint 1 was accomplished, which was

overseen by the scrum master for that week. Before the discussion, the topic and framework

were developed. The group acknowledged the prior iteration's obstacles, issues, achievements,

and errors. The following were the procedure enhancement activities highlighted at the meeting:

 Duties must be completed on schedule.

 Due to the sprint's short timeframe, timely interaction on the platforms is

essential.

 Prior to the meeting, appropriate notice of the unavailability should be provided.

Aside from the problems, the group praised everybody for the great attempt and

optimistic attitude. Because the optimization actions weren't really task-related, they were left off

the sprint backlog.

Sprint Planning

Planning phase is a continuous, just-in-time process that occurs prior to the start of every

sprint. The Product Owner explains the beginning sprint goal, as well as the highest tasks from

the grooming prioritized backlog that fit the criterion of ready. The key items have explicit

acceptance criteria and are evaluated, estimated, as well as prioritized. Depending on the team's

pace, restrictions, and skills, the development team collaborates to determine what they can offer
7

(Rubin, 2013). Ultimately, the development team expresses their dedication through the sprint

objective and product backlog elements that have been finalized (Rubin, 2013).

Sprint 2 planning started by grooming our product backlog, that includes shifting the

outstanding pages and top-level features to the sprint backlog. The product backlog items then

were sized as well as estimated, while acceptance criteria was set. the existing sprint backlog was

established depending on the team's velocity and actual capabilities. Sprint 2 was supposed to be

finished in one week on March 27, 2022. To achieve a good outcome, the Scrum Master watched

the planning activities, answered questions, and moderated the discussion.

Sprint (Jira) Execution

In this week, the scrum team has decided to execute sprint 2 for the home health care project.

The following are the major actions taken by the scrum team to execute sprint 2,

1. Task creation for User Stories

The team had completed the development of the website's 'Pages' in the initial

sprint. Furthermore, now in this second sprint, the scrum team has started working

on generating tasks for User stories related to services and functionalities of the home

health care project.

2. Building User Stories and Acceptance Criteria

Every user story was written from the end users’ point of view. These end users’

perspectives help the developers in creating a webpage that is suitable for the customers.

Moreover, the team has also defined acceptance criteria for the tasks and the developers

have successfully achieved the task objectives by comparing them to the provided

criteria.

3. Story point estimation for User Stories

The Planning Poker method was used to provide story point estimates to

the backlog items. Moreover, the team decided to use the Fibonacci sequence to

characterize the user stories in sprint 2.

4. Allocation of work to the team

Considering the team performance on sprint 1, the user stories were assigned to

all the five members involved and the tasks were assigned based on team members’

capabilities and skills that are required for executing those tasks in a timely manner.

5. Creating connections among User Stories and tasks

The work processes were managed by the team. The user stories were linked

using the terms ‘related to’,' 'blocks,' and 'is blocked by,' to make the necessary

connection with other stories. Using Jira’s parent-child issue capabilities, the tasks

were linked to the user stories as 'child issues'. 

6. Managing User Stories

The scrum team has actively collaborated with each other and advanced their

working capabilities for delivering the user stories as per the product owners’

requirements. Moreover, we have regularly updated the task status in the task

board to see the sprint progress and performed accordingly to achieve the sprint

goal.

References

Rubin, K.S. (2013). Essential Scrum: A Practical Guide to the Most Popular Agile Process.

Addison-Wesley Professional.

Ozoliņš, P. (2018). Preparation and Facilitation of Retrospective Meeting in Scrum process.

Information Technology and Management Science. DOI: 10.7250/itms-2018-0009.