SMC Exam Dumps - Scrum Master Certified (SMC)

The intended answer is Continuous stakeholder involvement because it is not one of the specific SBOK characteristics listed for achieving flexibility.

SCRUMstudy identifies the principal mechanisms supporting flexibility as iterative product development, time-boxing, cross-functional teams, customer value-based prioritization, and continuous integration. These mechanisms allow Scrum projects to absorb changing business needs while protecting stability within an active Sprint.

Iterative development creates repeated opportunities to inspect outcomes and adjust requirements. Time-boxing constrains uncertainty and establishes predictable review intervals. Cross-functional teams reduce handoffs and external dependencies by containing the required skills within the team.

Stakeholder involvement is certainly important in Scrum and supports feedback, validation, and value realization. However, the question asks for the item that is not part of the specific enumerated SBOK list of characteristics used to explain flexibility. The formally listed concept is customer value-based prioritization rather than “continuous stakeholder involvement.”

This is therefore a terminology-sensitive SMC question: option C describes a useful Scrum practice, but it is not the designated characteristic in this particular SBOK framework.

Study Guide reference: Change - > Flexibility versus Stability; Principles - > Iterative Development and Time-boxing.

========

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.

========

Within the SBOK framework reflected by this SMC question set, the recommended Scrum Team size is six to ten members. This range is intended to provide enough cross-functional capability to create the Sprint deliverables while keeping coordination and communication manageable.

If a team becomes too large, communication channels increase rapidly, meetings become more difficult to manage, self-organization becomes less efficient, and individual accountability can become diluted. Large projects are therefore normally handled through multiple Scrum Teams coordinated using mechanisms such as Scrum of Scrums rather than by constructing a single excessively large team.

Conversely, a very small team may not contain sufficient breadth of skills to function cross-functionally or may become vulnerable when one person is unavailable.

Therefore, among the choices presented, six to ten is the intended SBOK answer.

Study Guide reference: Organization - > Scrum Team - > Team Size and Personnel Selection; Scaling Scrum - > formation of multiple Scrum Teams for larger projects.

========

Option C incorrectly describes the Probability Impact Grid. In SBOK, the Probability Impact Grid evaluates each individual risk by assigning values to both probability and impact. Those ratings are then combined—commonly by multiplication—to derive a risk-severity or PI score for prioritization.

The wording in C—calculating an overall impact from the values of multiple possible events or outcomes—is more closely associated with Probability Trees, where potential outcomes are represented by separate branches with associated probabilities and impacts.

Option A is correct. Expected Monetary Value equals the monetary impact of a risk multiplied by its probability of occurrence. Option B is correct because Pareto Analysis ranks risks according to magnitude, enabling attention to be focused on the most consequential risks. Option D also correctly describes Probability Trees, where each potential outcome is represented graphically through branching alternatives.

Thus the mismatched technique-description pairing is C.

Study Guide reference: Risk - > Risk Assessment Techniques - > Probability Trees, Pareto Analysis, Probability Impact Grid, Expected Monetary Value.

========

Scrum balances flexibility with Sprint-level stability. Once the team commits to Sprint work, outside interference and arbitrary requirement changes should be prevented so that the Scrum Team can maintain focus and produce the committed increment.

The Scrum Master helps protect the Scrum Team from disruption, while the Scrum Team maintains commitment to the Sprint work. New Change Requests generally enter the Prioritized Product Backlog and are evaluated and prioritized for a future Sprint rather than being inserted indiscriminately into the active Sprint.

Option B violates this stability principle by suggesting that a Sponsor should introduce and approve changes directly during the Sprint. Option C is incorrect because Scrum does not seek “complete stability” across the project; the overall project remains deliberately adaptive. Option D is too absolute. Change approval authority can vary according to organizational tolerances and program/portfolio governance, even though the Product Owner controls project backlog prioritization.

Scrum's objective is therefore stable execution inside the Sprint and flexibility between Sprints, not resistance to change throughout the project.

Study Guide reference: Change - > Balancing Flexibility and Stability; Maintaining Sprint Stability.

========

The Scrum Master is fundamentally a facilitator and supporting/servant leader rather than a traditional command-and-control project manager. Within the quality aspect, the Scrum Master's responsibilities include eliminating environmental obstructions that can negatively affect either the quality of deliverables or the effectiveness of Scrum processes.

Environmental obstructions may include organizational interference, inadequate tools, coordination problems, communication barriers, disruptive working conditions, or dependencies that prevent the Scrum Team from working effectively. The Scrum Master facilitates their removal so the self-organizing Scrum Team can concentrate on producing high-quality deliverables.

“Leader” is too broad for the specific role described in this question. Although servant leadership is a characteristic of a Scrum Master, the operational action of clearing impediments and creating a conducive environment is fundamentally facilitative. “Pacifier” and “Escalator” are not formal Scrum roles.

The distinction matters because the Scrum Master does not solve the technical work for the team or direct members on how to build deliverables. Instead, the role improves the environment and process in which the team operates.

Study Guide reference: Quality - > Summary of Responsibilities Relevant to Quality; Organization - > Scrum Master as Facilitator/Supporting Leader.

========

A deliverable that fails its User Story Acceptance Criteria is a Rejected Deliverable. It is not marked Done and normally returns to, or remains in, the Prioritized Product Backlog where it can be reprioritized and completed during a future Sprint. SCRUMstudy explicitly states that rejected User Stories are added back to the updated backlog for future Sprints.

Option A is therefore false because future correction is specifically permitted and expected when necessary. Option B incorrectly states that the Scrum Master defines Acceptance Criteria. They are primarily defined by the Product Owner based on customer requirements. Option D is incorrect because the objective is not to create increments that may satisfy Acceptance Criteria; completed deliverables should satisfy the applicable criteria before acceptance.

Carrying rejected work into a later Sprint is undesirable because the aim is to create potentially shippable, acceptable results during each Sprint, but Scrum provides a clear mechanism for managing such incomplete work.

Therefore, C accurately describes the handling of a rejected deliverable.

Study Guide reference: Review and Retrospect - > Demonstrate and Validate Sprint - > Accepted and Rejected Deliverables.

========

Self-organization means that the Scrum Team determines how best to accomplish the work required to achieve the established project and Sprint objectives. Team members pull work, coordinate responsibilities, resolve problems collaboratively, and collectively produce tangible Sprint results.

Creating the Project Vision, however, is not a goal of the self-organizing Scrum Team. The Project Vision is established during the Initiate phase, principally under Product Owner leadership, before detailed Sprint execution. The vision provides direction within which the Scrum Core Team then self-organizes.

Option A reflects self-organized problem solving: Daily Standup identifies impediments, and detailed solutions are normally handled outside the short meeting. Option B is central to Sprint execution. Option D reflects Scrum's expectation that teams create tangible, potentially shippable results during iterations.

Self-organization therefore operates within an established vision rather than replacing the responsibility for defining that vision. The team decides how to achieve the objective but does not independently establish the project's overarching business purpose.

Consequently, C is not a goal of the self-organizing Scrum Team.

Study Guide reference: Principles - > Self-organization; Initiate - > Create Project Vision.

========