Scrum Fundamentals
Uploaded by
Matias SchulzScrum Fundamentals
Uploaded by
Matias SchulzSCRUM (AGILE METHODOLOGY)
COHESIVE UNITS OF PROFESSIONALS FOCUSED ON DELIVERING USABLE VALUE
Source: official Scrum guide
PILARS
Transparency enables
inspection. Inspection Scrum events are
Artifacts that have without transparency designed to provoke
low transparency can change. A Scrum Team
is misleading and
lead to decisions is expected to adapt
that diminish value wasteful. Inspection the moment it learns
and increase risk. enables adaptation. anything new through
Inspection without inspection.
adaptation is
considered pointless.
TEAM
The fundamental unit of Scrum: the Scrum Team consists of one Scrum Master, one Product Owner,
and Developers. These are cross-functional, self-managing, and small enough to remain nimble but
still able to complete significant work within a Sprint.
Accountable for establishing Scrum
as defined in the Scrum Guide, and
for the Scrum Team’s effectiveness.
Accountable for maximizing Committed to creating
the value of the product any aspect of a usable
resulting from the work of Increment each Sprint.
the Scrum Team.
ARTIFACTS
• Product Backlog: ordered list of what is needed to
improve the product. It is the single source of work
undertaken by the Scrum Team. It should be measured in
relation to the product goal.
• Sprint Backlog: composed of the Sprint Goal (why), the set
of Product Backlog items selected for the Sprint (what), as
well as an actionable plan for delivering the Increment (how).
• Increment: concrete stepping stone toward the Product
Goal. 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(1).
(1) Definition of Done: criteria to be met by any piece of work to be considered an increment and therefore, value-adding.
EVENTS
Scrum employs an iterative, incremental approach to optimize predictability and to control risk.
Combines four formal events for inspection and adaptation within a containing event: the Sprint.
These events implement the empirical Scrum pillars of transparency, inspection, and adaptation.
• Sprint planning: meeting where the Scrum Team decides
what will be done in the new Sprint.
• Daily Scrum: daily meeting to inspect progress toward
the Sprint Goal and adapt the Sprint Backlog as necessary.
• Sprint review: meeting at the end of each Sprint to
inspect the outcome of the Sprint and determine future
adaptations.
• Sprint retrospective: occasional meeting to plan ways
to increase general quality and effectiveness.
