SMC Scrum Master Certified (SMC) Questions and Answers

An Epic represents a high-level requirement that is generally too large or insufficiently detailed to be completed as a single User Story within one Sprint. As an Epic rises in priority and approaches implementation, it is progressively elaborated and decomposed into smaller User Stories.

SCRUMstudy explicitly states that some Epics/User Stories are initially too large to handle within one Sprint and are therefore broken into smaller User Stories when they move high enough in the Prioritized Product Backlog to be considered for upcoming Sprint work.

Smaller User Stories improve estimation, clarification, testability, and the team's ability to create potentially shippable increments within the Sprint time-box. They also enable the Product Owner to prioritize individual pieces of functionality according to value rather than treating a large requirement as one indivisible block.

Option A may be an indirect benefit but is not the fundamental reason. Team size does not determine whether an Epic must be decomposed, and review duration is not the defining criterion.

Therefore, the correct answer is that Epics are too large to be completed within a single Sprint.

Study Guide reference: Plan and Estimate - > Create User Stories - > Decomposition of Epics.

========

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

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.

========

Done Criteria establish the common quality conditions that apply across User Stories and provide a consistent basis for determining whether work is complete. The SBOK framework identifies activities such as completed unit testing, completed documentation, quality-assurance activities, peer review, resolution of issues, and successful demonstrations as legitimate examples of Done Criteria.

The critical distinction in this question is statement I. A list of issues to be fixed means unresolved work remains. That is different from the SBOK concept that all relevant issues are fixed before the item satisfies the Done Criteria. Therefore, simply maintaining a list of outstanding problems cannot itself establish completion.

Unit testing is directly associated with confirming technical quality. Documentation may be required to satisfy organizational, regulatory, operational, or support requirements. Demonstration to stakeholders or business representatives can also form part of the general completion conditions established for the project. Consequently, statements II, III, and IV are appropriate, while statement I is not properly worded as a completion condition.

Study Guide reference: Quality - > Done Criteria; Create Prioritized Product Backlog - > establishment of Done Criteria; distinction between Done Criteria and User Story Acceptance Criteria.

========

A deliverable does not become Accepted merely because the Scrum Team believes development is complete. Formal acceptance occurs when the Product Owner evaluates the deliverable against the agreed User Story Acceptance Criteria and accepts the associated User Story.

SCRUMstudy states that Acceptance Criteria are objective conditions used to judge User Story functionality. At the end of a Sprint, the Product Owner uses those criteria to verify completed deliverables and either accepts or rejects them. When accepted, the corresponding User Story is considered Done.

Option A lacks Product Owner validation. Option C reflects a team's assessment that work may be potentially shippable, but that does not independently constitute formal acceptance. Option D addresses internal testing and quality verification, which are necessary components of producing Done work but are insufficient by themselves to create an Accepted Deliverable.

This distinction separates technical completion from business acceptance. The Scrum Team builds and verifies the increment; the Product Owner determines whether the agreed business conditions have been fulfilled.

Therefore, B provides the correct definition.

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

========

The Initiate phase establishes the foundation of the Scrum project. SCRUMstudy identifies its processes as Create Project Vision, Identify Scrum Master and Business Stakeholder(s), Form Scrum Team, Develop Epic(s), Create Prioritized Product Backlog, and Conduct Release Planning. Therefore, identifying the Scrum Master and relevant stakeholders is explicitly an Initiate-phase activity.

The remaining options belong to later phases. Estimating and committing User Stories form part of Plan and Estimate, where requirements selected from the Prioritized Product Backlog are analyzed, estimated, and committed for upcoming Sprint work. Conduct Daily Standup belongs to Implement, because it occurs while the Scrum Team is executing Sprint work and synchronizing daily activities.

This phase separation is important in SMC questions. Initiate establishes the vision, roles, high-level requirements, prioritized backlog, and initial release structure. Plan and Estimate converts prioritized requirements into executable Sprint-level work. Implement concerns actual creation of deliverables and daily coordination.

Accordingly, Identify Scrum Master and Stakeholder(s) is the only option that is explicitly part of the Initiate phase.

Study Guide reference: Initiate - > Identify Scrum Master and Business Stakeholder(s); Plan and Estimate - > Estimate/Commit User Stories; Implement - > Conduct Daily Standup.

