An Introduction to Scrum

in 20 Minutes

Bill Hoberecht
billh@pmonotebook.com

Copyright © 2021 Pinnacle Projects, LLC.

ALL RIGHTS RESERVED
 What is Scrum?

• Scrum is a lightweight & incremental framework

– The Scrum Guide contains the definition of Scrum.
– Each element of the framework serves a specific purpose that is essential to Scrum.
– Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum,
covers up problems and limits the benefits of Scrum.

• Appling Scrum to your work

– Roots in software product development.
• Is used in other endeavors
– Created for complex situations, with unknowns.
• Evidence-based empirical approach – learn and adapt

• This presentation is about the definition of Scrum. Omitted are:

– The origin and history of Scrum and its relationship with the Agile Manifesto
– Applicability of Scrum for your efforts
– Details noted in the official Scrum Guide
– Implementation tips
– Patterns and anti-patterns for Scrum implementation

Revised for Nov 2020 Update to the Scrum Guide. Slide 2

https://www.scrumguides.org/index.html
 Scrum Theory

• Scrum is founded on empiricism and lean thinking.

– No guessing. Knowledge comes from making decisions based on observation.
– Lean thinking reduces waste and focuses on the essentials.

• An iterative approach optimizes predictability and controls risk.

• The empirical Scrum pillars:

– Transparency
• Work must be visible to those performing the work as well as those receiving the work.
• Important decisions are based on observation of the three Scrum artifacts.
• Transparency enables inspection.
– Inspection
• The Scrum artifacts and the progress toward agreed goals must be inspected frequently
to detect undesirable variances.
• Inspection enables adaptation.
– Adaptation
• When process deviation or product issues are detected, adjustments must be made.
• A Scrum Team is expected to adapt the moment it learns anything new through
inspection.

Slide 3
 Scrum Values

https://www.scrum.org/resources/scrum-values-poster Slide 4
 Overview

Daily
Scrum Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____ Sprint Sprint
5.____ Product
Planning • ____ Review Retrospective
6.____ Increment

7.____ • ____
8.____ …
9.____
…

Product Sprint Product

Backlog Backlog Increment

Revised for Nov 2020 Update to the Scrum Guide.

https://www.scrumguides.org/index.html
 SCRUM – A Lightweight Framework

1.____
2.____
3.____
4.____ • ____
5.____ • ____
6.____ • ____
7.____ • ____
8.____ …
9.____
…
 The Scrum Team

Scrum Team
• Small. <= 10
• Responsible – Product Work
• Self-Organizing
• Creates useful increment
every sprint

1.____
2.____
3.____
4.____ • ____
5.____ • ____
6.____ • ____
7.____ • ____
8.____ …
9.____
…
 The Scrum Team - Developers

Scrum Team
Developers
• Create Sprint backlog
• Quality – Done
• Adapt daily
• Mutually accountable

1.____
2.____
3.____
4.____ • ____
5.____ • ____
6.____ • ____
7.____ • ____
8.____ …
9.____
…
 The Scrum Team – Product Owner
Developers

Scrum Team
Product
Owner
• Maximizing value
• Create Product Goal
• Ordering Product Backlog

1.____
2.____
3.____
4.____ • ____
5.____ • ____
6.____ • ____
7.____ • ____
8.____ …
9.____
…
 The Scrum Team – Scrum Master
Developers

Product
Owner

Scrum Team
Scrum
Master
• Establishing Scrum
• Coaching
• Impediment removal
• Scrum Events

1.____
2.____
3.____
4.____ • ____
5.____ • ____
6.____ • ____
7.____ • ____
8.____ …
9.____
…
 The Scrum Team
Developers

Product
Owner

Scrum
Master Scrum Team

1.____
2.____
3.____
4.____ • ____
5.____ • ____
6.____ • ____
7.____ • ____
8.____ …
9.____
…
 Forming an Effective Scrum Team

• Team formation – Tuckman Model

