Scrum SMC Scrum Master Certified (SMC) Exam Practice Test

Create Sprint Backlog belongs to the Plan and Estimate phase, not the Implement phase.

In the terminology of this question's SBOK edition, the Implement phase consists of:

- Create Deliverables

- Conduct Daily Standup

- Groom Prioritized Product Backlog

Current SCRUMstudy terminology renames the third process Refine Prioritized Product Backlog, but it remains part of Implement.

Sprint Backlog creation occurs during planning after User Stories have been estimated and committed and tasks have been identified and estimated. The Sprint Backlog represents the work selected and structured for execution during the forthcoming Sprint.

Once implementation begins, the Scrum Team works through Sprint Backlog tasks to create deliverables, synchronizes through Daily Standups, and maintains the overall Prioritized Product Backlog through refinement activities.

Therefore, Create Sprint Backlog is the only listed process outside the Implement phase.

Study Guide reference: Plan and Estimate - > Create/Update Sprint Backlog; Implement - > Create Deliverables, Conduct Daily Standup, Groom/Refine Prioritized Product Backlog.

========

A Risk Breakdown Structure (RBS) is specifically designed to organize identified risks into logical categories based on common characteristics or sources. SCRUMstudy describes an RBS as a technique in which risks are grouped according to categories or commonalities—for example, financial, technical, operational, safety, regulatory, or external risks. This hierarchical categorization makes a potentially large collection of risks easier to analyze and manage.

The other options serve different purposes. A Risk Checklist helps ensure that commonly encountered risks are not overlooked. A Risk Prompt List stimulates thinking about possible risk sources. Brainstorming generates potential risks through collaborative discussion among knowledgeable participants. None of those techniques is primarily intended to categorize and structure already identified risks according to similarities.

The wording “categorize and organize” is therefore decisive. Once risks have been identified, an RBS provides a structured view that facilitates further assessment, ownership, prioritization, and response planning.

Consequently, Risk Breakdown Structure is the appropriate technique.

Study Guide reference: Risk - > Risk Identification - > Risk Breakdown Structure; Risk Checklists; Risk Prompt Lists; Brainstorming.

========

The Product Owner defines the User Story Acceptance Criteria based on understanding of customer and business requirements, but once a User Story has been committed to an active Sprint, the Scrum Master is responsible for protecting the team from inappropriate mid-Sprint alteration of those criteria.

SCRUMstudy explicitly assigns the Scrum Master responsibility for ensuring that Acceptance Criteria are not changed by the Product Owner in the middle of the Sprint.

This preserves Sprint stability and prevents completed or partially completed work from being judged retrospectively against requirements that did not exist when the team made its commitment. New or changed requirements are normally reflected in the Prioritized Product Backlog and considered for a subsequent Sprint.

The Sponsor, customers, and users may supply feedback and business requirements, but they do not control the active Sprint's Acceptance Criteria. The Product Owner owns the criteria but is precisely the role whose mid-Sprint changes must be controlled.

Therefore, the Scrum Master ensures that the agreed Acceptance Criteria remain stable for the committed Sprint.

Study Guide reference: Quality - > User Story Acceptance Criteria; Change - > Maintaining Sprint Stability; Scrum Master responsibilities.

========

SBOK defines risk as an uncertain event or set of events that can affect project objectives. Importantly, risk is not necessarily negative. Risks with potentially favorable consequences are classified as opportunities, whereas risks capable of producing adverse outcomes are called threats. SCRUMstudy explicitly distinguishes these two categories.

In this scenario, additional orders have not yet materialized, so they remain uncertain. However, if they occur, they would generate a positive business consequence attributable to successful project performance. That makes the event a positive risk—an opportunity.

An issue differs from a risk because an issue has already occurred and therefore is no longer uncertain. “Weakness” may be used in analytical techniques such as SWOT Analysis but is not the correct risk classification in this scenario. A threat would apply if the uncertain event could negatively affect objectives.

Because future orders represent uncertainty with a beneficial potential impact, the correct classification is Opportunity.

