SCRUM

Nguyễn Ngọc Hoàng 20IT371

Nguyễn Văn Tình 20IT554
Trần Anh Dũng 20IT478
Trương Vũ Khoa 20IT524
GV:Ths.Nguyễn Thanh Yên Tùng Lê Văn Chương 20IT734
GIỚI THIỆU NỘI DUNG

Hoàng Khoa Chương Tình Dũng

Scrum Definition Scrum Scrum Team Scrum Scrum
Scrum Values Theory Events Artifacts
 What is AGILE ?

The agile mindset is a flexible way of thinking that enables people to react quickly and adapt to changing situations.
It involves understanding, collaborating, learning, and staying flexible to achieve high-performing results..

4 core values:

1. Individuals and Interactions Over Processes and Tools

2. Working Software Over Comprehensive Documentation
3. Customer Collaboration Over Contract Negotiation
4. Responding to Change Over Following a Plan
01 SCRUM Definition
 SCRUM Definition

• Scrum is a lightweight framework that

helps people, teams and organizations
generate value through adaptive
solutions for complex problems.
• Scrum is built upon by the collective
intelligence of the people using it.
Rather than provide people with
detailed instructions, the rules of
Scrum guide their relationships and
interactions.
02
Scrum Theory
SCRUM Theory

01 Scrum is founded on empirical process control

theory, or empiricism.

Empiricism asserts that knowledge comes

02 from experience and making decisions based
on what is observed

03 There are 3 scrum pillars, transparency,

inspection, and adaptation.
 SCRUM Theory

Three pillars uphold every implementation of empirical process control

 SCRUM Theory

Transparency

● It is crucial that important aspects of the process are

clearly displayed for those performing the work as well
as those receiving the work.

● Transparency necessitates defining these aspects to

establish a shared understanding among stakeholders.
 SCRUM Theory

Inspection

● Inspection is vital in Scrum to maintain work quality and

progress.

● It involves examining Scrum artifacts and monitoring

work progress
 SCRUM Theory

Inspection

● Inspection is often carried out through meetings and

discussions in the Scrum process

● Inspection enables adaptation. Inspection without

adaptation is considered pointless. Scrum events are
designed to provoke change.
 SCRUM Theory

Adaptation

● If the inspector identifies process deviations beyond

acceptable limits, adjustments must be made to ensure
an acceptable outcome.

● In Scrum, adaptation is crucial to ensure continuous

improvement and development.
03 SCRUM Values
 SCRUM Values

01 Everyone individually achieves the Scrum

Team's goals
COMMITMENT

Scrum Team members have the courage to

02 do the right thing and solve difficult
problems
FOCUS

SCRUM 03 Everyone focuses on the work of the

COURAGE
Sprint and the goals of the Scrum Team
Values
The Scrum team and stakeholders agree
04 to be open about all of the work and the
challenges of doing the work
OPENNESS

Scrum Team members respect each other

05 to become competent and independent
people
RESPECT
04
SCRUM TEAM
 SCRUM TEAM

● Scrum Team is small enough to

Develops
remain nimble and large enough to
complete significant work within a
Sprint, typically 10 or fewer people
● They are also self-managing,
SCRUM meaning they internally decide who
Scrum master
TEAM does what, when, and how.
● Scrum Teams are cross-functional
● The Scrum Team is responsible for all
product-related activities from
stakeholder collaboration,
Product owner verification, maintenance, operation,
experimentation, research and
development
 SCRUM TEAM

Developers
● Helps to create (develop) a valuable
product for a customer.
● Requires the ability to self-manage work
according to commitment and
responsibility for completing work
 SCRUM TEAM

Product Owner
● The Product Owner is accountable for
maximizing the value of the product
resulting from the work of the Scrum Team
● The Product Owner is accountable for
effective Product Backlog management
● The Product Owner is one person not a
committee
 SCRUM TEAM

Scrum Master
● The Scrum Master is responsible for promoting
and supporting Scrum as defined in the Scrum
Guide
● The Scrum Master is a servant-leader for the
Scrum Team.
● Scrum Master is responsible for helping Product
Owner in Product Backlog management
● The Development Team should be coached by
the Scrum Master how to become a self-manage
and cross-functional team and deliver the high
value products
05
Scrum Events
 SCRUM EVENTS