– Forming (Scrum Master as teacher). Uncertainty.
– Storming (Coach). Challenging boundaries. Psychological safety.
– Norming (Mentor). Comfortable.
– Performing (Advisor). Supporting one another.

• Essentials
– (Nominally) Full time on the team
– Understanding of Scrum
– Alignment with Agile methods of operation
– Skills will contribute to the team’s goals

• Team Composition
– (Ideally) Cross functional
– Right-sized for the anticipated work demand

Slide 12
 The Sprint - Product Backlog
Developers

Product
Owner

Scrum
Master Scrum Team

1.____
2.____
3.____
4.____ • ____
5.____ • ____
6.____ • ____
7.____ • ____
8.____ …
9.____
…

Product
Backlog
 The Sprint - Product Backlog
Developers

Product
Owner

Scrum
Master Scrum Team

1.____
2.____
3.____
4.____ • ____
5.____ • ____
6.____ • ____
7.____ • ____
8.____ …
9.____
…

Product
Backlog
• Product Goal
• Ordered list
• Single source of work
• Ready?
• Developers perform sizing
 The Sprint – Sprint Planning
Developers

Product
Owner

Scrum
Master Scrum Team

1.____
2.____
3.____
4.____ • ____
Sprint • ____
5.____
6.____ Planning • ____
7.____ • ____
8.____ …
9.____
…

Product
Backlog
 The Sprint – Sprint Planning
Developers

Product
Owner

Scrum
Master Scrum Team

1.____
2.____
3.____
4.____ • ____
Sprint • ____
5.____
6.____ Planning • ____
7.____ • Why is this Sprint •Valuable?
____
8.____ …
• What can be Done in this Sprint?
9.____ • How will the chosen work get done?
…

Product
Backlog
 Be Vigilant for Anti-Patterns – Sprint Planning

• Populating the Sprint Backlog as a “wish list” and not a commitment

• Ignoring the team’s measured and demonstrated capacity
• Pressure to accept “stretch” items into the Sprint Backlog
• Continually deferring technical debt repayment
• Ad hoc guessing at item size
• A “team lead” pre-plans and uses Sprint Planning to assign work
• Unable to construct a Sprint Goal to rally around
• Defaulting a carry forward (into this Sprint) of Sprint Backlog items from the
prior sprint.
• Insufficient preparation of the Product Backlog prior to Sprint Planning
• Product Owner specifies “how” and/or “who”
• Ignoring or dogmatically applying the Definition of Ready

Slide 17
 The Sprint – Sprint Backlog
Developers

Product
Owner

Scrum
Master Scrum Team

1.____
2.____
3.____
4.____ • ____
Sprint • ____
5.____
6.____ Planning • ____
7.____ • ____
8.____ …
9.____
…

Product Sprint
Backlog Backlog
 The Sprint – Sprint Backlog
Developers

Product
Owner

Scrum
Master Scrum Team

1.____
2.____
3.____
4.____ • ____
Sprint • ____
5.____
6.____ Planning • ____
7.____ • ____
8.____ …
9.____
…

Product Sprint
Backlog Backlog
• Sprint Goal
• Planned by Developers
 The Sprint
Developers

Product
Owner

Scrum
Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____
5.____
6.____ Planning • ____
7.____ • ____
8.____ …
9.____
…

Product Sprint
Backlog Backlog
 The Sprint
Developers

Product
Owner

Scrum
Master Scrum Team

Sprint
• 1 Month or less
1.____ • Sprint Goal is protected
2.____ • Quality does not decrease
3.____ • Scope may be clarified
4.____ • ____
Sprint • ____
5.____
6.____ Planning • ____
7.____ • ____
8.____ …
9.____
…

Product Sprint
Backlog Backlog
 Be Vigilant for Anti-Patterns – The Sprint

• Product Owner is not present for Sprint Backlog conversations and