Study Guide reference: Risk - > Definition of Risk - > Opportunities and Threats; Risk Identification and Assessment.

========

Statements I, III, and IV are correct. Dependencies represent relationships among User Stories or tasks that constrain or influence the sequence in which work should be performed. SBOK classifies dependencies in several ways, including mandatory versus discretionary and internal versus external. Mandatory dependencies are inherent in the nature of the work; discretionary dependencies are introduced by choice, convention, preference, or workflow design.

Dependencies also highlight interaction between tasks and help determine the most logical execution sequence. Documenting them is especially important where multiple Scrum Teams, technical components, specialists, or external suppliers are involved.

Statement II is false. Dependencies are explicitly one of the three major factors considered when prioritizing the Prioritized Product Backlog, alongside value and risk/uncertainty. The Product Owner must account for implementation dependencies when determining ordering.

Where appropriate, dependencies among User Stories can also be reduced or resolved by splitting overly large stories or restructuring/combining related requirements.

Thus I, III, and IV accurately describe dependency management, making option B correct.

Study Guide reference: Plan and Estimate - > Identify Tasks - > Dependencies; Value-based Prioritization - > Dependencies.

========

The technique described is Planning Poker. In Planning Poker, Scrum Team members receive decks containing numerical values, commonly based on a modified Fibonacci sequence. After discussing a User Story or task, every estimator independently selects a card representing the relative effort, size, or complexity of that item. The cards are then revealed, and differences in estimates trigger further discussion until sufficient consensus is achieved.

Fist of Five uses fingers rather than numbered card decks and is useful for estimation or rapid consensus-building. Wideband Delphi involves repeated independent estimates and discussion but does not inherently require Planning Poker cards. Affinity Estimation instead groups or orders items by relative size.

Planning Poker combines individual judgment with collaborative discussion. Simultaneous revelation also reduces anchoring because one participant's estimate cannot influence everyone else's initial estimate before they have committed to a value.

The explicit reference to a deck of numbered cards and each member selecting a card corresponding to an estimate makes Planning Poker unambiguous.

Study Guide reference: Plan and Estimate - > Estimate User Stories/Estimate Tasks - > Planning Poker; Relative Estimation.

========

A Sprint Burndown Chart graphically represents the amount of work that remains to be completed during an ongoing Sprint. SCRUMstudy's SBOK glossary explicitly defines it as a graph depicting the amount of work remaining in the Sprint.

Normally, the horizontal axis represents elapsed Sprint time and the vertical axis represents remaining effort, tasks, or points. As work is completed, the plotted remaining workload should trend downward toward zero. Comparing actual remaining work with an expected trajectory helps the Scrum Team identify whether progress is broadly consistent with the Sprint plan.

Option A relates more directly to the Impediment Log and Daily Standup discussions. Although a Burndown Chart may indirectly indicate that progress has slowed, it does not identify the specific impediment causing that condition. Option C describes completed work rather than the traditional burndown representation of remaining work. Option D describes task or User Story estimation rather than Sprint tracking.

Therefore, its fundamental purpose is to visualize work remaining during the Sprint.

Study Guide reference: Implement - > Sprint Tracking Tools - > Sprint Burndown Chart.

========

Option C is false because User Story Acceptance Criteria are primarily defined by the Product Owner, based on the Product Owner's understanding of customer and business requirements. The Product Owner then communicates the User Stories and their criteria to the Scrum Team, and agreement and clarification are obtained. SCRUMstudy explicitly identifies Acceptance Criteria as objective conditions developed by the Product Owner.

The Scrum Master facilitates the process and ensures that agreed Acceptance Criteria are not inappropriately changed during an active Sprint, but the Scrum Master does not jointly own their definition with the Scrum Team.

Option D accurately reflects Scrum's iterative delivery approach: work is developed in short, time-boxed Sprints. Options A and B describe the more centralized quality and formal change-management characteristics typically associated with traditional project-management models in the SBOK comparison.