========

Statement C is false because risks differ substantially in both probability and impact. Risk assessment exists precisely to distinguish more significant risks from less significant ones.

SCRUMstudy defines risk as an uncertain event or set of events capable of affecting project objectives positively or negatively. Positive risks are called opportunities, while negative risks are threats.

Risk management is iterative and begins during project initiation, continuing throughout the project lifecycle. Risks are assessed primarily on their probability of occurrence and potential impact. Risks with high probability and high impact should generally receive greater attention than low-probability, low-impact risks.

This prioritization enables limited resources to be allocated rationally. Techniques such as Probability Impact Grids, Probability Trees, Expected Monetary Value, and Pareto Analysis help teams assess and compare exposures.

Therefore, the claim that all risks possess equal probability and impact directly contradicts the central mechanism of SBOK risk assessment and prioritization.

Study Guide reference: Risk - > Definition of Risk; Risk Assessment and Risk Prioritization.

========

Among the options given, the Retrospect Project Meeting is the correct answer. SBOK describes this meeting as being conducted after the project to determine ways in which team collaboration and effectiveness can be improved in future projects. Participants examine successes, failures, inefficiencies, and potential improvement opportunities and document lessons learned.

At Sprint level, the equivalent continuous-improvement event is the Retrospect Sprint Meeting, where the team determines what to continue, start, or stop doing in future Sprints. However, that choice is not present in this question.

Sprint Planning is concerned with selecting and planning upcoming Sprint work. Sprint Review/Demonstrate and Validate Sprint focuses on inspecting deliverables and obtaining Product Owner/stakeholder feedback. “Review Project Meeting” is not the defined SBOK retrospective event represented here.

Because this question asks specifically about improving collaboration and effectiveness in the future, and because Retrospect Sprint is absent from the options, Retrospect Project is the correct meeting.

Study Guide reference: Release - > Retrospect Project - > Lessons Learned and Future Improvement.

========

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.

========

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.

========

Earned Value Analysis (EVA) does not primarily increase awareness of the components, activities, and development sequence of a product. EVA is fundamentally a performance-measurement technique that compares planned value, earned value, and actual cost to assess cost and schedule performance.

By contrast, a Product Breakdown Structure decomposes the product into constituent components, increasing understanding of what must be created. A Work Breakdown Structure organizes the work required to create project outputs, improving awareness of activities and relationships. A Product Flow Diagram illustrates the sequence in which product components are created or integrated.

These techniques support the awareness dimension of collaboration because team members can understand what work exists, how components relate, and how activities interact. SBOK defines collaboration in terms of awareness, articulation, and appropriation, with awareness involving knowledge of one another's work and the overall project environment.

Earned Value Analysis instead measures performance against a baseline and therefore does not directly perform the structural or workflow-visualization function described in the question.

Study Guide reference: Principles - > Collaboration - > Awareness; project/product visualization techniques.

========

For a large project involving multiple Scrum Teams, coordination is commonly achieved through a Scrum of Scrums (SoS) Meeting. SCRUMstudy states that this meeting is usually facilitated by the Chief Scrum Master, whose focus is coordination and integration across the participating Scrum Teams.

Representatives from each Scrum Team attend the SoS meeting. In many cases, the representative is the individual team's Scrum Master, although another technically knowledgeable team member may represent the team when appropriate. These representatives provide status information, identify inter-team impediments and dependencies, and disclose activities that could affect other teams.

The Chief Product Owner is concerned principally with coordinating product and business-value matters across multiple Product Owners, not with facilitating the Scrum of Scrums. Option D, “Scrum Master,” is less precise because the question describes the designated scaled-project facilitation role. Although another Scrum Master can sometimes facilitate an SoS, the defined role in the standard large-project structure is the Chief Scrum Master.

Therefore, B is the expected SMC answer.

Study Guide reference: Organization - > Scrum in Large Projects - > Chief Scrum Master; Scrum of Scrums Meeting.

========

Statements II and IV are correct.

SBOK describes the Retrospect Project Meeting as a forum where the project participants examine positives, negatives, and potential opportunities for improvement. The meeting also explicitly captures and documents lessons learned so that they can be internalized and applied to future projects.

