SCRUM - TOOLBOX
SCRUM – DEFINITION
A framework within which people can
address complex adaptive problems,
while productively and creatively delivering
products of the highest possible value.
Ken Schwaber / Jeff Sutherland
SCRUM – DEFINITION Properly implemented,
Scrum will:
Scrum is an agile method designed to add energy, focus,
clarity, and transparency to project planning and Increase speed of development
implementation. Today, Scrum is used in small,
mid-sized and large software corporations Align individual and corporate
all over the world. objectives
24 h Create a culture driven by
performance
SPRINT
Support shareholder value creation
1-4 WEEKS
Achieve stable and consistent
communication of performance
at all levels
Enhance individual development
and quality of life
SCRUM – DEFINITION
M
LIGHTWEIGHT SIMPLE TO DIFFICULT
UNDERSTAND TO MASTER
SCRUM – THEORY
TRANSPARENCY INSPECTION ADAPTION
Main aspects of the process must be Scrum users must frequently inspect Process or the material being processed
defined by a common standard. Scrum artifacts and progress towards a must be adjusted if an inspection
Sprint Goal. determines that one or more aspects of a
A common language that refers to the process deviate outside acceptable limits
process has to be shared by all Inspections should not be so frequent that and the resulting product will be
participants. they get in the way of the work. unacceptable.
A common definition of „Done“ for those Inspections are most effective when Sprint Planning
performing work and accepting the work diligently performed by skilled inspectors
product. at the point of work. Daily Scrum
Sprint Review
Sprint Retrospective
SCRUM TEAM
SCRUM – TEAM
Scrum Teams are self-organizing and cross-functional
PRODUCT OWNER DEVELOPMENT TEAM SCRUM MASTER
A person responsible for maximizing the Consists of professionals who do the A person ensuring that Scrum is
value of the product and the work of the work for delivering a potentially understood and enacted. Sets up
releasable Increment of „Done“ meetings and monitors everything.
Development Team (Product Backlog product at the end of each Sprint.
and determination of priorities) Self-organizing, cross-functional
SCRUM – PRODUCT OWNER ROLES Incubator / Colocation
Joint backlog grooming
Vision and roadmap Joint meetings
Empowerment
Budget Personas
Feedback
Business model Data through exposing
Revenues sources increments to user
Cost structure
Channels
User stories and sketches
Product backlog / product canvas
SCRUM – SCRUM MASTER ROLES Meetings / Scrum Principles
Team’s release planning
Face to face communication Team bonding activities
Team’s self organization Definition of Done
Transparency / Openness Continuous self-learning
Adaptability of change Coach / Consult team
Exchange experience / Feedback
Monitoring & Tracking Supporting team monitoring metrics
(Burndown Chart / Status Boards)
Mediate and resolve Conflicts
Management reporting, Shield of the team
performance feedback and Protect team of impediments
and obstacles from outside
process improvement
Maintaining Scrum tool
Appreciate great work
Take pride in the good work done
Celebrate success
SCRUM – TEAM • Coaching in self-organization and teamwork and removing
impediments from the Development Team
Supporting activities
• Helps the Development Team to create high-value products
• Facilitates Scrum implementation
PRODUCT OWNER DEVELOPMENT TEAM SCRUM MASTER ORGANIZATION
• Finding techniques for effective Product Backlog • Leading and coaching the organization in its Scrum
management adaption, planning Scrum implementation within the
organization
• Helping the Scrum Team understand the need for clear and
concise Product Backlog items • Helping employees and stakeholders understand and enact
Scrum and empirical product development
• Facilitates Scrum implementation
SCRUM – TEAM
Self-organizing and inter-disciplinary
PRODUCT OWNER DEVELOPMENT TEAM SCRUM MASTER
A person responsible for maximizing Consists of professionals who do the A person ensuring that Scrum is
the value of the product and the work work for delivering a potentially understood and enacted. Sets up
releasable Increment of „Done“ meetings and monitors everything
of the Development Team product at the end of each Sprint.
(Product Backlog and determination Self-organizing, cross-function
of priorities)
SCRUM – TEAM • Coaching in self-organization and teamwork and removing
impediments from the Development Team
Supporting activities
• Helps the Development Team to create high-value products
• Facilitates Scrum implementation
PRODUCT OWNER DEVELOPMENT TEAM SCRUM MASTER ORGANIZATION
• Finding techniques for effective Product Backlog • Leading and coaching the organization in its Scrum
management adaption, planning Scrum implementation within the
organization
• Helping the Scrum Team understand the need for clear and
concise Product Backlog items • Helping employees and stakeholders understand and enact
Scrum and empirical product development
• Facilitates Scrum implementation
SCRUM – EVENTS
Pre-described events are used in Scrum to create regularity and to minimize
the need for meetings not defined in Scrum
All events are time-boxed events with a maximum
duration
Once a Sprint begins, its duration is fixed and
cannot be shortened or lengthened
An appropriate amount of time is spent without
allowing waste in the process
SCRUM – SPRINT MAX.
Heart of the Scrum Process 4 WEEKS
Time Box of max. 4 weeks or less
During this period a „Done“, useable and potentially
releasable product increment is created
All Sprints have the same duration, a new Sprint starts
immediately after the conclusion of the previous one
SCRUM – SPRINT CANCELLATION
A Sprint can be cancelled before the Sprint time-box is over
Company changes direction or if market
or technology conditions change
Sprint goal has become obsolete
All „Done“ Product Backlog items are reviewed. If part of the work is
potentially releasable, the Product Owner accepts it. All incomplete Product
Backlog items are re-estimated and put back on the Product Backlog.
SCRUM – THE 5 DYSFUNCTIONS
Use SCRUM to remove team dysfunctions
• Always focus on individual performances than the whole team performance. Inattention
• Get easily distracted and lose achievement-oriented employees. to Results
• Encourage mediocre performance from the team members Avoidance of
and usually miss key deadlines. Accountability
• Lack motivation to complete the tasks on time.
• Create ambiguity about direction. Lack of Commitment
• Spend a lot of time on analysis.
• Hesitate to engage in healthy conflicts. Fear of Conflict
• Hiding weaknesses from each other. Absence of Trust
• Hesitate to request for help.
SCRUM – THE 5 VALUES OF SCRUM
Teams implementing the Scrum framework the right way, strongly adhere to its five values
Retaining focus, the teams pay close FOCUS
attention to the results OPENNESS
COMMITMENT
Being very open, the teams hold COURAGE
each other accountable RESPECT
Being committed, the team members ensure
that the whole team is committed
Having the courage to engage each other,
the team members involve in healthy conflicts
The team members earn respect by building
trust among the teams
SCRUM PROCESS
SCRUM – PROCESS (3D)
SCRUM – PROCESS (3D)
PRE-GAME STAGING DEVELOPMENT SPRINTS WRAPPER SPRINT
SPRINT
SCRUM – PROCESS (3D)
SCRUM – PROCESS
Inputs from End-Users, BURNDOWN / UP DAILY STANDUP
Customers, Team and CHARTS MEETING
Stakeholders SCRUM MASTER
PRODUCT
BACKLOG
REFINEMENT
Every
24h
PRODUCT OWNER THE TEAM REVIEW
1 SELECTS HOW SPRINT
2 MUCH TO
3 COMMIT To Do 1-4 WEEKS
4 BY SPRINT’S END
5 FINISHED WORK
6 SPRINT
7 PLANNING RETROSPECTIVE
8 MEETING
PRODUCT SPRINT Sprint end date, goal and team
BACKLOG BACKLOG deliverable do not change
SCRUM – PROCESS
From product planning to “shippable increment”
SPRINT 24h
SHIPPABLE
INCREMENT
SCRUM – PROCESS 24h
SPRINT BACKLOG
• Features assigned to Sprint
• Estimated by team
• Team Commitment
SPRINT
TIME-BOX
PRODUCT BACKLOG WORKING CODE READY
BACKLOG TASKS FOR DEPLOYMENT
SPRINT PLANNING MEETING DAILY SCRUM MEETINGS SPRINT REVIEW MEETINGS
• Review Product Backlog • Done since last meeting • Demo features to all
• Estimate Sprint Backlog • Plan for today • Retrospective on the Sprint
• Commit • Accelerators / Roadblocks
adjustments
SCRUM – PROCESS 24h
SPRINT BACKLOG
• Features assigned to Sprint
• Estimated by team
• Team Commitment
SPRINT
TIME-BOX
PRODUCT BACKLOG WORKING CODE READY
BACKLOG TASKS FOR DEPLOYMENT
SPRINT PLANNING MEETING DAILY SCRUM MEETINGS SPRINT REVIEW MEETINGS
• Review Product Backlog • Done since last meeting • Demo features to all
• Estimate Sprint Backlog • Plan for today • Retrospective on the Sprint
• Commit • Accelerators / Roadblocks
adjustments
SCRUM – PROCESS DAILY STANDUP
MEETING
Inputs from End-Users, REVIEW
Customers, Team and
FINISHED WORK
Stakeholders
RETROSPECTIVE
SCRUM MASTER
24h
PRODUCT OWNER THE TEAM
1 SELECTS HOW TASK SPRINT
2 MUCH TO BREAKOUT
3 1-4 WEEKS
4 PRIORITIZED COMMIT To Do BY SPRINT
5 FEATURE SPRINT’S END BACKLOG
6 LIST
7 SPRINT
8 PLANNING
MEETING
PRODUCT BACKLOG
Sprint end date, goal and team
deliverable do not change
SCRUM – PROCESS
Sprint includes Sprint Planning, Daily Scrums, Development & Test and Sprint Review
• Feedback AGILE
• Self-reflection COACH
• Celebration
• Improvement SPRINT 24h SCRUM
TEAM
• Product increment 4 WEEKS SCRUM MASTER
• Product integration • Planning
• Sprint Backlog
• Distribution of workstations
• Building of product backlog
• Configuration of development
environment
INITIAL PHASE WORKING INCREMENT
PRODUCT OWNER
SCRUM – PROCESS
Agile Scrum method at a glance
VISION
PRODUCT BACKLOG SPRINT PLANNING SPRINT BACKLOG
DAILY SCRUM
STAKEHOLDER RETROSPECTIVE NEW FUNCTIONALITY
PRODUCT OWNER
SCRUM MASTER
TEAM
SCRUM – ROLES SCRUM PROCESS
ROLES
SCRUM
ROLES This is a placeholder text. This text can
be replaced with your own text.
STAKEHOLDERS
USERS The text demonstrates how your own
TEAM text will look when you replace the
MEMBERS placeholder with your own text.
If you don’t want to use the style and
size of the fonts as used in this
placeholder it is possible to replace it
by selecting different options.
SCRUM – PROCESS
SPRINT DAILY SCRUM /
PLANNING DAILY WORK
MEETING
PREPARATION
• Business case & funding UPDATE RELEASE n
• Contractual agreement PRODUCT
• Vision BACKLOG PRODUCT
• Initial product backlog OWNER
• Initial release plan SCRUM PRODUCT
• Stakeholder buy-in PROCESS INCREMENT
• Assemble team
PRODUCT SPRINT SCRUM
BACKLOG RETROSPECTIVE MASTER
IMPEDIMENT PRODUCT BACKLOG SPRINT TEAM
LIST BURNDOWN REVIEW MEMBERS
PRODUCT BACKLOG SPRINT USERS
DELTA REPORT BACKLOG STAKEHOLDERS
SPRINT
BACKLOG
BURNDOWN
SCRUM – PROCESS OVERVIEW
SPRINT DAILY SCRUM / SPRINT PLANNING
PLANNING DAILY WORK MEETING
MEETING
The work to be performed during the
UPDATE Sprint is planned at the Sprint Planning
PRODUCT Meeting. Collaborative work of the
BACKLOG entire Scrum Team leads into a working
plan.
SCRUM PRODUCT
PROCESS INCREMENT What can be delivered in the Increment
resulting from the upcoming Sprint?
SPRINT
RETROSPECTIVE How will the work required to deliver
the Increment be achieved?
SPRINT
REVIEW
SCRUM – PROCESS OVERVIEW
SPRINT DAILY SCRUM / DAILY SCRUM CYCLE /
PLANNING DAILY WORK DAILY WORK
MEETING
The Daily Scrum is a 15-minute time-
UPDATE boxed event for the Development Team
PRODUCT to synchronize activities and create a
BACKLOG plan for the next 24 hours. Team
members explain:
SCRUM PRODUCT
PROCESS INCREMENT What did I do yesterday that helped the
Development Team meet the Sprint
SPRINT Goal?
RETROSPECTIVE
What will I do today to help the
SPRINT Development Team meet the Sprint
REVIEW Goal?
Do I see any stumbling blocks that
prevent me or the team from meeting
the Sprint Goal?
SCRUM – PROCESS OVERVIEW
SPRINT DAILY SCRUM / PRODUCT INCREMENT /
PLANNING DAILY WORK FINISHED WORK
MEETING
The Increment is the sum of all the
UPDATE Product Backlog items completed
PRODUCT during a Sprint, including the value of
BACKLOG the Increments of all previous Sprints.
At the end of a Sprint, the new
SCRUM PRODUCT Increment must be „Done“.
PROCESS INCREMENT
The product must be in a useable
SPRINT condition regardless of whether the
RETROSPECTIVE Product Owner decides to actually
release it.
SPRINT
REVIEW
SCRUM – PROCESS OVERVIEW
SPRINT DAILY SCRUM / SPRINT REVIEW
PLANNING DAILY WORK
MEETING A Sprint Review is held at the end of a
Sprint to inspect the Increment and
UPDATE adapt the Product Backlog if needed.
PRODUCT During this meeting, the Scrum Team
BACKLOG and stakeholders collaborate about
what was done in the Sprint.
SCRUM
PROCESS The Sprint Review is an informal
meeting, not a status meeting.
PRODUCT
INCREMENT
SPRINT
RETROSPECTIVE
SPRINT
REVIEW
SCRUM – PROCESS OVERVIEW
SPRINT DAILY SCRUM / SPRINT RETROSPECTIVE
PLANNING DAILY WORK
MEETING The Sprint Retrospective is an
opportunity for the Scrum Team to
UPDATE inspect and create a plan for
PRODUCT improvement to be carried out during
BACKLOG the next Sprint. The Sprint
Retrospective occurs after the Sprint
SCRUM PRODUCT Review and prior to the next Sprint
PROCESS INCREMENT Planning.
Purpose: Inspect how the last Sprint
went with regard to people,
relationships, process and tools.
SPRINT
RETROSPECTIVE
SPRINT
REVIEW
SCRUM – PROCESS OVERVIEW
SPRINT DAILY SCRUM / UPDATE PRODUCT
PLANNING DAILY WORK BACKLOG
MEETING
The Product Backlog is an ordered list
UPDATE of everything that might be necessary
PRODUCT in the product. It is the single source of
BACKLOG requirements of any changes to be
made to the product.
SCRUM PRODUCT
PROCESS INCREMENT The Product Backlog is dynamic, it is
never complete. It constantly changes
to identify what the product needs to
be appropriate, competitive and useful.
SPRINT
RETROSPECTIVE
SPRINT
REVIEW
SCRUM – PROCESS OVERVIEW
PRE-GAME (PHASE 1) MID-GAME (PHASE 2) POST-GAME (PHASE 3)
DEVELOP
PLANNING & WARP
HIGH LEVEL DESIGN
CLOSURE
ADJUST
REVIEW
SCRUM BOARD
SCRUM – COMMAND-AND-CONTROL VS. SELF-ORGANIZING
COMMAND AND CONTROL SELF-ORGANIZING TEAM
PROJECT SCRUM BOARD
MANAGER
Command: To Do OnGoing Done
Work assigned to the team
Control:
Project manager constantly
monitoring project progress
and updating plan
Everyone plans together
and takes on the work
that needs to be done
during the sprint
SCRUM – BOARD To Do LIST EMPTY
DOES NOT CHANGE QUEUES
WORK SELECTED
UPFRONT
To Do OnGoing Done To Do OnGoing Done To Do OnGoing Done
12 4 12 12
3 53 3
4 4
5 5
NO RESTRICTIONS TO THE ALL WORK DONE
NUMBER OF ONGOING ITEMS
SCRUM – BOARD Ongoing Done
To Do Description
Description text
text Description
text
Description Description Description Description
text text text text
Description Description Description Description
text text text text
Description Description
text text
SCRUM – BOARD Ongoing Done
To Do Description
Description text
text Description
text
Description Description Description Description
text text text text
Description Description Description Description
text text text text
Description Description
text text
SCRUM – BOARD
Story To Do In Progress To Verify Done
User need to Description Description Description Description Description
have the ability to… text text text text text
Description Description Description
text text text
User need to Description Description Description
have the ability to… text text text
Description
text Description
text
Task box colors according to priority
SCRUM – BOARD
To Do Ongoing Done Sprint Goal: Beta-Ready Release
DESCRIPTION DESCRIPTION Description BURNDOWN CHART
text
Description Description
text text 2000
1800
Description Description Description Work Remaining 1600
text text text 1400
1200
DESCRIPTION 1000 Projected
Finish
Description 800
text 600
400
200
0
1 Time 5 10 15
UNPLANNED ITEMS NEXT
Description
text
Description
text
Withdraw
SCRUM – BOARD
Stories To Do Ongoing Done
User need to DESCRIPTION Description DESCRIPTION Description Description
have the ability to… text text text
Description Description
text text Description
text
Description Description
text text Description
text
User need to DESCRIPTION DESCRIPTION
have the ability to… Description
Description Description Description text
text text text
SCRUM TEMPLATES
SCRUM – PRODUCT BACKLOG TEMPLATE
Prio Description Time (estimate) Company value
1 Description Task 1 2 50
2 Description Task 2 14 80
3 Description Task 3 1 40
4 Description Task 4 - 25
5 Description Task 5 5 30
6 Description Task 6 7 25
7 Description Task 7 2 10
The order of the entries determines the priority determined based on the business value
and respectively associated with a request risk.
SCRUM – PRODUCT BACKLOG TEMPLATE
SPRINT ID Backlog Item Owner Estimate (days) Remaining (days)
1 1 Task Description 1 TB 1 1
1 2 Task Description 2 TB 4 4
1 3 Task Description 3 TB 16 16
1 4 Task Description 4 AC 10 10
1 5 Task Description 5 FH 4 4
6 Task Description 6 AC 6 6
7 Task Description 7 AC 8 8
8 Task Description 8 TB 2
9 Task Description 9 BB 1
10 Task Description 10 TB 1
11 Task Description 11 BB 1
12 Task Description 12 AC 1
SCRUM – PRODUCT BACKLOG TEMPLATE
!!! ID Backlog Item Assigned to Due Status Hours
Estimate Actual
1 Task Description 1 None Day 10 Open 82
2 Task Description 2 TB Day 8 Open
3 Task Description 3 Day 12 Open 43
4 Task Description 4 None None Open
5 Task Description 5 None None Open 40
6 Task Description 6 None Open
7 Task Description 7 FH None Open 20
8 Task Description 8 AC None Open
9 Task Description 9 None None Open 10
10 Task Description 10 None None Open
11 Task Description 11 None None Open 20
None Total
None 40
20
27 5
SCRUM – IMPEDIMENT LIST TEMPLATE
Prio Description From Date Status Comments (Scrum Master)
1 After starting the Sprint, each team TB 14.02. Pending Comment
member can add Impediments
(Blocker) to the list. AC 10.02. Comment
2 The Scrum Master is responsible LA 08.02. Comment
for the removal of this blocker. TB 05.01 Comment
AC 22.01.
3 Impediment description 3 FH
4 Impediment description 4
5 Impediment description 5
6 Impediment description 6
7 Impediment description 7