This distinction is important because Scrum incorporates quality continuously through Done Criteria, Acceptance Criteria, iterative development, inspection, adaptation, and frequent stakeholder feedback instead of treating quality primarily as a late project-control activity.

Study Guide reference: Quality - > Quality in Scrum versus Traditional Project Management; Acceptance Criteria; Product Owner Responsibilities.

========

Page

Scrum Master Certified (SMC®) — 100 Questions

Takeuchi and Nonaka's work is historically important because it explicitly contrasted the new product-development model with the traditional sequential relay-race approach. They did not recommend sequential development. Instead, they described a holistic or rugby-style model in which a multidisciplinary team progresses together toward a common objective.

The rugby metaphor emphasized overlapping activities, collaboration, adaptability, and shared responsibility rather than handing work sequentially from one specialist group to another. Their observations were derived from case studies involving organizations across several manufacturing industries. This conceptual foundation later contributed to what became known as Scrum.

Therefore, option B reverses the historical argument. The sequential relay-race model was the approach Takeuchi and Nonaka were challenging, whereas the rugby model represented the flexible, integrated alternative they advocated.

Options A, C, and D accurately describe the historical background presented by SCRUMstudy: the rugby analogy, team-based development toward a shared objective, and the use of cross-industry manufacturing case studies.

Study Guide reference: Introduction to Scrum - > History of Scrum; traditional sequential product development versus the holistic/rugby approach.

========

SBOK emphasizes behavioral characteristics that enable a self-organizing and cross-functional team rather than requiring every individual to possess narrow specialist mastery or extensive Scrum theory. SCRUMstudy identifies desirable Scrum Team members as independent, self-motivated, customer-focused, responsible, and collaborative.

A Scrum Team member must be capable of working collectively toward shared Sprint objectives while taking personal ownership of assigned or selected work. “Independent” in this context does not mean isolated; it means being capable of taking responsibility without requiring command-and-control supervision. Collaboration remains essential because knowledge, work, risk, and accountability are shared across the team.

Options A, B, and C contain useful competencies, but they are not the defining combination sought by the question. A Scrum Team may contain generalist-specialists with differing domain and technical abilities, and not every member needs mastery of Scrum-specific tools or sophisticated negotiation capabilities.

The combination of collaborative, highly motivated, and independent most closely reflects the qualities needed for successful self-organization and collective ownership.

Study Guide reference: Organization - > Scrum Team - > Team Characteristics; Principles - > Self-organization and Collaboration.

========

The Retrospect Project Meeting is the meeting described in the relevant SBOK edition as not Time-boxed and capable of being conducted either in person or virtually. Its objective is broader than a Sprint-level retrospective: participants evaluate the overall project, document lessons learned, discuss positive and negative experiences, and identify opportunities to improve future projects.

SCRUMstudy specifically describes this meeting as not being Time-boxed and notes that it may take place physically or in a virtual format.

The other choices are Time-boxed Scrum events. The Daily Standup has a strict short duration. Sprint Planning is Time-boxed according to Sprint length, and Sprint Review/Demonstrate and Validate Sprint is also conducted within a defined time-box.

The rationale is that Retrospect Project occurs after the broader project lifecycle and may involve examining substantial lessons, organizational practices, knowledge transfer, transition matters, and stakeholder feedback. It therefore does not carry the same fixed execution-cycle constraint as recurring Sprint events.

Accordingly, the correct answer is B.

Study Guide reference: Review and Retrospect/Release - > Retrospect Project Meeting; Lessons Learned; Continuous Improvement.

========

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.

========

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.

========

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.

========

A Scrumboard represents work associated with a particular Sprint. During that Sprint, tasks move through workflow states such as To Do, In Progress, Testing, and Done. The board is updated continuously so that the team has a transparent view of current progress.

At the completion of the Sprint, however, that Sprint's working board is no longer the active execution board. Earlier SBOK guidance explicitly describes the Scrumboard as being reset or wiped off, with a new Scrumboard created for the next Sprint. Current SBOK guidance similarly states that one Scrumboard is valid for one Sprint and that the Scrum Team creates a new board for the next Sprint.