Statement III is false because the Retrospect Project Meeting is not Time-boxed, although it may indeed be conducted physically or virtually. Because the statement combines one false and one true condition, the complete statement is false.

Statement I is not an accurate description of the principal meeting objective. Scrum Guidance Body recommendations may address mechanisms for maintaining organizational knowledge, but the Retrospect Project Meeting itself primarily examines overall project experience, team effectiveness, collaboration, lessons, and improvement opportunities.

This meeting differs from Retrospect Sprint in scope. Retrospect Sprint seeks improvements for subsequent Sprints within an ongoing project, whereas Retrospect Project captures broader learning after completion.

Therefore, statements II and IV are the supported pair.

Study Guide reference: Release - > Retrospect Project - > Retrospect Project Meeting and Lessons Learned.

========

Ownership of grooming—or in current terminology, refining—the Prioritized Product Backlog belongs primarily to the Product Owner, not the Scrum Master. SCRUMstudy explicitly states that the Product Owner leads backlog refinement, adds or revises User Stories, reprioritizes work, and ensures upcoming requirements are sufficiently refined.

The Scrum Master may facilitate Prioritized Product Backlog Review Meetings and help ensure that communication, estimation, and Scrum practices remain effective, but facilitation is not the same as owning or grooming the backlog.

The Scrum Master also coordinates creation of the Release Planning Schedule as part of Conduct Release Planning. SCRUMstudy's role mapping explicitly lists that responsibility.

Similarly, the Scrum Master can represent Scrum Core Team experience and lessons learned so that organizational knowledge and Scrum Guidance Body recommendations can improve.

The critical distinction is between facilitating backlog refinement and being accountable for the contents and prioritization of the backlog. The latter belongs to the Product Owner.

Therefore, A is the activity that is not a Scrum Master responsibility.

Study Guide reference: Organization - > Scrum Master Responsibilities; Implement - > Groom/Refine Prioritized Product Backlog.

========

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.

========

Scrum is especially valuable where requirements are uncertain, changing, innovative, or dependent on continuing stakeholder feedback. All three scenarios possess one or more of these characteristics.

Vault Safe involves a new and innovative product. Innovation normally brings technical uncertainty and evolving understanding, making iterative development and frequent inspection advantageous. Paint Pro operates in a competitive market where features may have to change frequently; Scrum allows the Prioritized Product Backlog to evolve as market information changes. Money Manager combines expanding functional needs with changing security requirements, creating precisely the kind of dynamic environment in which short Sprints, backlog reprioritization, and stakeholder feedback help reduce risk.

SCRUMstudy explicitly states that Scrum can be applied to products, services, and projects across industries and across varying levels of size and complexity. It is not restricted to simple software projects or projects with completely known requirements.

Thus each project can benefit from iterative delivery, continuous feedback, adaptation, and value-based prioritization. Because A, B, and C are all suitable, the correct response is D.

Study Guide reference: Introduction to Scrum - > Applicability of Scrum; Principles - > Iterative Development and Empirical Process Control.

========

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 description corresponds to the Scrum Guidance Body (SGB). The SGB can provide organizational guidance, standards, regulations, recommended practices, templates, procedures, and lessons learned that Scrum Core Teams may use when appropriate.

In the backlog-refinement context, Scrum Guidance Body Recommendations can include guidance on how to understand and collate requirements, prioritize the backlog, document User Stories appropriately, and communicate changes to relevant participants.

Subject Matter Experts provide specialized knowledge based on particular technical or business domains, but the question specifically refers to documented organizational rules, development guidelines, standards, and best practices, which are characteristic of the Scrum Guidance Body.

Team Expertise refers to the collective capability of Scrum Team members to understand and execute Sprint work. Stakeholders contribute requirements, business needs, feedback, and priorities, but they are not the repository responsible for organizational Scrum standards.

The Scrum Guidance Body therefore provides consistency without converting Scrum into a centralized command-and-control methodology. Its recommendations support teams while still allowing appropriate tailoring.

Study Guide reference: Implement - > Groom/Refine Prioritized Product Backlog - > Scrum Guidance Body Recommendations.

========

