HKSM

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.