This document details the Scrum framework as outlined in the Scrum Guide, focusing on principles such as empiricism, transparency, and adaptation. It covers roles within a Scrum team, including the Product Owner and Development Team, and describes key events like Sprints, Sprint Planning, Daily Scrums, Sprint Reviews, and Retrospectives. Additionally, it outlines artifacts like the Product Backlog and Sprint Backlog, emphasizing the importance of transparency and a shared understanding of what 'done' means.

1. SCRUM BY PICTURE
2017

2. based on The Scrum GuideTM
November 2017
prepared by Paweł Lewiński

3. empiricism
- knowledge comes
from experience
- make decisions based
on what is known

4. THEORY

5. transparency
- the process visible to those
responsible for the outcome
- observers share a common
understanding of what
is being seen

6. inspection
frequently inspect:
- Scrum artifacts
- progress toward a Sprint Goal
to detect undesirable
variances

7. adaptation
if any aspect of a process
deviate outside acceptable
limits process must be adjusted
as soon as possible

8. VALUES

14. SCRUM TEAM

15. self-organizing
choose how best
to accomplish their work

16. cross-functional
have all competencies
needed to
accomplish
the work

17. Product Owner
- one person
- maximizing the value of the product
- managing the Product Backlog
- the entire organization must
respect PO decisions

18. Development Team
- professionals who do the work of delivering a potentially releasable
increment of "Done" product at the end of each Sprint
- empowered to organize and manage their own work
- 3 to 9 members
- no sub-teams
- no titles for members

19. - responsible for promoting and
supporting Scrum
- helping everyone understand Scrum
- servant-leader for the Scrum Team
- serves the Product Owner,
the Development Team and
the Organization
Scrum Master

20. EVENTS

21. Sprint
- time-box of one month or less
- creates useable, and potentially
releasable product Increment
new starts immediately
after the conclusion of the
previous

22. Sprint
- no changes are made
that would endanger the Sprint Goal
- quality goals do not decrease
- scope may be clarified and re-
negotiated

23. - what can be done this Sprint?
- how will the chosen
work get done?
- time-box of eight
hours or less
Sprint Planning

24. Sprint Goal
an objective set for the Sprint
that can be met through
the implementation of Product Backlog
- it provides guidance
- gives some flexibility
- As the Development
Team works, it keeps
the Sprint Goal in
mind

25. Sprint Planning: what
- Development Team forecast the
functionality that will be developed
- all collaborates on understanding
the work of the Sprint
- the number of items selected from
the Product Backlog is solely up to
the Development Team

26. Sprint Planning: how
- Development Team decides
how it will build this functionality
into a "Done" product
Increment
- The Product Backlog
items selected for this
Sprint plus the plan
for delivering them
is called the Sprint
Backlog
- enough work is
planned
- The Product Owner
can help to clarify the selected Product Backlog items

27. Daily Scrum
- 15-minute time-boxed
- Development Team plans
work for the next 24 hours
- inspect progress toward
the Sprint Goal
- the Development Team
should understand how it
intends to work together
as a self-organizing team
to accomplish the Sprint Goal
- an internal meeting for the
Development Team

28. Sprint Review
- the presentation of the Increment is intended to elicit feedback and
foster collaboration
- held at the end of the Sprint to inspect the Increment and adapt the
Product Backlog
- all collaborate about what was done in the Sprint
- result of the Sprint Review is a revised Product Backlog
- max four-hour meeting for one-month Sprints

29. Retrospective
- an opportunity for the Scrum Team
to inspect itself and create a plan
for improvements to be enacted
during the next Sprint
- occurs after the Sprint Review and prior
to the next Sprint Planning
- the Scrum Team plans ways
to increase product quality
by improving work processes
- max three-hour meeting for
one-month Sprints

30. ARTIFACTS

31. - an ordered list of everything that is known to be needed in the product
- The Product Owner responsibility
- dynamic; it constantly changes to identify what the product needs to be
appropriate, competitive, and useful
- higher ordered Product Backlog items are usually clearer and more
detailed than lower ordered ones
Product Backlog

32. Sprint Backlog
- the set of Product Backlog items
selected for the Sprint, plus a plan
for delivering the product Increment
and realizing the Sprint Goal
- includes at least one high priority
process improvement identified in
the previous Retrospective
- emerges during the Sprint
- belongs solely to the Development
Team

34. Artifact Transparency
- Scrum relies on transparency
- The Scrum Master’s job is to work with the Scrum Team
and the organization to increase the transparency
- Transparency doesn’t occur overnight, but is a path

35. Definition of "Done"
- everyone must understand what "Done" means
- Development Teams deliver an useable Increment of product
functionality every Sprint

36. Creative Commons License Attribution
This is a derivative work by Paweł Lewiński based on the Scrum Guide ©2017 by
Scrum.Org and ScrumInc, available at http://scrumguides.org. Offered for license
under the Attribution Share-Alike license of Creative Commons, accessible at
http://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in
summary form at http://creativecommons.org/licenses/by-sa/4.0/. By utilizing this
Scrum Guide you acknowledge and agree that you have read and agree to be
bound by the terms of the Attribution ShareAlike license of Creative Commons.
This work is not associated with Scrum.org nor Scrum Inc in any way.