Scrum Guide updates - What would you change?
Soon the updated Scrum will be released. It will be a little bit shorter, only 13 pages.
(https://kenschwaber.wordpress.com/2020/08/30/scrum-guide-2020/)
What would you change and why? What do you think will be changed?
Nils
- The name of one of the roles, but there's a separate thread for that.
- Shorten the description of Sprint Planning. It's very prescriptive, and leaves less room than I'd like for Scrum Teams to find their own way.
- Remove the 3 questions altogether from the description of the Daily Scrum. Why should this practice have more prominence than walking the board, or any other technique a self-organizing Development Team may choose?
- Replace references to negotiating between the Product Owner and Development Team with a greater emphasis on inspect & adapt. Negotiation can be interpreted to be non-collaborative.
- Remove the requirement for "at least one high priority process improvement" to appear on the Sprint Backlog. In my view it was a mistake to add this in 2017. It's overly prescriptive, and an abuse of the Sprint Backlog. Even though it would be a good idea to do this on many occasions, I see no reason why we should constrain the outcome of a Sprint Retrospective to something that has to be visualized and processed in this way. It enforces delegation to the Development Team of something that was agreed by the Scrum Team.
+1 to Simon's response on renaming the role. A Developer is not referred to as a "Code Master" or "Development Master" either.