A new update of Scrum Guide was released in Nov. 2020 which contains an exciting change in the content and how Scrum Framework evolved! In this article, I like to share my views on the changes.
We developed Scrum in the early 1990s. We wrote the first version of the Scrum Guide in 2010 to help people worldwide understand Scrum. We have evolved the Guide since then through small, functional updates. Together, we stand behind it. – Scrum Guides. Ken Schwaber and Jeff Sutherland
1. Even Less Prescriptive
Scrum is like your mother-in-law, it points out ALL your faults
2, One Team, Focused on One Product
Empiricism asserts that knowledge comes from experience and making decisions based on what is observed.
3. Introduction of Product Goal
INo Heroics. If you need a hero to get things done, you have a problem. Heroic effort should be viewed as a failure of planning.
4. A Home for Sprint Goal, Definition of Done, and Product Goal
- Product Backlog aligned with Product Goal
- Sprint Backlog aligned with Sprint Goal, and
- Increment aligned with Definition of Done
5. Self-Managing over Self-Organizing
6. Three Sprint Planning Topics
- Three Questions removed from Daily Scrum – Expected; it recommends one way of doing it specifically. Follow any format relevant to your team.
- Team size of 3-9 – BRAVO! Yes, why to be picky about this. You evolve based on time. From now no one talks about the “Magical number 9”.
- The emphasis on commitment – Now we all forget the title “Forecast over Commitment.”
- Scrum Master Role – Really relevant words. I strongly believe in “You do not need a Coach if you have a “Scrum Master” in your team.” Now it’s specific to highlight this role with commitment.
- Developers Role – I am feeling little bad, and some of the prescription links removed and made it implicitly in self-managed, but it’s ok, goal achieved for specific.