Sprint
● It can be said that Sprint is the heart of Scrum
● Sprints are time-boxed no longer than 1 month and typically no
shorter than a week.
● Sprints have the same length and take place consecutively
without interruption.
● The Sprint ends when the time-boxed period ends
● During the Sprint:
+ No changes are made that would endanger the Sprint Goal
+Quality does not decrease;
+The Product Backlog is refined as needed; and,
+Scope may be clarified and renegotiated with the Product
Owner as more is learned.rified and renegotiated with the PO as
more is learned.
 SCRUM EVENTS

01 Sprint Planning 02 Daily Scrum

• Inspect progress toward
• An event that takes place at the Sprint Goal and
the beginning of a Sprint to adapt the Sprint Backlog
plan work for the entire Sprint as necessary, adjusting
Description the upcoming planned
work
04 Sprint Retrospective 03 Sprint Review
• inspect the outcome of
• Identify area of improvement the Sprint and determine
to increase product quality future adaptations
• Requesting feedback
from stakeholders
 SCRUM EVENTS

Sprint Planning Daily Scrum

• Enhance customer satisfaction • Identify obstacles and improve
by manage product backlog team communication
• Save time by reviewing backlog • Boost team knowledge and
in advance helps in making decision

Benefits

• Improve responsiveness to
stakeholders. Requirement
• Improve quality of production
• Boost team morale
Sprint Retrospective Sprint Review
 SCRUM EVENTS

▪ Scrum master (facilitate)

01 ▪ Product owner Sprint Planning
▪ Developers

▪ Scrum master (facilitate)

02 ▪ Developers
Daily Scrum

▪ Developers
Participants
03 ▪ Product owner Sprint Review
▪ Scrum master (facilitate)

▪ Developers
Sprint
05 ▪ Product owner
Retrospective
▪ Scrum master (facilitate)
 SCRUM EVENTS

24 h

30
Days

Sprint Planning Daily Scrum Sprint Review Sprint Retrospective

For a one-month Sprint, The Daily Scrum is a concise Sprint Reviews are Sprint Retrospectives are
Sprint Planning is 15-minute meeting, regardless timeboxed to 4 hours timeboxed to 3 hours for
timeboxed to 8 hours of the Sprint length. for a one-month Sprint. a one-month Sprint.
 ARTIFACTS

06
 SCRUM Artifacts

01 Product Backlog
• Scrum artifacts represent work or
value.
• They are designed to maximize
transparency of key information.
SCRUM 03 Sprint Backlog
Artifacts

05 Increment
SCRUM Artifacts
 SCRUM Artifacts

1. Increment

• An Increment is a concrete stepping stone toward the Product Goal.

• Each Increment is additive to all prior Increments and thoroughly verified,

ensuring that all Increments work together.

• In order to provide value, the Increment must be usable.

• Work cannot be considered part of an Increment unless it meets the Definition

of Done.
SCRUM Artifacts
 SCRUM Artifacts

2. Sprint Backlog

• The Sprint Backlog is a plan by and for the Developers. It is a highly visible,
real-time picture of the work that the Developers plan to accomplish during the
Sprint in order to achieve the Sprint Goal.
• The Sprint Backlog is updated throughout the Sprint as more is learned
• The Sprint Goal is a commitment by the Developers, it provides flexibility in
terms of the exact work needed to achieve it.
• The Sprint Goal also creates coherence and focus, encouraging the Scrum Team
to work together rather than on separate initiatives.
• The Sprint Goal is created during the Sprint Planning event and then added to
the Sprint Backlog.
 SCRUM Artifacts

3. Product Backlog

• The Product Backlog is an

emergent, ordered list of what is
needed to improve the product. It is
the single source of work.
undertaken by the Scrum Team.
• Product Backlog refinement is the
act of breaking down and further
defining Product Backlog items
into smaller more precise items.
• Can be updated at any time by PO.
• The Developers who will be doing
the work are responsible for the
sizing.
• Never completed.
THANK YOU FOR LISTENING