Improve Flow of Sprint Planning
In the PSM and PSPO there are great flow diagrams for the Sprint Planning, where Definition of Done and Retrospective Commitments are part of the input for the Sprint Planning. This is inconsistent with the way it is now described in the Scrum Guide.
From Scrum Guide, section Sprint Planning, subsection Topic One: What can be done this Sprint?
"The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and past performance of the Development Team."
Suggestion: remove "the latest product Increment" (btw: in the rest of the guide it is called Increment), and replace it by Definition of Done and Retrospective Commitments.
Reason: Increment is input to the Sprint Review, and feedback is already translated to an update Product Backlog there. Definition of Done and Retrospective commitments are not mentioned anywhere in the Sprint Planning section, even though we do teach this.