How to Get a Job For Project Managers

Learn how to write resume and interview

Leadership for Project Managers

Learn how to lead and drive project success.

Project Management with AI

From a beginner to project management professional.

Agile Project Management and SCRUM with AI

Learn to run Scrum and Agile with AI.

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?

  1. Ignore the gap and allow each team to create its own process.
  2. Submit a proposal as a Recommended Scrum Guidance Body Improvement for review and approval.
  3. Immediately enforce a new process across all teams without review.
  4. 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.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Run the drill before the incident runs you

Design, run and prove OT drills and tabletop exercises before an incident tests your team. OT Incident Drills and Exercises includes 24 lessons and practical exercise materials, delivered through HKSM Courses for US$47 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course