3. Stacey Matrix
Certainty vs. Agreement
s/w development
is here…
Agreement
CertaintyHigh Low
High
Low
Political
Control -
Compromise
Standard
Guidance
Monitoring
Simple Complicate
Complex
Anarchy
Chaos
Experimenting
Innovation
Creativity
Debate
Trial & Error
Complicate
4. Empiricism & Lean Thinking
knowledge comes from experience and making
decisions based on what is observed.
5. Scrum Definition
Scrum is a lightweight framework that helps people, teams and organizations generate
value through adaptive solutions for complex problems.
In a nutshell, Scrum requires a Scrum Master to foster an environment where:
1. A Product Owner orders the work for a complex problem into a Product Backlog.
2. The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
3. The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
4. Repeat
The Scrum framework is purposefully incomplete, only defining the parts required to implement
Scrum theory. Scrum is built upon by the collective intelligence of the people using it. Rather than
provide people with detailed instructions, the rules of Scrum guide their relationships and
interactions.
6. Scrum Teams commit to a single Product Goal
Scrum is pointless without a focus on valuable outcomes.
More attention goes
to the vehicle of
Scrum than to where
it’s supposed to
take you.
8. From Roles to Accountabilities
A common make is that the focus on job titles often distracts from their accountabilities.
This further emphasizes that
the Scrum framework isn’t a
collection of job titles,
but a collection of
accountabilities to develop
a product in an empirical
manner.
9. Three Commitments To Uphold Empiricism
focuses only on the mechanics, and doesn’t bother itself with clear and singular goals
The Scrum framework, in
all its iterations, has always
been about enabling the
people who do the work
to take control of
that work.
10. Shorter and even less prescriptive
…because it can’t possibly account for every context
The Scrum framework only
sets the goalposts for an
empirical approach and trusts
in the experience and
creativity of the players to
decide how to best play
the game.
11.
12. In Summary
from 2017 to 2020 (1/2)
1. Even Less Prescriptive
Over the years, the Scrum Guide started getting a bit more prescriptive. The 2020 version aimed to bring Scrum back to being
a minimally sufficient framework by removing or softening prescriptive language. e.g. removed Daily Scrum questions, soften
language around PBI attributes, soften language around retro items in Sprint Backlog, shortened Sprint cancellation section,
and more.
2. One Team, Focused on One Product
The goal was to eliminate the concept of a separate team within a team that has led to “proxy” or "us and them” behavior
between the PO and Dev Team. There is now just one Scrum Team focused on the same objective, with three different sets
of accountabilities: PO, SM, and Developers.
3. Introduction of Product Goal
The 2020 Scrum Guide introduces the concept of a Product Goal to provide focus for the Scrum Team toward a larger
valuable objective. Each Sprint should bring the product closer to the overall Product Goal.
13. In Summary
from 2017 to 2020 (2/2)
4. A Home for Sprint Goal, Definition of Done, and Product Goal
Previous Scrum Guides described Sprint Goal and Definition of Done without really giving them an identity. They were not quite artifacts but
were somewhat attached to artifacts. With the addition of Product Goal, the 2020 version provides more clarity around this. Each of the three
artifacts now contain ‘commitments’ to them. For the Product Backlog it is the Product Goal, the Sprint Backlog has the Sprint Goal, and the
Increment has the Definition of Done (now without the quotes) . They exist to bring transparency and focus toward the progress of each
artifact.
5. Self-Managing over Self-Organizing
Previous Scrum Guides referred to Development Teams as self-organizing, choosing who and how to do work. With more of a focus on the
Scrum Team, the 2020 version emphasizes a self-managing Scrum Team, choosing who, how, and what to work on.
6. Three Sprint Planning Topics
In addition to the Sprint Planning topics of “What” and “How”, the 2020 Scrum Guide places emphasis on a third topic, “Why”, referring to the
Sprint Goal.
7. Overall Simplification of Language for a Wider Audience
The 2020 Scrum Guide has placed an emphasis on eliminating redundant and complex statements as well as removing any remaining
inference to IT work (e.g. testing, system, design, requirement, etc). The Scrum Guide is now less than 13 pages.
14. References
worth to read…
• Scrum Guide
https://www.scrumguides.org
• Change between 2017 and 2020 Scrum Guide
https://www.scrumguides.org/revisions.html
• What 4 Key Changes To The Scrum Guide Tell Us About Scrum
https://bit.ly/3obxquS