SlideShare a Scribd company logo
1 of 36
SCRUM BY PICTURE
2017
based on The Scrum GuideTM
November 2017
prepared by Paweł Lewiński
empiricism
- knowledge comes
from experience
- make decisions based
on what is known
THEORY
transparency
- the process visible to those
responsible for the outcome
- observers share a common
understanding of what
is being seen
inspection
frequently inspect:
- Scrum artifacts
- progress toward a Sprint Goal
to detect undesirable
variances
adaptation
if any aspect of a process
deviate outside acceptable
limits process must be adjusted
as soon as possible
VALUES
SCRUM TEAM
self-organizing
choose how best
to accomplish their work
cross-functional
have all competencies
needed to
accomplish
the work
Product Owner
- one person
- maximizing the value of the product
- managing the Product Backlog
- the entire organization must
respect PO decisions
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
- 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
EVENTS
Sprint
- time-box of one month or less
- creates useable, and potentially
releasable product Increment
new starts immediately
after the conclusion of the
previous
Sprint
- no changes are made
that would endanger the Sprint Goal
- quality goals do not decrease
- scope may be clarified and re-
negotiated
- what can be done this Sprint?
- how will the chosen
work get done?
- time-box of eight
hours or less
Sprint Planning
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
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
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
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
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
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
ARTIFACTS
- 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
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
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
Definition of "Done"
- everyone must understand what "Done" means
- Development Teams deliver an useable Increment of product
functionality every Sprint
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.

More Related Content

What's hot

What's hot (20)

What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day? What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day?
 
Scrum 101: Introduction to Scrum
Scrum 101: Introduction to ScrumScrum 101: Introduction to Scrum
Scrum 101: Introduction to Scrum
 
Agile & SCRUM basics
Agile & SCRUM basicsAgile & SCRUM basics
Agile & SCRUM basics
 
What is scrum in Agile methodology?
What is scrum in Agile methodology?What is scrum in Agile methodology?
What is scrum in Agile methodology?
 
What Is Agile Scrum
What Is Agile ScrumWhat Is Agile Scrum
What Is Agile Scrum
 
Agile Methodology in Software Development
Agile Methodology in Software DevelopmentAgile Methodology in Software Development
Agile Methodology in Software Development
 
Agile Scrum software methodology
Agile Scrum software methodologyAgile Scrum software methodology
Agile Scrum software methodology
 
Scrum events
Scrum eventsScrum events
Scrum events
 
Understanding Scrum in 30 Minutes
Understanding Scrum in 30 MinutesUnderstanding Scrum in 30 Minutes
Understanding Scrum in 30 Minutes
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Agile Introduction - Scrum Framework
Agile Introduction - Scrum FrameworkAgile Introduction - Scrum Framework
Agile Introduction - Scrum Framework
 
Scrum In Ten Slides
Scrum In Ten SlidesScrum In Ten Slides
Scrum In Ten Slides
 
What is Scrum
What is ScrumWhat is Scrum
What is Scrum
 
Scrum in a nutshell
Scrum in a nutshellScrum in a nutshell
Scrum in a nutshell
 
Scrum
ScrumScrum
Scrum
 
Scrum framework
Scrum frameworkScrum framework
Scrum framework
 
Scrum
ScrumScrum
Scrum
 
Agile Scrum Quick Reference Card
Agile Scrum Quick Reference CardAgile Scrum Quick Reference Card
Agile Scrum Quick Reference Card
 
scrum
scrumscrum
scrum
 
Scrum In 15 Minutes
Scrum In 15 MinutesScrum In 15 Minutes
Scrum In 15 Minutes
 

Viewers also liked

Agile Methodology(SCRUM)
Agile Methodology(SCRUM)Agile Methodology(SCRUM)
Agile Methodology(SCRUM)
KhushSlideShare
 
Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.
SlideTeam.net
 
Introduction to Scrum.ppt
Introduction to Scrum.pptIntroduction to Scrum.ppt
Introduction to Scrum.ppt
Mohan Late
 
Overview of Agile Methodology
Overview of Agile MethodologyOverview of Agile Methodology
Overview of Agile Methodology
Haresh Karkar
 

Viewers also liked (16)

Scrum introduction
Scrum introductionScrum introduction
Scrum introduction
 
Scrum 101
Scrum 101 Scrum 101
Scrum 101
 
The Scrum Model
The Scrum ModelThe Scrum Model
The Scrum Model
 
Running a Scrum process with Trello
Running a Scrum process with TrelloRunning a Scrum process with Trello
Running a Scrum process with Trello
 
Learn Scrum Engineering in 5 minutes
Learn Scrum Engineering in 5 minutesLearn Scrum Engineering in 5 minutes
Learn Scrum Engineering in 5 minutes
 