Acceptance Criteria are the objective conditions by which the functionality of a User Story is judged. They enable the Product Owner to determine whether the completed deliverable satisfies the agreed requirement and whether the associated User Story can be accepted as Done. SCRUMstudy specifically emphasizes the objectivity of Acceptance Criteria and the Product Owner's authority to accept or reject work against them.

Option C is incorrect because Acceptance Criteria are defined primarily by the Product Owner, based on understanding of customer requirements. The Scrum Master facilitates Scrum and protects the integrity of the Sprint but does not own those business acceptance conditions.

Option D places acceptance in the wrong meeting. Acceptance occurs during Demonstrate and Validate Sprint/Sprint Review, not during Retrospect Sprint. The retrospective concerns lessons learned and process improvement.

Option A similarly confuses activities and meetings.

Therefore, the core purpose of Acceptance Criteria is to provide measurable, objective conditions against which a User Story can be judged Done or not Done.

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

========

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

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

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.

========

Successful release depends fundamentally on the Scrum Team creating the agreed deliverables so that completed and accepted work can eventually be transitioned to the customer or other relevant business stakeholders. The Release phase's Ship Deliverables process handles accepted deliverables, while the Product Owner coordinates deployment with the customer.

Option B describes activities associated with the Product Owner following validation and backlog/release-plan management rather than the specific condition the Scrum Master must ensure for successful creation of releasable work.

Option C is incorrect because the Release Planning Schedule is developed during Conduct Release Planning, involving the Product Owner and Scrum Core Team; it is not simply created by the Scrum Team during Ship Deliverables.

Option D incorrectly assigns acceptance authority. During Demonstrate and Validate Sprint, the Product Owner, not the Scrum Team, accepts or rejects completed User Stories against their Acceptance Criteria.

Therefore, ensuring that the Scrum Team creates the committed deliverables as agreed provides the necessary basis for later acceptance and release.

Study Guide reference: Release - > Ship Deliverables; Implement - > Create Deliverables; Review and Retrospect - > Demonstrate and Validate Sprint.

========

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.

========

The intended process relationship is represented by option D. In the terminology used by this question set, Groom Prioritized Product Backlog continuously maintains and updates the backlog. A formal Prioritized Product Backlog Review Meeting is one of the principal mechanisms used to review requirements, obtain feedback, clarify User Stories, and incorporate appropriate changes. The resulting backlog is therefore updated and reprioritized.

Current SCRUMstudy materials use the term Refine Prioritized Product Backlog rather than “Groom,” but the underlying concept remains essentially the same: the Product Owner leads backlog maintenance with input from the Scrum Master, Scrum Team, and relevant business stakeholders.

Accepted Deliverables belong to Demonstrate and Validate Sprint, while the Sprint Backlog is created in planning rather than as the output of backlog refinement. Likewise, a Retrospect Sprint Meeting focuses on lessons learned and actionable improvements.

Thus, the valid Input/Tool/Output combination among the choices is D.

Study Guide reference: Implement - > Groom/Refine Prioritized Product Backlog - > Prioritized Product Backlog Review Meeting - > Updated Prioritized Product Backlog.

========

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.

========

Statements II and III are incorrect.

Rejected Deliverables are not normally maintained in a separate list. If a deliverable fails the Acceptance Criteria, the associated backlog work remains unresolved and is returned or retained in the Prioritized Product Backlog so that the Product Owner can reprioritize it for future development. SCRUMstudy explicitly states that rejected deliverables normally remain in the backlog rather than being placed in a separate repository.

Statement III also contradicts backlog refinement. The purpose of Groom/Refine Prioritized Product Backlog is to maintain a relevant, current, prioritized set of requirements. Items may be added, modified, reprioritized, refined, or removed when they cease to contribute sufficient business value or become obsolete.

Statement I is valid because backlog refinement can involve the Product Owner, Scrum Master, Scrum Team, and relevant stakeholders across multiple review interactions. Statement IV is also conceptually valid: changes in internal or external business conditions can generate changes at program level that subsequently affect project backlogs.

Current SCRUMstudy terminology uses Refine Prioritized Product Backlog, replacing the older term “Groom.”

Study Guide reference: Implement - > Groom/Refine Prioritized Product Backlog; Rejected Deliverables; Prioritized Product Backlog Review Meeting.

========