clarifications
• Excessive Work in Progress (no WIP limits)
• The Scrum Board is not kept current
• The Team works on issues that are not in the Sprint Backlog
• Team members are diverted (typically by management) to other work
• The Scrum Master passively allows the agreed process to be subverted
• Impediments that can be resolved by a Development Team member are
instead taken on by the Scrum Master
• Unmanaged additions or deletions to the Sprint Backlog
• The presence of a “hardening sprint” (potentially signaling the incomplete
application of the Definition of Done)
• Absence of value in a Product Increment at the sprint conclusion

Slide 22
 The Sprint – Daily Scrum
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____
5.____
6.____ Planning • ____
7.____ • ____
8.____ …
9.____
…

Product Sprint
Backlog Backlog
 The Sprint – Daily Scrum
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team
• Inspect Progress
• Adapt
• 15-minutes
• Communications,
Impediments,
decision making

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____
5.____
6.____ Planning • ____
7.____ • ____
8.____ …
9.____
…

Product Sprint
Backlog Backlog
 Be Vigilant for Anti-Patterns – Daily Scrum

• Regresses to Project Management methods

– It becomes a status meeting for a project leader

• Inspection doesn’t happen

– Lackluster sharing of information (“I was in meetings and then worked on a few tickets.”)

• Inspection happens, but adapting doesn’t

– Missed signals of needed support
– Seeming acceptance of problems with no “adapt” actions

• Lack of focus on the meeting goals and agenda

– It becomes a working session to resolve issues

• Engagement
– Perennial late arrivals
– Insufficient preparation by the team – superficial information sharing
– Multi tasking – missed opportunities to listen and contribute

Slide 25
 The Sprint - Product Increment
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____
5.____ Product
6.____ Planning • ____ Increment

7.____ • ____
8.____ …
9.____
…

Product Sprint Product

Backlog Backlog Increment
 The Sprint - Product Increment
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____
5.____ Product
6.____ Planning • ____ Increment

7.____ • ____
8.____ …
9.____
…

Product Sprint Product

Backlog Backlog Increment
• A step towards Product Goal
• Definition of Done
 The Sprint – Sprint Review
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____ Sprint
5.____ Product
6.____ Planning • ____ Increment Review
7.____ • ____
8.____ …
9.____
…

Product Sprint Product

Backlog Backlog Increment
 The Sprint – Sprint Review
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____ Sprint
5.____ Product
6.____ Planning • ____ Increment Review
7.____ • ____ • Inspect Sprint
8.____ … outcome
9.____ • Adapt
… • 4-hour max

Product Sprint Product

Backlog Backlog Increment
 Be Vigilant for Anti-Patterns – Sprint Review

• Reviews are not conducted

• Stakeholders never or rarely participate
• The review is used for Product Owner acceptance of Sprint Backlog items
• Surprises at the Review – new “requirements” by the PO, bonus features
delivered by the team
• Demonstrating items that haven’t satisfied the Definition of Done

Slide 30
 The Sprint – Sprint Retrospective
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____ Sprint Sprint
5.____ Product
Planning • ____ Review Retrospective
6.____ Increment

7.____ • ____
8.____ …
9.____
…

Product Sprint Product

Backlog Backlog Increment
 The Sprint – Sprint Retrospective
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____ Sprint Sprint
5.____ Product
Planning • ____ Review Retrospective
6.____ Increment

7.____ • ____ • Increase quality

8.____ … & effectiveness
9.____ • What went
… well?
• Problems?
Product • Helpful
Product Sprint changes.
Backlog Backlog Increment • 3-hour max
 Be Vigilant for Anti-Patterns – Sprint Retrospective

• Retrospectives are not conducted

– “There’s no need for us to improve”
– “We don’t have time given all the pressures on us”

• A vocal few people dominate the participation

• Some individuals never speak up
• It becomes a rote exercise with little value
• Repeated complaining about topics that are outside of the team’s control
• No reviews of agreed actions from past retrospectives
• Improvement actions are rarely identified
• Identification of actions is vague (and perhaps not actionable)

