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.

Scrum Guidance Body Meetings

Regular sessions where the Scrum Guidance Body evaluates whether its Recommendations need updates, drawing on inputs like improvement ideas from Retrospectives and other processes, as well as new or revised regulations. The body sets how often to meet based on the specific needs of the enterprise.

Key Points

  • Purpose is to review and decide on updates to Scrum Guidance Body Recommendations.
  • Inputs include retrospective insights, process feedback, and regulatory changes.
  • Meeting cadence is determined by the organization's context and needs, not a fixed schedule.
  • Outcomes may include updated recommendations, a backlog of improvement items, or guidance for teams and leadership.

Example

A global fintech company holds Scrum Guidance Body meetings every quarter. The group reviews suggestions from team Retrospectives and new compliance rules, then updates enterprise-wide Definition of Done and branching policies. When a major regulation changes midyear, they schedule an extra meeting to issue interim guidance.

PMP Example Question

Which statement best describes Scrum Guidance Body Meetings in an enterprise setting?

  1. They are daily standups used by all Scrum teams to synchronize work.
  2. They are periodic sessions to assess and update organizational Scrum recommendations, with frequency set by enterprise needs.
  3. They are mandatory monthly audits conducted by external regulators.
  4. They are project kickoffs to approve the Product Backlog and sprint goals.

Correct Answer: B — Periodic sessions to update organizational Scrum recommendations, with frequency based on needs

Explanation: Scrum Guidance Body Meetings focus on reviewing and updating enterprise-level recommendations using inputs like retrospectives and regulations. Their cadence is determined by what the organization requires.

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


Stop Managing Admin. Start Leading the Future!

HK School of Management helps you learn AI prompt engineering for project work. Move beyond status reports and risk logs with practical prompt frameworks for everyday tasks. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Enroll Now