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.

ICS/OT Incident Response Plan: Write One That Works

Most OT incident response plans fail before anyone writes a word: no sponsor, no charter, no agreement on who decides. This workshop course takes you from a blank page to a plan your site approves and your operators can follow.

Each of the eight sections writes one chapter of your plan: the authority and scope, the inputs, severity in the language of the plant, command and decision rights, response steps, recovery and the readiness library.

You get the plan template, more than 40 templates and worksheets, 21 worked examples and a capstone with a full model answer.

50 videos, 7.7 hours. US$147 one-time through HKSM Courses. 30-day money-back guarantee when 50% or less consumed.

Explore the Course


ICS/OT Incident Response Plan course preview

Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course