Slide 33
 Extras Commonly Associated with Scrum Implementations

• User Stories
• The “three questions” answered in a Daily Scrum
• Backlog Grooming, Backlog Refinement
• Velocity
• Burn-down, Burn-up (mentioned but not part of the Scrum definition)
• Scrum of Scrums
• Minimum Viable Product (MVP)
• Spike
• Hardening Sprint

Slide 34
 3 Artifacts
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____ Sprint Sprint
5.____ Product
Planning • ____ Review Retrospective
6.____ Increment

7.____ • ____
8.____ …
9.____
…

Product Sprint Product

Backlog Backlog Increment
 3 Accountabilities
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____ Sprint Sprint
5.____ Product
Planning • ____ Review Retrospective
6.____ Increment

7.____ • ____
8.____ …
9.____
…

Product Sprint Product

Backlog Backlog Increment
 5 Events
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____ Sprint Sprint
5.____ Product
Planning • ____ Review Retrospective
6.____ Increment

7.____ • ____
8.____ …
9.____
…

Product Sprint Product

Backlog Backlog Increment
 The Sprint - The Full Picture
Developers

Product
Owner

Daily Scrum
Scrum Master Scrum Team

Sprint

1.____
2.____
3.____
4.____ • ____
Sprint • ____ Sprint Sprint
5.____ Product
Planning • ____ Review Retrospective
6.____ Increment

7.____ • ____
8.____ …
9.____
…

Product Sprint Product

Backlog Backlog Increment
 Scrum Certifications

• Is a Scrum Certification beneficial for you?

– The training can be a useful immersive experience
– A certification is evidence of professional development

• Fractured certification landscape

– AgileAlliance – Certified ScrumMaster – CSM
– Scrum.Org – Professional Scrum Master – PSM
– ScaledAgile – SAFe® Scrum Master – SSM
– PMI - Agile Certified Practitioner (PMI-ACP)®

Slide 39
 What’s Next?

Try this activity:

• On a blank piece of paper, draw the Scrum Framework

• Label each Accountability, Artifact and Event.

Slide 40
 What’s Next?

Try this activity:

• On a blank piece of paper, draw the Scrum Framework

• Label each Accountability, Artifact and Event.

Slide 41
 Thank you!

Your Comments and Feedback are Appreciated

Please comment to billh@pmonotebook.com

Slide 42
 SCRUM – A Lightweight Framework
Developers
• Create Sprint backlog
Scrum Theory • Quality – Done
• Transparency • Adapt daily
• Inspection • Mutually accountable
• Adaptation
Daily Product
Scrum Owner Scrum Team
• Small. <= 10
• Inspect Progress • Maximizing value
Scrum Values • Responsible – Product Work
• Adapt • Create Product Goal • Self-Organizing
• Commitment • 15-minutes • Ordering Product Backlog
• Creates useful increment
• Focus • Communications,
every sprint
• Openness Impediments,
Scrum
• Respect decision making
Master
• Courage Sprint • Establishing Scrum
• 1 Month or less • Coaching
• Sprint Goal is protected • Impediment removal
1.____
• Quality does not decrease • Scrum Events
2.____
3.____ • Scope may be clarified
4.____ • ____
Sprint • ____ Sprint Sprint
5.____ Product
Planning • ____ Review Retrospective
6.____ Increment

7.____ • Why is this Sprint •Valuable?

____ • Inspect Sprint • Increase quality
8.____ …
• What can be Done in this Sprint? outcome & effectiveness
9.____ • How will the chosen work get done? • Adapt • What went
… • 4-hour max well?
• Problems?
Product • Helpful
Product Sprint changes.
Backlog Backlog Increment • 3-hour max
• Product Goal • Sprint Goal • A step towards Product Goal
• Ordered list • Planned by Developers • Definition of Done
• Single source of work
• Ready?
• Developers perform sizing
Revised for Nov 2020 Update to the Scrum Guide.
https://www.scrumguides.org/index.html