2017 Scrum Guide
2017 Scrum Guide
org
Practiced everywhere
Challenges are moving beyond the complex, increasingly to the chaotic. The rate of
change is well beyond linear.
Three dimensions of change:
• People – markets, increased number, distribution, social organization, religion
• Technology – iPhone in 2007, robust Internet, energy
• Mother Earth – things are changing
“In a world rife with change, dominance is fleeting; only agility creates
sustainable advantage. As we move forward, the market must put a premium on
agility and companies must measure it along with other key metrics.”
• Uses of Scrum
• Refined the Role of the Scrum Master
• The Daily Scrum is for Inspection and Adaption
to ensure progress toward the Sprint Goal
• Time-boxes carry a maximum length
– “Time-boxing refers to the act of putting strict time
boundaries around an action or activity”
• Sprint Backlog includes feedback from the
Sprint Retrospective
The Daily Scrum is for Inspection and Adaption to ensure progress is being made
toward the Sprint Goal
The Development Team uses the Daily Scrum to inspect progress toward the
Sprint Goal and to inspect how progress is trending toward completing the work in
the Sprint Backlog. The Daily Scrum optimizes the probability that the
Development Team will meet the Sprint Goal. Every day, the Development Team
should understand how it intends to work together as a self-organizing team to
accomplish the Sprint Goal and create the anticipated Increment by the end of the
Sprint.
The structure of the meeting is set by the Development Team and can be
conducted in different ways if it focuses on progress toward the Sprint Goal. Some
Development Teams will use questions, some will be more discussion based.
Added clarity around time-boxes using the words “at most” to remove
any questions that Events have to be of a certain length. Time-boxes
are the maximum times allotted.
“Time-boxing refers
to the act of putting
strict time boundaries
around an action or
activity”
The Sprint Backlog makes visible all the work that the Development
Team identifies as necessary to meet the Sprint Goal. To ensure
continuous improvement, it includes at least one high priority process
improvement identified in the previous Retrospective meeting.
How often the team is able to release, and how the product is supported are often part of
the equation, but so is the customer’s ability to absorb the new functionality.
Example: Self-driving cars where more functionality is released than is within the
boundaries of safety.
• Releases may be delivered at any time that the Product Owner chooses and the
Scrum Team is capable of
– Watch out for value being outweighed by debt
• The only requirement is that at the end of the Sprint there is an increment that is
“Done” and must be in useable condition regardless of whether the Product
Owner decides to actually release it
• The Development Team has to prove within the first several Sprints that the
Product is viable and will produce value
• If the Scrum Team is empowered and the organization is supportive, the result is
organizational change without any crisis
• Scrum projects often require new capabilities to be instantiated and tested prior
to proceeding
– Minimize risk early