This distinction is important because velocity is not calculated merely by retaining two physical boards side by side. Historical metrics and Sprint results can be preserved through appropriate tracking mechanisms, while the operational Scrumboard remains focused on current Sprint work.

Thus the exam wording “reset or wiped off” reflects the SBOK concept that each Sprint receives its own current execution view rather than indefinitely accumulating tasks from earlier Sprints.

Study Guide reference: Implement - > Create Deliverables - > Updated Scrumboard; Scrumboard lifecycle across Sprints.

========

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.

========

Sprint length should be selected deliberately and consistently, with consideration for the nature of the project, anticipated rate of change, risk, and planned release dates. SCRUMstudy specifically identifies planned product or service release dates as a factor that should be considered when determining Sprint length.

Option B is incorrect because the expected frequency and impact of changes matter considerably. Environments with substantial uncertainty or frequent changes often benefit from shorter feedback cycles, allowing the team and Product Owner to inspect results and adapt more frequently.

Option C reverses the logic. A highly stable environment does not automatically require the shortest Sprint purely because little change is expected. Sprint length should reflect the project's context rather than follow that blanket rule.

Option D is also incorrect. SBOK guidance uses relatively short Sprint intervals and emphasizes consistent time-boxes. A universal six-week Sprint is not the recommended rule.

Once an appropriate Sprint length has been agreed upon, unnecessary variation between Sprints should be avoided because changing duration undermines historical velocity and forecasting comparability.

Study Guide reference: Initiate - > Conduct Release Planning - > Length of Sprint; Principles - > Time-boxing and 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 how the Scrum Core Team can originate proposed changes. SBOK explains that ongoing interaction among the Product Owner, Scrum Master, Scrum Team, and stakeholders may lead Scrum Core Team members to suggest changes or product improvements. Recommendations commonly arise while creating deliverables, during Daily Standups, and particularly through the Retrospect Sprint process.

Statement IV is incorrect because the Scrum Master does not finalize formal Change Requests. The Product Owner has the decision authority to determine which suggested changes should become formal Change Requests and how approved changes should be prioritized in the Prioritized Product Backlog.

Statement III is not the applicable SBOK responsibility in the form stated here. Escalation beyond defined tolerances can involve other organizational authorities, but that does not make the Scrum Master the authority for finalizing or approving the change.

Thus, the technically supported statements are I and II. This also reinforces Scrum's separation between proposing/facilitating change and business prioritization/approval.

Study Guide reference: Change - > Change Requests - > Scrum Core Team; Retrospect Sprint; Product Owner authority over Prioritized Product Backlog.

========

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.

========

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.

========

Statements II, III, and IV align with the Scrum Master's facilitative role. The Scrum Master ensures Scrum practices and processes are correctly followed, supports transparency and effective communication, facilitates Scrum meetings, and removes obstacles that interfere with successful delivery. SCRUMstudy describes the Scrum Master as the facilitator and supporting/servant leader who creates an environment conducive to team success.

Statement I is incorrect because strategic objectives and priorities are not defined by the Scrum Master. Strategic priorities are associated with Product Owner roles at the appropriate organizational level—for example, Program Product Owner or Portfolio Product Owner when Scrum is scaled. The Scrum Master supports execution of Scrum and removes impediments; the role does not own the business strategy.

Release Planning is also facilitated or coordinated by the Scrum Master while the Product Owner and Scrum Team participate in determining the release structure and Sprint length. Transparency is supported through visible artifacts, effective facilitation, and adherence to empirical process control.

Therefore, the valid combination is II, III, and IV.

Study Guide reference: Organization - > Scrum Master Responsibilities; Initiate - > Conduct Release Planning; Principles - > Empirical Process Control/Transparency.

========

Story points are a relative estimation unit, not a direct representation of elapsed hours. They allow the Scrum Team to compare the overall size of User Stories by considering characteristics such as effort, complexity, uncertainty, and risk.

