Members Selection Criteria

Criteria set by business stakeholders to determine the composition of the Scrum Guidance Body, including who should participate, their roles and accountabilities, how many members are needed, and the skills and experience required.

Key Points

  • Defined by business stakeholders to guide selection of the Scrum Guidance Body (SGB).
  • Clarifies membership composition: roles, responsibilities, and total number of members.
  • Specifies required competencies, such as domain expertise, agile experience, and decision authority.
  • Promotes objective, transparent, and strategy-aligned governance; reviewed and updated as needs evolve.

Example

Before launching a multi-team agile program, business stakeholders create Members Selection Criteria for the Scrum Guidance Body. They require seven members, including an agile coach, a product management lead, a compliance officer, a security architect, and a DevOps lead. The criteria state that each member must have at least three years of agile experience, authority to make policy decisions, and familiarity with the companys regulatory environment. Using these criteria, candidates are evaluated and the final SGB is formed.

PMP Example Question

Which statement best describes Members Selection Criteria in an agile organization?

  1. A checklist used by the Development Team to accept completed user stories.
  2. Stakeholder-defined rules specifying who should serve on the Scrum Guidance Body, their roles, the number of members, and required skills.
  3. A method for prioritizing the product backlog based on business value and urgency.
  4. Guidelines for inviting stakeholders to Sprint Reviews and setting meeting agendas.

Correct Answer: B - Stakeholder-defined criteria for selecting the Scrum Guidance Body

Explanation: Members Selection Criteria are created by business stakeholders to define SGB membership, roles, headcount, and necessary competencies; they are not acceptance criteria, prioritization methods, or meeting rules.

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


Build complete project plans in minutes with AI

Learn how to use AI to create charters, WBSs, schedules, risk registers, and executive reports while staying in control. This course gives you prompt templates and practical workflows based on real project work. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More