Key Changes in the 2020 Scrum Guide: From Teams to Developers and Product Goal
The 2020 Scrum Guide slimmed down to 17 pages from 26 in the 2017 version. It keeps the core principle: simple to understand, tough to master. Gone are the rigid rules for Daily Scrum—the team now decides its own format, ditching the standard three questions.
Roles got a clearer definition: "Development Team" is now simply "Developers." This eliminates the "us vs. them" divide between the Product Owner and the rest. The Scrum Team is now a unified group: Product Owner, Scrum Master, and Developers, capped at 10 people.
Product Goal as the Guiding Star
Enter the Product Goal—a long-term objective that sits above the Sprint Goal. Every sprint moves the product closer to it. The Product Owner shares it with the team, while the Scrum Master helps craft it.
Teams are now self-managing, not just self-organizing. They decide who does what, when, and how. This ramps up accountability across the entire Scrum Team.
Warning to developers: Tweaking core Scrum elements hides problems and weakens the framework's power. Scrum is a framework, not a rigid methodology—plug in any practices inside it, as long as you keep the iterative flow and user focus.
Scrum Adoption Stats
In Russia, 82% of teams use Scrum for IT products (Scrumtrek's "Agile in Russia 2023" study, over 1,000 respondents). Globally, it's 63% (State of Agile 2023 by Digital.ai, 780 respondents from 6 continents).
Over 30 years, there have been 7 guide editions. Average Agile experience in Russia is about 3.4 years (2021–2022).
Key Takeaways
- Developers over Development Team: Puts the spotlight on a unified Scrum Team, breaking down silos.
- Product Goal: The product's big-picture target, linking sprints into a cohesive chain.
- Self-management: Teams own their processes, including Daily Scrum format.
- Slimmer guide: 17 pages, fewer rules, more flexibility.
- Change caution: Altering Scrum's core dilutes its value.
Impact on Mid- and Senior-Level Practices
For senior developers and Product Owners, these shifts highlight accountability for goals. The Product Goal demands strong roadmap skills—make it measurable and achievable.
In Daily Scrums, try techniques like Walking Skeleton or Silent Grouping for feedback without rigid templates. Self-management calls for T-shaped skills—every Developer pitches in cross-functionally.
Version comparison:
| Aspect | Scrum Guide 2017 | Scrum Guide 2020 |
|--------|------------------|-------------------|
| Length | 26 pages | 17 pages |
| Daily Scrum | 3 required questions | Team's choice |
| Dev Role | Development Team (up to 9) | Developers (up to 10) |
| Management | Self-organization | Self-management |
| Goals | Sprint Goal | Sprint Goal + Product Goal |
Experiment with practices (Kanban in sprints, OKRs for Product Goal), but stick to the artifacts: Product Backlog, Sprint Backlog, and Increment.
Scrum stays the go-to for complex, adaptive products. Tailor it to your context—in distributed teams, amp up the Scrum Master's facilitation role.
— Editorial Team
No comments yet.