SMC Exam Dumps - Scrum Master Certified Questions and Answers

A Program Scrum Master extends the facilitative Scrum Master role from an individual project to the program level. SCRUMstudy describes the Program Scrum Master as responsible for guiding, facilitating, and teaching Scrum practices to those involved in the program; helping remove program-level impediments; supporting individual project Scrum Masters; and ensuring that Scrum processes are followed effectively.

Option B is associated more closely with the Program Product Owner, who establishes strategic objectives and priorities for the program and ensures alignment of component projects with program outcomes.

Option A improperly assigns ownership of business justification and viability creation to the Program Scrum Master. Business justification is primarily a Product Owner/business responsibility, although the Scrum Master may facilitate relevant processes.

Option D is inconsistent with Scrum because the Program Scrum Master does not directly control project teams. Scrum Masters facilitate self-organizing teams rather than exercising command authority over them.

Thus the correct responsibility is facilitating and teaching Scrum practices throughout the program.

Study Guide reference: Organization - > Scrum in Programs and Portfolios - > Program Scrum Master responsibilities; Supporting Leadership.

========

The standard SBOK User Story format is:

As a < role/persona > , I should be able to < requirement > so that < benefit > .

A User Story therefore expresses three essential dimensions: Who, What, and Why. The “Why” component identifies the benefit or value expected from satisfying the requirement.

Option D directly corresponds to that third component: What benefit is expected from the requirement? This helps ensure that functionality is connected to user or business value rather than being treated simply as an isolated technical request.

Cost of development is addressed through estimation and business-justification activities rather than the core User Story template. The specific individual responsible for performing the work is not embedded in a User Story because Scrum Teams are self-organizing and determine task ownership during planning and execution. Testing techniques may influence tasks or Acceptance Criteria but are not one of the three core User Story template elements.

Therefore, the expected benefit is the relevant question.

Study Guide reference: Plan and Estimate - > Create User Stories - > User Story Template: Role/Persona, Requirement, Benefit.

========

The Scrum Team determines how prioritized requirements are transformed into completed deliverables. This is a direct consequence of Scrum's principle of self-organization.

SBOK states that Scrum Team members possess both the authority and responsibility to determine the best means of converting Prioritized Product Backlog Items into finished deliverables without requiring business stakeholder involvement in those technical implementation decisions.

The Product Owner determines what should be built and prioritizes requirements according to value, risk, dependencies, and stakeholder needs. The Scrum Team determines how committed functionality will actually be designed, developed, integrated, tested, and completed.

The Scrum Master facilitates the team's work, removes impediments, coaches participants, and protects Scrum processes but does not dictate implementation. Stakeholders supply business needs and feedback but similarly do not control technical execution.

This separation of responsibilities is fundamental to Scrum: business priorities are represented by the Product Owner, process effectiveness is supported by the Scrum Master, and technical/product-delivery decisions are made by the self-organizing Scrum Team.

Therefore, D is correct.

Study Guide reference: Organization - > Scrum Team Responsibilities; Principles - > Self-organization.

========

A Probability Impact Grid evaluates each identified risk according to two primary dimensions: its probability of occurrence and its potential impact on project objectives. SBOK explains that each dimension may be assigned a numerical or categorical rating and that probability and impact can then be combined to derive a risk-severity score.

That makes the technique particularly appropriate for the flood-and-landslide scenario. The team can estimate how likely these events are and assess the severity of their consequences for safety, cost, schedule, infrastructure, or environmental objectives. The resulting score helps determine prioritization and the urgency of mitigation.

Probability Trees model multiple possible outcomes as branches and calculate associated expected values. Pareto Analysis ranks identified risks by magnitude to focus attention on the most significant contributors. Expected Monetary Value converts uncertainty into a financial expectation by multiplying monetary impact by probability.

All four can support risk analysis, but the question specifically emphasizes evaluating probability and impact on project objectives, which directly matches the Probability Impact Grid.

Study Guide reference: Risk - > Risk Assessment - > Probability Impact Grid.

========

This scenario describes Refactoring. SBOK defines refactoring as improving the internal design or structure of existing software while preserving its externally observable functionality. The objective is to make code more concise, maintainable, flexible, and understandable without changing what the software does.

The scenario specifically states that the existing implementation is complex, redundant, and time-consuming to maintain, while functionality must remain intact. Those are classic refactoring conditions. Typical refactoring work can include eliminating duplicated code, simplifying overly complicated logic, separating responsibilities, improving naming and structure, and reducing unnecessary coupling.

