Recommended Scrum Guidance Body Improvements
During planning for a large project, teams may propose updates to refine or expand the Scrum Guidance Body recommendations. If the Guidance Body reviews and approves these proposals, the official Scrum Guidance Body documents are revised to include the changes.
Key Points
- Ideas typically emerge while planning complex or large-scale initiatives.
- Proposals target improving or clarifying Scrum Guidance Body recommendations.
- Changes take effect only after formal review and approval by the Guidance Body.
- Once approved, the updates are published in the Scrum Guidance Body documentation.
Example
During a multi-team program increment planning session, several Scrum Masters note recurring cross-team dependency delays. They propose adding explicit guidance on dependency visualization and resolution to the Scrum Guidance Body. After evaluation, the Guidance Body accepts the proposal and updates the documentation with new recommended practices and templates.
PMP Example Question
While planning a large agile program, the teams identify a gap in current organizational Scrum guidance related to handling cross-team dependencies. What should they do next?
- Ignore the gap and allow each team to create its own process.
- Submit a proposal as a Recommended Scrum Guidance Body Improvement for review and approval.
- Immediately enforce a new process across all teams without review.
- Wait until the end of the program to document lessons learned.
Correct Answer: B — Submit a Recommended Scrum Guidance Body Improvement
Explanation: Improvements to organizational Scrum guidance should be proposed formally for Guidance Body review; approved changes are then incorporated into the official documentation.