SCRUMstudy states that Relative Sizing/Story Points assigns a point value according to the overall size of a User Story, considering factors including the effort required and level of complexity. Once one item has been estimated, other User Stories can be estimated relative to that reference item.

Option A incorrectly equates story points with hours. Scrum can use time-based task estimates, but story points intentionally support relative rather than absolute estimation. Option C describes a count of completed stories rather than story points. Option D incorrectly assigns estimation responsibility to the Product Owner. Estimation is performed by the Scrum Team, because those performing the work are best positioned to judge its technical complexity and effort.

Story points consequently support velocity measurement and future forecasting without pretending that complex knowledge work can always be predicted precisely in hours.

Study Guide reference: Plan and Estimate - > Estimate User Stories - > Relative Sizing/Story Points.

========

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.

========

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.

========

Option A most accurately reflects the Product Owner's authority during backlog refinement and change management. The Product Owner decides which stakeholder input is relevant, evaluates suggested changes, and determines which changes should progress as formal Change Requests or be incorporated into the Prioritized Product Backlog.

Option B is incorrectly worded. The Scrum Master protects committed Sprint requirements and Acceptance Criteria throughout the active Sprint, not merely during the Sprint Review Meeting. The distinction matters because the Sprint Review occurs at the end of the Sprint and is specifically intended to validate completed deliverables and obtain feedback.

Option C describes development work that belongs to the Scrum Team. Stakeholders provide requirements, feedback, and Change Requests; they do not directly incorporate features into Sprint Deliverables.

Option D improperly gives the Scrum Team unilateral business authority over an urgent requirement change. Significant business changes are evaluated through the Product Owner/change-management mechanism. If a change is critical enough to invalidate current Sprint work, the Sprint can be terminated and replanned through the applicable Scrum governance process.

Therefore, A is the correctly matched responsibility.

Study Guide reference: Change - > Integrating Change; Product Owner Responsibilities; Groom/Refine Prioritized Product Backlog.

========

Velocity measures the amount of estimated work successfully completed by a Scrum Team during a Sprint. Where User Stories are estimated in story points, Sprint velocity is normally calculated by totaling the story-point values of the User Stories completed during that Sprint. SCRUMstudy explicitly describes velocity in these terms.

Velocity is particularly useful because historical values can support future Sprint planning and release forecasting. After several Sprints, a reasonably stable team can use its observed velocity to estimate how much work it is realistically capable of completing in a similar Sprint.

Business Value Delivered measures value rather than effort points. Number of Stories counts items without considering their relative size—a Sprint containing five small stories is not necessarily equivalent to one containing five large stories. A Sprint Burndown Chart shows remaining work over time during the Sprint rather than defining the quantity of story points successfully delivered.

Therefore, the metric that directly captures the number of completed story points per Sprint is Velocity.

Study Guide reference: Plan and Estimate - > Estimation; Implement - > Sprint Metrics; Velocity and Story Points.

========

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.

========

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.

========

SCRUMstudy defines the Scrum Master primarily as a facilitator who ensures that the Scrum Team is provided with an environment conducive to successfully completing product development.

Options A and B describe Product Owner responsibilities. The Product Owner is responsible for maximizing business value, representing the Voice of the Customer, articulating customer requirements, and maintaining the business justification of the project. The Scrum Master supports these processes but does not own them.

Option C also improperly combines responsibilities. In larger Scrum initiatives, scaled roles such as Chief Scrum Master, Program Scrum Master, Chief Product Owner, or Program Product Owner may coordinate corresponding roles across teams or projects. A standard Scrum Master is not responsible for maintaining business justification across multiple Product Owners.

The Scrum Master's central duties instead include facilitating Scrum processes and meetings, coaching participants, removing impediments, protecting the team from disruptive interference, and maintaining a working environment in which a self-organizing team can succeed.

Therefore, D precisely reflects the SBOK definition.

Study Guide reference: Organization - > Core Roles - > Scrum Master; Product Owner; Supporting/Servant Leadership.

========