Design Patterns differ because they provide reusable documented solutions to recurring design problems. A team might employ a design pattern while refactoring, but “Design Patterns” does not describe the overall activity of restructuring existing code without changing behavior.

Mitigated Risks and Updated Dependencies are project-management outputs rather than software-engineering techniques for internal code improvement.

Therefore, the defining combination—redesign internal code, remove redundancy, improve maintainability, preserve functionality—identifies refactoring unambiguously.

Study Guide reference: Quality/Implement - > Create Deliverables - > Refactoring; technical practices for maintaining product quality.

========

SBOK deliberately defines Scrum as broadly applicable. SCRUMstudy states that Scrum can be applied to portfolios, programs, and projects in any industry; to products and services; and to projects of varying sizes and complexity.

Each scenario therefore represents a condition Scrum can accommodate. Existing products receiving incremental updates can use Sprints to prioritize and release new value. Innovative products with uncertain outcomes particularly benefit from iterative development, frequent inspection, feedback, and adaptation. Scarce specialist skills can be addressed as shared-resource and organizational constraints, although careful capacity management is required. Distributed teams introduce communication and coordination challenges, but geographical distribution does not make Scrum inapplicable.

The question is testing an important principle: constraints influence how Scrum is implemented, rather than automatically disqualifying a project from Scrum. The framework can be scaled or organizational practices adapted to accommodate these conditions.

Accordingly, all four project scenarios can be candidates for Scrum, making D the intended SBOK answer.

Study Guide reference: Introduction to Scrum - > Applicability of Scrum; Organization - > Distributed Teams/Shared Resources; Principles - > Iterative Development.

========

Value-based Prioritization means that Scrum continually orders work so the most valuable requirements receive appropriate priority and business value can be delivered early and continuously, rather than being deferred until final project completion. SCRUMstudy describes this as a core Scrum principle focused on delivering maximum business value from early in the project and throughout its lifecycle.

Option A defines Time-boxing, where time functions as a limiting constraint. Option B defines Self-organization, which empowers the people performing the work. Option C defines Collaboration, specifically using the SBOK dimensions of awareness, articulation, and appropriation.

Value-based prioritization is implemented most visibly through the Prioritized Product Backlog. The Product Owner evaluates requirements by factors including value, risk/uncertainty, and dependencies and continually maintains the ordering as business conditions evolve.

The effect is that the Scrum Team works on high-value functionality without requiring the entire project's requirements to be delivered before stakeholders realize benefits.

Therefore, option D precisely states the SBOK definition.

Study Guide reference: Principles - > Value-based Prioritization; Business Justification - > Value-driven Delivery.

========

Statements I and II correctly describe the purpose of Release Planning Sessions. SCRUMstudy states that Release Planning Sessions develop a plan defining when usable sets of functionality or products will be delivered. Their major objective is to give the Scrum Team an overview of releases and the delivery schedule so that development aligns with Product Owner and stakeholder expectations.

Statement III is inaccurate because the choice between continuous and phased deployment is described primarily as an organizational strategy, not simply something determined by stakeholder requirements. Organizations may release after specified functionality has been achieved or according to predefined release dates.

Statement IV is inconsistent with Scrum's adaptive approach. Release planning establishes a useful release roadmap or schedule but does not freeze a highly detailed plan for the entire project. Requirements, priorities, risks, and business conditions can evolve, and the release schedule can be updated accordingly.

Therefore, only statements I and II are correct.

Study Guide reference: Initiate - > Conduct Release Planning - > Release Planning Sessions and Release Planning Schedule.

========

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.

========

The Product Owner has primary accountability for project-level business justification, including ensuring value delivery and maintaining the project's business rationale. The Scrum Master's role is facilitative: helping ensure that desired outcomes are understood, coordinating with the Product Owner and Scrum Team, and supporting Continuous Value Justification throughout execution.

SBOK's responsibility model assigns the Product Owner responsibility for value delivery and maintenance of project business justification, while the Scrum Master supports continuous justification and ensures that the project's desired outcomes are communicated and understood by the Scrum Team.

Therefore, A is incorrect because creation and confirmation of project business justification belong principally to the Product Owner. B likewise represents Product Owner accountability. D is also primarily assigned to the Product Owner, who is responsible for maximizing and ensuring project value.

Option C best represents the Scrum Master's supporting role. Through Sprint execution, risk/change facilitation, communication, and coordination with the Product Owner, the Scrum Master helps verify that continued investment remains aligned with the expected business outcomes.

Study Guide reference: Business Justification - > Summary of Responsibilities; Continuous Value Justification; Product Owner and Scrum Master roles.

========

Page

Scrum Master Certified (SMC®) — 100 Questions