Scribd
Upload
59 views3 pages

Day 10

Scrum is a management framework that focuses on delivering products incrementally through defined roles, including the Product Owner and ScrumMaster, and structured ceremonies. The Product Owner prioritizes the work and communicates with stakeholders, while the ScrumMaster ensures adherence to the Scrum process and facilitates the team's work. Key ceremonies include Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, which help teams stay aligned and continuously improve.

Uploaded by

Divya S
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
59 views3 pages

Day 10

Scrum is a management framework that focuses on delivering products incrementally through defined roles, including the Product Owner and ScrumMaster, and structured ceremonies. The Product Owner prioritizes the work and communicates with stakeholders, while the ScrumMaster ensures adherence to the Scrum process and facilitates the team's work. Key ceremonies include Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, which help teams stay aligned and continuously improve.

Uploaded by

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

Scrum

Scrum is a management and control process that cuts through complexity to focus on
building products that meet business needs. Management and teams are able to get
their hands around the
requirements and technologies, never let go, and deliver working products,
incrementally and empirically. Scrum is simple. It is the opposite of a big
collection of interwoven mandatory components. Scrum replaces a programmed
algorithmic approach with a heuristic one, with respect for people and self-
organization to deal with unpredictability and solving complex problems.
A product owner creates a prioritized wish list called a product backlog.
During sprint planning, the team pulls a small chunk from the top of that wish
list, a sprint
backlog, and decides how to implement those pieces.
The team has a certain amount of time — a sprint (usually two to four weeks) — to
complete its
work, but it meets each day to assess its progress (daily Scrum).
Along the way, the ScrumMaster keeps the team focused on its goal.
At the end of the sprint, the work should be potentially shippable: ready to hand
to a customer,
put on a store shelf, or show to a stakeholder.
The sprint ends with a sprint review and retrospective.
As the next sprint begins, the team chooses another chunk of the product backlog
and begins
working again.

Product Owner:

The product owner is the cornerstone of project success, responsible for defining
the work that needs to be completed and prioritizing that work. He or she needs to
know what the project is expected to deliver and why those elements are important
-- to customers, to the market, to the organization. The product owner must also be
the face of all of those interests to the project team, acting as an expert guide
as the team carries out the project. his role is central to ensuring that the team
delivers high-quality work that meets the needs and expectations of stakeholders.
The Product Owner acts as a bridge between the stakeholders (customers, users, and
other business representatives) and the Scrum Team.

Day to day activities of a Product Owner

1. Creates and MAINTAINS the Product Backlog.


2. Prioritizes and sequences the Backlog according to business value or ROI
3. Assists with the elaboration of Epics, Themes and Features into User stories
4. Conveys the Vision and Goals at the beginning of every Release and Sprint.
5. Represents the customer, interfaces and engages the customer.
6. Participates in the daily Scrums, Sprint Planning Meetings and Sprint Reviews
and Retrospectives.
7. Inspects the product progress at the end of every Sprint and has complete
authority to accept or reject work done.
8. Can change the course of the project at the end of every Sprint
9. Communicates status externally.
10. Terminates a Sprint if it is determined that a drastic change in direction is
required

SCRUM Master

The ScrumMaster role has two distinct elements. First, he or she acts as the
protector of the team, making sure that everyone on the project, especially the
development team members, can focus on their work without any distractions. The
second element of the ScrumMaster role is to protect the Scrum process itself. The
ScrumMaster is the expert on how Scrum works and how it should be applied. He or
she will ensure that the product owner and development team stay within the Scrum
framework. By extension, the ScrumMaster can coach the other team members on how to
use Scrum in the most effective manner.

Day to day activities of a Scrum Master


1. Organizing the meetings
2. Facilitating the team members solving impediments
3. Facilitating the Product Owner in fulfilling his role adequately
4. Facilitate preparing and having the meetings
5. Facilitate the team in following the Scrum process

Different roles in a SCRUM Team

The Team is responsible for turning the product backlog items into increments of
value in each Sprint. It consists of a cross functional team of 7 +- 2 people.
There might be core team members and shared team members. The scrum team consists
of Business Analyst/Product Owner, Scrum Master/ Agile Coach, Technical team
(Developers, Tech Architects, Data Analysts/Data Modelers, Testers, etc.,)

12 Principles of SCRUM

1. Empirical Process Control


2. Self-Organizing Teams
3. Cross-Functional Teams
4. Iterative Development
5. Transparency
6. Inspection
7. Adaptation
8. Focus on Value
9. Customer Collaboration
10. Deliver Working Software
11. Simplicity
12. Continuous Improvement

SCRUM Ceremonies

In Scrum, ceremonies (or events) are structured meetings that occur at specific
points during a Sprint to ensure that the Scrum framework is followed effectively.
These ceremonies help Scrum Teams stay aligned, inspect progress, adapt to changes,
and plan future work.

1. Sprint Planning

Purpose: To plan the work for the upcoming Sprint.


When: At the beginning of each Sprint.
Duration: Typically 2 hours for a 2-week Sprint (adjustable based on Sprint
length).
Participants: Scrum Team (Product Owner, Scrum Master, Development Team).
Activities: Discussion of the requirements, Discussions between developers and
testers

2. Daily Scrum (Daily Stand-Up)


Purpose: To synchronize the team's work and identify any obstacles.
When: Every day during the Sprint.
Duration: 30 minutes.
Participants: Scrum Team (Development Team, Scrum Master, Product Owner).
Activities:

Answer Three Questions:


What did I do yesterday that helped the team meet the Sprint Goal?
What will I do today to help the team meet the Sprint Goal?
Do I see any obstacles that are preventing me or the team from meeting the Sprint
Goal?
Briefly discuss progress, plans, and any issues or blockers.

3. Sprint Review
Purpose: To inspect the increment and adapt the Product Backlog if needed.
When: At the end of each Sprint.
Duration: Typically 1-2 hours for a 2-week Sprint.
Participants: Scrum Team, stakeholders, and sometimes other interested parties.

Activities:
Demonstrate the Increment: The team presents the work completed during the Sprint,
including the new features or changes. Usually BA gives a brief overview of the
user story followed by the demonstration of what the developers has created
followed by answering any queries. The Demo usually happens in the testing
environment and the demo happens after the tester signoff.
Receive Feedback: Stakeholders provide feedback on the increment and discuss any
changes or new requirements.
Update the Product Backlog: Based on feedback, the Product Backlog may be updated
to reflect new priorities or changes.

4. Sprint Retrospective
Purpose: To reflect on the Sprint and identify improvements for the next Sprint.
When: After the Sprint Review and before the next Sprint Planning.
Duration: Typically 1-1.5 hours for a 2-week Sprint.
Participants: Scrum Team (Development Team, Scrum Master, Product Owner).

Activities:

Reflect on the Sprint: Discuss what went well, what didn’t go well, and what could
be improved.
Identify Improvements: Determine actionable items or changes that could improve
processes or team dynamics.
Create a Plan: Develop a plan for implementing improvements in the next Sprint.

You might also like