Get Up! Stand Up!
Get Up! Stand Up!Get Up! Stand Up!
Get Up! Stand Up!
 
Agile Methodology(SCRUM)
Agile Methodology(SCRUM)Agile Methodology(SCRUM)
Agile Methodology(SCRUM)
 
Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.
 
Scrum by picture
Scrum by pictureScrum by picture
Scrum by picture
 
Scrum ppt
Scrum pptScrum ppt
Scrum ppt
 
Agile Software Development Overview
Agile Software Development OverviewAgile Software Development Overview
Agile Software Development Overview
 
Introduction to Scrum.ppt
Introduction to Scrum.pptIntroduction to Scrum.ppt
Introduction to Scrum.ppt
 
Agile Scrum Methodology
Agile Scrum MethodologyAgile Scrum Methodology
Agile Scrum Methodology
 
Agile Is the New Waterfall
Agile Is the New WaterfallAgile Is the New Waterfall
Agile Is the New Waterfall
 
Overview of Agile Methodology
Overview of Agile MethodologyOverview of Agile Methodology
Overview of Agile Methodology
 
AI and Machine Learning Demystified by Carol Smith at Midwest UX 2017
AI and Machine Learning Demystified by Carol Smith at Midwest UX 2017AI and Machine Learning Demystified by Carol Smith at Midwest UX 2017
AI and Machine Learning Demystified by Carol Smith at Midwest UX 2017
 

Similar to 2017 Scrum by Picture

Mod 6 - Agile Scrum in a nutshell.pdf
Mod 6 - Agile Scrum in a nutshell.pdfMod 6 - Agile Scrum in a nutshell.pdf
Mod 6 - Agile Scrum in a nutshell.pdf
LuongMinhHai
 

Similar to 2017 Scrum by Picture (20)

Management fundamentals scrum 101
Management fundamentals scrum 101Management fundamentals scrum 101
Management fundamentals scrum 101
 
What is Scrum?
What is Scrum?What is Scrum?
What is Scrum?
 
Présentation scrum
Présentation scrumPrésentation scrum
Présentation scrum
 
Présentation scrum
Présentation scrumPrésentation scrum
Présentation scrum
 
Agile Project Management – SCRUM Methodology
Agile Project Management – SCRUM MethodologyAgile Project Management – SCRUM Methodology
Agile Project Management – SCRUM Methodology
 
Scrum Presentation by Amir Rabinkhah.pptx
Scrum Presentation by Amir Rabinkhah.pptxScrum Presentation by Amir Rabinkhah.pptx
Scrum Presentation by Amir Rabinkhah.pptx
 
Scrum Overview
Scrum OverviewScrum Overview
Scrum Overview
 
Mod 6 - Agile Scrum in a nutshell.pdf
Mod 6 - Agile Scrum in a nutshell.pdfMod 6 - Agile Scrum in a nutshell.pdf
Mod 6 - Agile Scrum in a nutshell.pdf
 
Scrum: Scrum Guide Summary
Scrum: Scrum Guide SummaryScrum: Scrum Guide Summary
Scrum: Scrum Guide Summary
 
Introduction Professional Scrum Developer for Java
Introduction Professional Scrum Developer for JavaIntroduction Professional Scrum Developer for Java
Introduction Professional Scrum Developer for Java
 
Let’s Play Agile ! 12-09-15-testers_hub
Let’s  Play  Agile ! 12-09-15-testers_hubLet’s  Play  Agile ! 12-09-15-testers_hub
Let’s Play Agile ! 12-09-15-testers_hub
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Unit III Scrum Events.pptx for Agile software
Unit III Scrum Events.pptx for Agile softwareUnit III Scrum Events.pptx for Agile software
Unit III Scrum Events.pptx for Agile software
 
Agile & SCRUM - Deep Dive for General Assembly
Agile & SCRUM - Deep Dive for General AssemblyAgile & SCRUM - Deep Dive for General Assembly
Agile & SCRUM - Deep Dive for General Assembly
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Agile Methodologies: Introduction to Scrum .
Agile Methodologies: Introduction to Scrum .Agile Methodologies: Introduction to Scrum .
Agile Methodologies: Introduction to Scrum .
 
Scrum Pocket Edition - Cas2k14
Scrum Pocket Edition - Cas2k14Scrum Pocket Edition - Cas2k14
Scrum Pocket Edition - Cas2k14
 
An introduction to Agile & Scrum
An introduction to Agile & ScrumAn introduction to Agile & Scrum
An introduction to Agile & Scrum
 
Scrum Process
Scrum ProcessScrum Process
Scrum Process
 
Introduction to scrum
Introduction to scrumIntroduction to scrum
Introduction to scrum
 

