Short introduction to Scrum - a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.

1. INTRODUCTION to SCRUM
(framework for developing and sustaining complex products)

2. scrum
noun
a framework within which people can address
complex adaptive problems, while productively
and creatively delivering products of the highest
possible value.

4. consists of
scrum
Scrum Team & their associated roles
Events
Artifacts
Rules
noun
a framework within which people can address
complex adaptive problems, while productively
and creatively delivering products of the highest
possible value.

5. Scrum Theory
is founded on empirical process control theory,
or empiricism. Empiricism asserts that
knowledge comes from experience and making
decisions based on what is known. Scrum
employs an iterative, incremental approach to
optimize predictability and control risk.

6. based on
Transparency
Inspection
Adaptation
Scrum Theory
is founded on empirical process control theory,
or empiricism. Empiricism asserts that
knowledge comes from experience and making
decisions based on what is known. Scrum
employs an iterative, incremental approach to
optimize predictability and control risk.

7. based on
Transparency
Inspection
Adaptation
empirical process control theory,
m. Empiricism asserts that
omes from experience and making
ed on what is known. Scrum
erative, incremental approach to
dictability and control risk.
Significant aspects of the
process must be visible
to those responsible to
the outcome.
Requires to define those
aspects in a common
standard so observers
share a common
understanding of what is
being seen.
(e.g. common language,
definition of “Done”)

8. based on
Transparency
Inspection
Adaptation
empirical process control theory,
m. Empiricism asserts that
omes from experience and making
ed on what is known. Scrum
erative, incremental approach to
dictability and control risk.
Scrum users must
frequently inspect Scrum
artifacts and progress
toward a Sprint Goal to
detect undesirable
variances.

9. Estimation Variability
4x
2x
1.5x
1.25x
1.0x
0.8x
0.67x
time
0.5x
Detailed Software
Design
Detailed UI
Design Ready
0.25x
Initial
Concept
Requirements
Complete
Product
Definition
Software
Complete

10. Associated Costs/Value
Costs
Strategy
Value

11. Associated Costs/Value
Costs
Strategy
Trivia
Value

12. Associated Costs/Value
Costs
Consultancy
Trivia
Strategy
???
Value

13. Associated Costs/Value
Costs
Consultancy
Trivia
Strategy
Design Detail
Value

14. based on
Transparency
Inspection
Adaptation
empirical process control theory,
m. Empiricism asserts that
omes from experience and making
ed on what is known. Scrum
erative, incremental approach to
dictability and control risk.
If an inspector determines
that an aspect of a process
deviates outside acceptable
limits, an adjustment must
be made ASAP to minimize
further deviation.
4 formal events for
inspection and adaptation:
1. Sprint Planning.
2. Daily Scrum.
3. Sprint Review.
4. Sprint Retrospective.

15. consists of
m
Scrum Team
Events
Artifacts
Rules
Product Owner
Responsible for:
• maximizing the value of the product
• accountable for the Product success
and...
• maintains the Product Backlog
Dev Team
Professionals who do the work of
delivering potentially releasable
increment of “Done” product at the
end of the Sprint.
framework within which people can address
omplex adaptive problems, while productivelyScrum Master
Responsible for:
nd creatively delivering products of the highestensuring Scrum is understood and
•
enacted
ossible value.
• helps the Product Owner find
techniques for effective Product
Backlog management
• facilitating Scrum events
• remove impediments to the Dev
Team progress

16. consists of
m
Scrum Team
Events
Artifacts
Rules
The Sprint
Time-box of month or less during
which a “Done” product increment is
created.
Sprint Planning
Time-boxed to a day. Answers the
following:
• What can be delivered in the
Increment from the upcoming Sprint?
• How will the work needed to deliver
the Increment be achieved?
framework within which people can address
Daily Scrum
omplex adaptive problems, while productively
15 minute time-boxed event for the Dev
nd creatively delivering products of the Team to sync.
highest
Sprint Review
ossible value.
Max. 4 hour time-boxed meeting held
at the end of the Sprint.
Sprint Retrospective
Max. 3 hour time-boxed meeting held
at the end of the Sprint.

17. Scrum Team
Events
Artifacts
Rules
The Sprint
Time-box of month or less during
which a “Done” product increment is
created.
Sprint Planning
Time-boxed to a day. Answers the
following:
• What can be delivered in the
Increment from the upcoming Sprint?
• How will the work needed to deliver
the Increment be achieved?
which people can address
Daily Scrum
blems, while productively
15 minute time-boxed event for the Dev
ing products of the Team to sync.
highest
Sprint Review
Max. 4 hour time-boxed meeting held
at the end of the Sprint.
Sprint Retrospective
Max. 3 hour time-boxed meeting held
at the end of the Sprint.
Sprint Goal
After the Dev Team forecasts the
Product Backlog items it will deliver in
the Sprint, the Scrum Team crafts a
Sprint Goal. The Sprint Goal is an
objective that will be met within the
Sprint through the implementation of
the Product Backlog, and it provides
guidance to the Dev Team on why it is
building the Increment.

18. consists of
m
Scrum Team
Events
Artifacts
Rules
Product Backlog
• ordered list of everything that might
be needed in the product
• single source of requirements for any
changes
• dynamic and never complete
• lays out the initially known and bestunderstood requirements
• each item has a description, order,
estimate and value
framework within which people can address
Sprint Backlog
• subset of the Product Backlog
omplex adaptive problems, while productively sprint
selected for the
• plan for delivering the product
nd creatively delivering products of theIncrement and realizing the Sprint
highest
Goal
ossible value.
• it’s a forecast of the Dev Team
• plan with enough detail that changes
in progress
Increment

19. consists of
m
Scrum Team
Events
Artifacts
Rules
No changes are made that would
endanger the Sprint Goal
Quality goals do not decrease
Scope may be clarified and renegotiated between the Product
Owner and the Dev Team as more
is learned
framework within which people can address
omplex adaptive problems, while productively
nd creatively delivering products of the highest
ossible value.

20. END NOTE
Scrum’s roles, artifacts, events and rules are immutable and although
implementing only part of Scrum is possible, the result is not Scrum. Scrum
exists only in its entirety and functions well as a container for other
techniques, methodologies, and practices.