Scrum Scrum Master Certified (SMC) SMC Exam Dumps: Updated Questions & Answers (October 2026)

The intended SMC answer is C — Ensure back-up resources are available. During the Form Scrum Team process, the Scrum Master facilitates selection and formation of the team, supports the Collaboration Plan and Team Building Plan, and ensures that appropriate backup resources are available where necessary. SCRUMstudy's current role-responsibility mapping explicitly assigns this responsibility to the Scrum Master.

Option A is primarily associated with the Product Owner, who defines the Project Vision and is accountable for aligning the project with business objectives. Option D is also a Product Owner responsibility: the Product Owner defines User Story Acceptance Criteria based on customer and business requirements, although the Scrum Master facilitates their creation and protects them from inappropriate modification during a Sprint.

There is nuance around option B: modern SBOK responsibility tables state that the Scrum Master helps identify business stakeholders. However, this legacy exam item is specifically testing the Form Scrum Team responsibility and its established keyed answer is C. The distinction is that identifying and formally representing business stakeholder interests remains primarily aligned with Product Owner/project initiation activities, whereas ensuring backup resources is explicitly stated as a Scrum Master duty.

Study Guide reference: Organization - > Scrum Master Responsibilities; Initiate - > Form Scrum Team.

========

A risk threshold identifies the point or level at which exposure changes from being acceptable to unacceptable. SCRUMstudy distinguishes risk threshold from the related concepts of risk appetite and risk tolerance. Risk appetite reflects the overall amount of uncertainty an organization is willing to pursue or accept, while risk tolerance describes the degree or volume of variation the stakeholder can withstand. The threshold establishes the boundary at which action or rejection becomes necessary.

In this scenario, some defects remain acceptable and do not prevent release. Once the defect level rises beyond a specified point, however, the deliverables will be rejected. This establishes a clear acceptance boundary, making it a textbook example of a risk threshold.

Risk seeking is a behavioral attitude in which a stakeholder is willing to accept greater uncertainty in pursuit of additional benefits. That concept does not apply here.

The decisive phrase is effectively “acceptable until this level is exceeded.” Once that boundary is crossed, the response changes. Therefore, the scenario illustrates Risk Threshold.

Study Guide reference: Risk - > Risk Attitude - > Risk Appetite, Risk Tolerance, Risk Threshold, Utility Function.

========

Mark should inform the Scrum Master, who can address the resource interference with the Product Owner. One of the Scrum Master's fundamental responsibilities is to maintain an environment conducive to team success and remove impediments or organizational interference that threatens Sprint execution.

Option A is incorrect because Sprint deadlines are not simply extended when resource problems occur. The Sprint is a fixed time-box. Option B is also inconsistent with self-organization because the Scrum Master should not act as a traditional manager by directly assigning Mark's task to another team member. The Scrum Team determines internally how work is allocated.

Option D incorrectly assumes that the Product Owner can automatically move unfinished work while disrupting the active Sprint. If work cannot be completed, backlog consequences are handled through the normal Sprint and backlog processes rather than by arbitrarily extending or reallocating committed work.

A mid-Sprint reassignment can undermine capacity, predictability, and Sprint commitment. The Scrum Master should therefore raise the issue with Andy and protect the team's ability to perform its committed work while facilitating an appropriate organizational resolution.

Study Guide reference: Organization - > Scrum Master as Facilitator/Supporting Leader; Self-organization; Impediment Removal.

========

SBOK distinguishes risks from issues primarily through uncertainty. A risk is an uncertain future event that may affect project objectives. An issue is an existing, well-defined condition that is already occurring and therefore does not require a probability assessment.

Statements I and II contain future uncertainty: the representatives might not be ready, and the painting crew might be delayed by rain. These events have not occurred and therefore qualify as risks.

Statements III and IV describe current facts. Funding was not approved, making this an existing problem. Requirements are unclear, so ambiguity is already affecting the project. SCRUMstudy actually uses these examples when explaining the distinction: delayed crews and potentially unprepared representatives are risks, while unapproved funding and unclear requirements are issues.

Risk management is proactive—identify, assess, prioritize, mitigate, and communicate uncertain events before they materialize. Issues require active resolution because they are already real.

Therefore, I and II are the risks.

Study Guide reference: Risk - > Difference between Risks and Issues.

========

The incorrect statement targeted by this question is statement II. A Scrumboard is fundamentally a Scrum Team information radiator used to visualize and track Sprint work. SCRUMstudy explains that the team uses the Scrumboard to plan and track progress and that it can be maintained manually on paper or a whiteboard, or electronically.

Stakeholders may be able to observe the board because Scrum promotes transparency, but the board is not described as a stakeholder-owned planning and progress-control mechanism. Sprint execution remains with the self-organizing Scrum Team.

The exact number of columns has varied across SBOK editions and examples. Typical layouts include To Do, In Progress, Testing, and Done; other representations may include an additional Stories column. Therefore, the essential exam concept is not a rigid visual format but the board's role in transparently showing Sprint task status. During implementation it is continually updated as work progresses, and a fresh board is used for the subsequent Sprint.

Thus statement II incorrectly assigns ownership/use to stakeholders rather than the Scrum Team.