Recently uploaded

Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptxHarnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
FIDO Alliance
 
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider  Progress from Awareness to Implementation.pptxTales from a Passkey Provider  Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
FIDO Alliance
 

Recently uploaded (20)

WebRTC and SIP not just audio and video @ OpenSIPS 2024
WebRTC and SIP not just audio and video @ OpenSIPS 2024WebRTC and SIP not just audio and video @ OpenSIPS 2024
WebRTC and SIP not just audio and video @ OpenSIPS 2024
 
Extensible Python: Robustness through Addition - PyCon 2024
Extensible Python: Robustness through Addition - PyCon 2024Extensible Python: Robustness through Addition - PyCon 2024
Extensible Python: Robustness through Addition - PyCon 2024
 
State of the Smart Building Startup Landscape 2024!
State of the Smart Building Startup Landscape 2024!State of the Smart Building Startup Landscape 2024!
State of the Smart Building Startup Landscape 2024!
 
Overview of Hyperledger Foundation
Overview of Hyperledger FoundationOverview of Hyperledger Foundation
Overview of Hyperledger Foundation
 
ADP Passwordless Journey Case Study.pptx
ADP Passwordless Journey Case Study.pptxADP Passwordless Journey Case Study.pptx
ADP Passwordless Journey Case Study.pptx
 
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptxHarnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
Harnessing Passkeys in the Battle Against AI-Powered Cyber Threats.pptx
 
The Value of Certifying Products for FDO _ Paul at FIDO Alliance.pdf
The Value of Certifying Products for FDO _ Paul at FIDO Alliance.pdfThe Value of Certifying Products for FDO _ Paul at FIDO Alliance.pdf
The Value of Certifying Products for FDO _ Paul at FIDO Alliance.pdf
 
Top 10 CodeIgniter Development Companies
Top 10 CodeIgniter Development CompaniesTop 10 CodeIgniter Development Companies
Top 10 CodeIgniter Development Companies
 
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdfIntroduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
Introduction to FDO and How It works Applications _ Richard at FIDO Alliance.pdf
 
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider  Progress from Awareness to Implementation.pptxTales from a Passkey Provider  Progress from Awareness to Implementation.pptx
Tales from a Passkey Provider Progress from Awareness to Implementation.pptx
 
Long journey of Ruby Standard library at RubyKaigi 2024
Long journey of Ruby Standard library at RubyKaigi 2024Long journey of Ruby Standard library at RubyKaigi 2024
Long journey of Ruby Standard library at RubyKaigi 2024
 
Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf
Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdfSimplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf
Simplified FDO Manufacturing Flow with TPMs _ Liam at Infineon.pdf
 
Event-Driven Architecture Masterclass: Engineering a Robust, High-performance...
Event-Driven Architecture Masterclass: Engineering a Robust, High-performance...Event-Driven Architecture Masterclass: Engineering a Robust, High-performance...
Event-Driven Architecture Masterclass: Engineering a Robust, High-performance...
 
How we scaled to 80K users by doing nothing!.pdf
How we scaled to 80K users by doing nothing!.pdfHow we scaled to 80K users by doing nothing!.pdf
How we scaled to 80K users by doing nothing!.pdf
 
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdfWhere to Learn More About FDO _ Richard at FIDO Alliance.pdf
Where to Learn More About FDO _ Richard at FIDO Alliance.pdf
 
Generative AI Use Cases and Applications.pdf
Generative AI Use Cases and Applications.pdfGenerative AI Use Cases and Applications.pdf
Generative AI Use Cases and Applications.pdf
 
Intro in Product Management - Коротко про професію продакт менеджера
Intro in Product Management - Коротко про професію продакт менеджераIntro in Product Management - Коротко про професію продакт менеджера
Intro in Product Management - Коротко про професію продакт менеджера
 
Collecting & Temporal Analysis of Behavioral Web Data - Tales From The Inside
Collecting & Temporal Analysis of Behavioral Web Data - Tales From The InsideCollecting & Temporal Analysis of Behavioral Web Data - Tales From The Inside
Collecting & Temporal Analysis of Behavioral Web Data - Tales From The Inside
 
Introduction to FIDO Authentication and Passkeys.pptx
Introduction to FIDO Authentication and Passkeys.pptxIntroduction to FIDO Authentication and Passkeys.pptx
Introduction to FIDO Authentication and Passkeys.pptx
 
TopCryptoSupers 12thReport OrionX May2024
TopCryptoSupers 12thReport OrionX May2024TopCryptoSupers 12thReport OrionX May2024
TopCryptoSupers 12thReport OrionX May2024
 

2017 Scrum by Picture

  • 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
  • 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
  • 9.
  • 10.
  • 11.
  • 12.
  • 13.
  • 15. self-organizing choose how best to accomplish their 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
  • 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
  • 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
  • 33.
  • 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.