Scrum SMC Practice Test Questions Answers

The Prioritized Product Backlog is not a tool of the Create Deliverables process. In the legacy SBOK process structure underlying this question, the principal Create Deliverables tools include Team Expertise, Software, Other Development Tools, and Scrum Guidance Body Expertise. Other Development Tools may include techniques such as refactoring and Design Patterns.

Team Expertise represents the collective technical and functional knowledge used by Scrum Team members to transform Sprint work into finished deliverables. Software tools may support scheduling, collaboration, tracking, information distribution, and project execution. Design Patterns provide reusable approaches for resolving recurring design problems and can therefore support creation of deliverables.

The Prioritized Product Backlog serves a different function: it represents the prioritized project requirements maintained by the Product Owner. During the Sprint itself, the Scrum Team executes work from the Sprint Backlog, which contains the committed work for that Sprint.

Therefore, although the Prioritized Product Backlog ultimately drives what enters future Sprints, it is not classified as a Create Deliverables tool.

Study Guide reference: Implement - > Create Deliverables - > Inputs and Tools.

========

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.

========

A sustainable pace is a level of effort that the Scrum Team can maintain consistently without burnout, chronic overtime, deterioration in quality, or progressively declining effectiveness. Therefore, option C most accurately reflects the concept: Sprint effort should normally be comparable with previous Sprints and remain comfortable and repeatable for the team.

Sustainable pace does not mean continually increasing workload as experience grows. Productivity may improve as the team learns, but that improvement should arise from better collaboration, technical practices, reduced waste, and accumulated knowledge—not from continually demanding greater physical effort.

Likewise, sustainable pace does not imply that effort must steadily decrease. Different Sprint contents will vary, but the team's workload should remain within a manageable long-term capacity.

SCRUMstudy links sustainable pace directly to quality. Excessive overtime and end-loaded testing tend to increase defects and reduce maintainability, while regular development and testing throughout Sprints produce a more stable working environment.

Thus C expresses the central idea: consistent, repeatable, healthy effort across Sprints.

Study Guide reference: Quality - > Sustainable Pace; Scrum Master Responsibilities Relevant to Quality.

========

Option C contains the intended SBOK responsibility mapping. The Sponsor provides resources and financial support for the project. The Scrum Guidance Body (SGB) establishes organizational guidance, including recommendations concerning business justification techniques and other Scrum practices. The Scrum Master facilitates creation of project deliverables and helps manage risks, changes, and impediments through Scrum processes.

Customers and users constitute important business stakeholders whose requirements and expected value feed the Prioritized Product Backlog. In the formal core-role model, the Product Owner consolidates, articulates, and prioritizes those requirements as the Voice of the Customer; therefore, statement b should be understood in this question's stakeholder-input context rather than as transferring Product Owner accountability to customers. SCRUMstudy identifies the Product Owner as the role responsible for representing stakeholder interests and maintaining prioritized requirements.

The other mappings incorrectly assign funding, guidance, or facilitation responsibilities.

Thus the intended mapping is Sponsor - > c; SGB - > d; Customers/Users - > b; Scrum Master - > a.

Study Guide reference: Business Justification - > Responsibilities of Scrum Roles; Organization - > Sponsor, Business Stakeholders, Scrum Guidance Body, Scrum Master.

========

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.

========