Study Guide reference: Implement - > Create Deliverables - > Scrumboard; Empirical Process Control - > Transparency.

========

After development is completed, the increment must be validated and demonstrated. The Scrum Team is responsible for ensuring that Sprint Deliverables satisfy the agreed quality conditions before presenting them in the Sprint Review/Demonstrate and Validate Sprint process. During that review, the team demonstrates completed functionality to the Product Owner and relevant business stakeholders, including customers or users where appropriate.

Acceptance Criteria provide the objective basis for checking whether a User Story satisfies the required functionality. Formal acceptance or rejection authority belongs to the Product Owner, not the Scrum Master.

Consequently, statement II is incorrect: the Scrum Master does not independently deploy the functionality into production merely because Sprint development has finished. Release is a business decision and follows the appropriate Ship Deliverables process. Statement IV is also incorrect because the Scrum Master cannot reject a User Story based on stakeholder feedback.

Statements I and III correctly represent demonstration and validation activities associated with completed Sprint work. Therefore, A is the intended answer.

Study Guide reference: Review and Retrospect - > Demonstrate and Validate Sprint; Quality - > Acceptance Criteria.

========

SBOK defines six non-negotiable Scrum principles:

1. Empirical Process Control

2. Self-organization

3. Collaboration

4. Value-based Prioritization

5. Time-boxing

6. Iterative Development

Collaboration is therefore a Scrum principle and focuses on awareness, articulation, appropriation, and shared value creation. Value-based Prioritization ensures that the project continuously focuses on work producing the greatest business value. Iterative Development allows teams to repeatedly build, inspect, obtain feedback, and adapt to changing requirements.

Manage by Stages is not an SBOK Scrum principle. It is terminology associated particularly with PRINCE2's project-management principles, where a project is planned, monitored, and controlled stage by stage.

Although Scrum does divide work into Sprints, this should not be confused with the “Manage by Stages” principle. Scrum Sprints are iterative, adaptive development cycles rather than traditional management stages.

Therefore, C is not one of SBOK's six Scrum principles.

Study Guide reference: Principles - > Six Scrum Principles.

========

SBOK establishes a specific exception to the general rule that Sprint scope remains unchanged once implementation begins. If the Scrum Team determines that it has significantly overestimated the effort required and consequently has genuine spare capacity, the team may ask the Product Owner which additional User Stories can be introduced into the current Sprint.

The Sprint Backlog and Sprint Burndown/Burnup information can make this situation visible by showing that work is being completed considerably faster than expected and that meaningful capacity remains.

Option A is insufficient because having highly skilled individuals does not itself authorize scope modification. Option B is also insufficient: one idle member does not necessarily mean the overall Scrum Team has enough capacity to complete another User Story. Option C concerns potential future Change Requests and provides no justification for disturbing the current Sprint.

The exception therefore applies when the team as a whole has overestimated effort and has spare capacity. Even then, the Scrum Team does not unilaterally select new work; it asks the Product Owner which additional prioritized User Story should be included.

Study Guide reference: Change - > Changes to a Sprint - > Exception for Overestimated Effort and Spare Capacity.

========

Page

Scrum Master Certified (SMC®) — 100 Questions

The Daily Standup is a synchronization and transparency mechanism, not an individual performance-management meeting. Team members discuss recent progress, upcoming work, and impediments so that the self-organizing Scrum Team can coordinate effectively and identify problems requiring follow-up.

SCRUMstudy describes Daily Standups as providing team members with visibility into strengths, weaknesses, missed tasks, dependencies, and impediments so that the team can collaboratively adjust its work.

Detailed problem solving is normally kept outside the tightly time-boxed meeting. An impediment raised during the Standup can subsequently be investigated and resolved with Scrum Master support. Information about recurring difficulties can also contribute to subsequent Sprint improvement discussions and retrospective learning.

Using the meeting to track individual employee performance, however, would undermine self-organization and encourage reporting upward to a manager rather than communication among peers. Scrum evaluates progress primarily at the team and deliverable level.

Therefore, individual performance tracking is specifically the inappropriate use of Daily Standup information.

Study Guide reference: Implement - > Conduct Daily Standup; Principles - > Self-organization and Collaboration.

========

Once a Sprint begins, its committed scope and Acceptance Criteria are normally protected from change. New requirements are ordinarily added to the Prioritized Product Backlog and considered in a later Sprint. However, SBOK defines an important exception: if a change is so significant that continuing the existing Sprint would no longer create meaningful or useful results, the active Sprint should be terminated and a new Sprint planned using the revised requirements.

The scenario explicitly describes a critical business requirement that changes the Acceptance Criteria governing committed work. This implies that the existing Sprint outcome may no longer satisfy the customer's essential need. In that situation, simply continuing against obsolete criteria would waste resources.

Option A allows uncontrolled mid-Sprint scope substitution, which Scrum avoids. Option B would normally be correct for a non-urgent change, but the question emphasizes criticality. Option C incorrectly frames the problem as team bandwidth rather than Sprint stability and business value.

Therefore, where the changed requirement invalidates the current Sprint's intended outcome, Sprint termination and replanning is the appropriate response.

Study Guide reference: Change - > Integrating Change; Maintaining Sprint Stability; Managing Urgent Change Requests.

========