……

……
…… CMU-SE 433 EIS

Scrum
Process
Group 2
 Group x

Member Information
x x x x

MSSV: 26211200134 MSSV: 26201141758 MSSV: 26211200238 MSSV: 26211227122

Nguyen van vi Nguyen THI Do huy hoang Nguyen anh minh

Leader XUAN DUNG Member Member
Member
 Introduce the topic

Presentation Content

01 Introduction to Scrum

02 Scrum Theory

03 Scrum Values

04 Scrum Team

05 Scrum Events

06 Scrum Artifacts
 01.
Introduction to Scrum
 Scrum History

The First Scrum Team The Agile Manifesto is

Created

1986 1995 2010

1993 2001

Takeuchi and Nonaka Scrum is First First Scrum Guide is

Introduce the Concept Presented to the Public Published
 What is
Scrum is a lightweight
framework that helps Scrum?
people, teams and
1

65
4

32
organizations generate
value through adaptive
solutions for complex
problems.
 Scrum Purpose

Team Satisfaction 1 Delivering Value to

6
Customers

Transparency and Enhancing Flexibility and

2
5
Communication Responsiveness

3
4
Increasing Productivity Creating a Positive Work
and Quality Environment
 x x x x

Transparency
Inspection Adaptation
02.
Giving visibility
Timely checks on Adjusting a
Scrum
to the significant
aspects of the
process to those
the progress
toward a sprint
goal to detect
process as soon
as possible to
minimize any
Theory
responsible for
undesirable further deviation
the outcome.
variances. or issues.

x x x x
 03.
Scrum
Value
 Commitment
People personally commit to achieving the goals of the Scrum
Team

03.
Scrum
Value
 Focus
Everyone focuses on the work of the Sprint and the goals of the
Scrum Team

03.
Scrum
Value
 Openness
The Scrum Team and its stakeholders agree to be open about all
the work and the challenges with performing the work

03.
Scrum
Value
 Respect
Scrum Team members respect each other to be capable,
independent people

03.
Scrum
Value
 Courage
Scrum Team member have courage to do the right thing and work
on tough problems

03.
Scrum
Value
 Scrum

Applying Scrum Values

Sprint Daily Sprint Sprint Backlog

Planning Scrum Review Retrospective Refinement
 Scrum

Applying Scrum Values

Sprint Planning

Commit to a realistic and achievable

sprint goal that aligns with the
product vision and customer needs.
 Scrum

Applying Scrum Values

Daily Scrum

Commit to updating the team on your

progress, have the courage to speak up
about any issues or risks
 Scrum

Applying Scrum Values

Sprint Review

Commit to delivering a potentially

releasable product increment that meets
the definition of done and acceptance
criteria.
 Scrum

Applying Scrum Values

Sprint Retrospective

Commit to participating actively and

honestly, sharing positive and negative
experiences, and addressing any issues
that might affect the team.
 Scrum

Applying Scrum Values

Backlog Refinement

Commit to maintaining a well-defined and

well-ordered product backlog that reflects
the product vision and customer needs.
04
SCRUM
TEAM

SCRUM The fundamental unit of

Scrum is a small team of
people,
Scrum teams are cross-
functional and self-

TEAM
organizing.
Scrum Team.
 Benefits of a Scrum team
THREE MAIN SCRUM ROLES

Work happens Workflow processes are Return on investment (ROI)

simultaneously made clear increases and risk decreases
 x x x x

• The Scrum events are key elements of the Scrum Framework

SCRUM EVENTS
• The Scrum events are time-boxed events.

x x x x
05. The Sprint

Five Scrum Sprint Planning

Events Daily Scrum

Sprint Review

Sprint Retrospective
 Scrum Events

Daily
Sprint Scrum The Scrum Team may also invite other people to attend Sprint Planning to provide advice.
TheRetrospective
Sprint
Sprint Sprint
Review
Planning

The
The purpose
purpose of the
of the Daily
The purpose of the
The purpose
Scrum
Sprint
The Review
Purpose ofofisthe
is to increase forSprint
the
Sprintthe
Sprint is to deliver a
likelihood
team of delivering
Retrospective
to discuss to a
is the
what
Planning
Done, is to plan
usable
Done,
they usable
completed
improve theincrement
during
Scrum
work for
increment the upcoming
that meetsthat meets
the Sprint
the Sprint
Team’sSprint. and
effectiveness.
the Sprint
Goal.Goal.
collaborate on what to The
During
feedback
A Sprint
Sprints
The theScrum
begins
are
Daily Sprint
fromisaRetrospective,
the
time-framed,
with Sprint
aSprint noReview
thesession
arePlanning
short, more
15-minuteteam
isdaily
thanused
areflects
todefine
month
to update
on the
theSprint
in held
meeting past
length,
the Product
by Sprint
and
the areBacklog
Goal and
and identifies
and
consistent
Developersplan inform
ofthe waystoto
throughout
thework
Scrum
do next. improve
planning
the development.
process
for the next
be Team.
done.for the
Sprint.
next Sprint.
 06.
Scrum
Artifacts
x x x x

Product Increment User Stories

Product Backlog
The product that is delivered by the
A user story team
is aat thepart of A prioritized list of all the work

Scrum Artifacts end of each sprint 01 that needs to be done to

an Agile software achieve the product goal.

development approach
06.

to acquire the details of

02
03
a requirement from an
end-user’s point of
Sprint Backlog
view.
A list of the work that the team plans to complete
during the current sprint.
x x x x
When it comes to the user story writing technique, there are just three basic requirements you need to keep in
mind before getting started.
 Product Backlog

The Product Backlog is a prioritized list of all the work that

needs to be done on the product.

Requirements

Features

Tasks
 Product Backlog

The Sprint Backlog is composed

of the Sprint Goal (why), the set
The Sprint Backlog is a subset
of Product ofitems
Backlog the
Product Backlog, containing
selected specific
for the Sprint (what), as
well asfor
work items selected an actionable plan for
a particular
delivering the Increment (how).
Sprint.
 The Increment is the sum of all completed work items marked as "Done" from

Increment previous Sprints. It is a potentially releasable version of the product that can
be delivered to the customer at any time.
 Sprint
Burndown Charts
A sprint burndown chart is a graphical
representation of the estimated effort remaining for
a given period of time during a Sprint.
 Sprint Burndown Chart
Why is it important?

Track their progress Identify and address any Communicate their

towards the Sprint Goal potential problems early on progress to stakeholders
 Sprint Burndown Chart
Estimation
How to read a sprint burndown chart
Estimation
Techniques Techniques
T-shirt
The
Big/uncertain/small
Dot
Planning
voting
Bucket
sizing
poker
System
 The horizontal axis represents the days in the
Sprint
A quick and
rough
simple
Planningestimation
andeasy
fast
Poker is estimation
techniqueestimation
antechnique
where where
Agileteam Estimation is an important part of
 The vertical axis represents the estimated
technique
team members
estimating
members where
categorize
teamwork
categorize members
and planning work
items vote
technique
into
agile development,
effort remaining but there is no
on
place
items
thatthe
iswork
into
size
different
basedthree
of
items
sizes,each
on categories:
into
such
an work
asdifferent
item
agreement
extrabig,
using
small,
from  The ideal burn rate is a straight line from the
stickers.
buckets
uncertain,
the team
small, based
onand
medium, theon
small.
theirand
points
large, size.extra
being one-size-fits-all
top approach.
of the vertical axis to the bottom,
assigned to the PBI.
large. indicating that the team is completing work at
a steady pace.
……
……
……

THANK YOU!
for listening.
GROUP x