Free and Premium Scrum SMC Dumps Questions Answers

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.

========

The Prioritized Product Backlog is not listed as an input to the SBOK Conduct Daily Standup process. In the relevant SBOK process model, inputs include the Scrum Team, Scrum Master, Scrumboard, Impediment Log, Sprint Burndown/Burnup Chart, Product Owner, previous workday experience, and dependencies. The Product Owner is not mandatory for the meeting, but may contribute as an input to the process.

The Sprint Burndown Chart provides visibility into Sprint progress and remaining work. Dependencies may surface during the Daily Standup because they can create impediments or affect sequencing. The Product Owner may be available where clarification or business input is relevant, although the Daily Standup remains principally a Scrum Team synchronization forum.

The Prioritized Product Backlog is instead the overarching project requirements repository managed and refined through backlog processes. The active Sprint is driven by its Sprint Backlog, not by repeatedly replanning directly from the entire Prioritized Product Backlog each day.

Therefore, among the options presented, B is the exception.

Study Guide reference: Implement - > Conduct Daily Standup - > Inputs; distinction between Prioritized Product Backlog and Sprint execution artifacts.

========

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

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

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

Thus the mismatched technique-description pairing is C.

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

========

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.

========

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.

========

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.

========

Statement B is inaccurate because SBOK risk management operates across project, program, and portfolio levels. A risk may originate at the program or portfolio level yet affect one or more projects. In such circumstances, information about that risk must be communicated to the affected Product Owner and Scrum Team, while the risk can continue to be managed at the level where it originated. Serious portfolio/program risks can even cause a project team to reconsider or re-plan Sprint work.

Scrum's iterative structure also reduces exposure by creating short feedback cycles. Problems become visible sooner than in long sequential delivery models, allowing corrective action before excessive investment accumulates. Risk information can be communicated through artifacts such as Risk Burndown Charts.

Scrum's flexibility further assists risk management because approved changes can be incorporated into the Prioritized Product Backlog and prioritized for subsequent Sprints. This does not mean uncontrolled scope changes are introduced into an active Sprint; Sprint stability remains protected.

Therefore, the assertion that risks can only be managed at project level directly contradicts SBOK's treatment of program- and portfolio-level risk.

Study Guide reference: Risk - > Risks in Portfolios and Programs; Risk Identification, Assessment, Prioritization, and Communication.

========

The Project Vision Statement establishes the project's overall direction and communicates the fundamental business objective that the project is intended to achieve. During Create Project Vision, the Project Business Case is reviewed and the Project Vision Statement is produced to provide inspiration and focus for the entire project.

SCRUMstudy further emphasizes that a good project vision focuses on the business need or problem, rather than prematurely prescribing the detailed solution. It should not be so specific that adaptation becomes difficult as assumptions and requirements evolve.

Specific requirements are subsequently developed through Epics, User Stories, and the Prioritized Product Backlog. Project status is communicated through Scrum artifacts and meetings, while daily progress is tracked through mechanisms such as Daily Standups, Scrumboards, and Sprint Burndown Charts.

Consequently, the Project Vision is neither a detailed requirements specification nor a daily control document. Its primary function is to define the high-level objective and desired direction of the project.

Study Guide reference: Initiate - > Create Project Vision - > Project Business Case and Project Vision Statement.

========

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.

========

Option C reverses the actual Scrum-versus-traditional distinction. In Scrum, Return on Investment and business value can begin early and continue throughout the project lifecycle because potentially valuable increments are produced iteratively. Traditional sequential projects frequently defer realization of substantial value until the completed product is delivered. SCRUMstudy's comparison explicitly lists Scrum ROI as “early/throughout project life” and traditional ROI as occurring at the end of project life.

The other statements correctly reflect SBOK's comparison. Scrum organizations are self-organized rather than centrally managed. Scrum places greater emphasis on people and collaborative responsibility, whereas traditional management generally emphasizes formally defined processes. Scrum's quality philosophy is customer-centric and centered on delivering working outcomes that satisfy customer requirements and Acceptance Criteria, whereas traditional approaches are described as more process-centric.

Therefore, C is not merely a subtle difference—it states the ROI relationship in exactly the opposite direction.

Study Guide reference: Introduction to Scrum/Business Justification - > Scrum versus Traditional Project Management; Value-driven Delivery.

========

This scenario represents Risk Mitigation because concrete responses are being developed to reduce or manage the consequences of identified risks.

SBOK defines risk mitigation as developing an appropriate strategy to deal with risk. Mitigation can include proactive responses designed to reduce probability or impact and reactive contingency actions to be implemented if the event occurs.

Strengthening or safeguarding the infrastructure is a proactive mitigation measure because it reduces the potential physical impact of earthquakes or tsunamis. Establishing a contingency reserve provides resources that can be used reactively if the disaster actually occurs.

Risk Assessment would involve evaluating probability and potential impact but would not itself implement safeguards. Risk Prioritization would determine which identified risks require the greatest attention. Risk Avoidance would involve eliminating the underlying exposure entirely—for example, redesigning the project so that the threatened infrastructure was no longer exposed to the disaster risk.

Because the proposed actions reduce impact and prepare contingency capability rather than eliminating the risk altogether, Risk Mitigation is correct.

Study Guide reference: Risk - > Risk Management - > Risk Mitigation; Proactive and Reactive Risk Responses.

========

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.

========

All four questions are explicitly associated with the Scrum of Scrums (SoS) Meeting. The purpose of the meeting is to coordinate multiple Scrum Teams working on the same large project or on strongly interdependent work.

SCRUMstudy lists all four questions: what the team has worked on since the previous meeting; what it will work on before the next meeting; what other teams expected it to finish that remains incomplete; and what upcoming activities might affect other teams.

The first two provide cross-team visibility into progress and upcoming activity. The third exposes delayed inter-team dependencies. The fourth identifies potential future conflicts, shared-resource issues, interface changes, or other work that can affect neighboring teams.

These questions make SoS more than a status meeting. They support dependency management, early risk identification, integration, transparency, and coordination across team boundaries. The Chief Scrum Master, or another facilitating Scrum Master, normally facilitates the meeting.

Since I, II, III, and IV are all standard SoS questions, D is correct.

Study Guide reference: Organization - > Scaling Scrum - > Scrum of Scrums Meeting.

========

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.

========

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.

========

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.

========

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.

========

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.

========

A Piloting Plan is used when an organization wants to deploy a product or release initially to a controlled group before broader implementation. According to the SBOK glossary, such a plan can specify the scope and objectives of deployment, the target deployment user base, deployment schedule, transition arrangements, user preparation, evaluation criteria, and other deployment-related details.

The target user base is particularly important because a pilot must clearly identify who will receive and evaluate the initial deployment. Without a defined population, feedback cannot be interpreted reliably, operational impact cannot be controlled, and the organization cannot determine whether the pilot results are representative of the intended implementation.

Security concerns may certainly matter to a specific project, but they are not the defining element tested here. Likewise, employee-friction guidelines and synchronization methods are not identified as the fundamental element of a Piloting Plan in this context.

Therefore, specifying the target deployment user base is the choice that directly corresponds to SBOK's description of an effective Piloting Plan.

Study Guide reference: Release - > Ship Deliverables - > Organizational Deployment Methods/Piloting Plan.

========

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.

========

The Chief Scrum Master is the designated role responsible for coordinating multiple Scrum Masters and facilitating cross-team integration in a large Scrum project. The Scrum of Scrums Meeting is one of the principal mechanisms used for this purpose.

Each Scrum Team normally sends a representative—often its Scrum Master—who communicates team progress, upcoming activities, dependencies, impediments, and work that could affect other teams. The meeting allows problems spanning several teams to be identified and coordinated at an appropriate level.

A Product Owner manages business value and requirements for a product or project scope. A Portfolio Product Owner operates at the broader portfolio level and is concerned with strategic prioritization and portfolio value. A Sponsor provides business support and funding. None of these roles normally facilitates the Scrum of Scrums.

SCRUMstudy's scaling guidance describes synchronization across multiple teams as essential to large-project Scrum and assigns this coordination responsibility to scaled Scrum leadership structures.

Therefore, Chief Scrum Master is correct.

Study Guide reference: Organization - > Scrum for Large Projects - > Chief Scrum Master and Scrum of Scrums.

========

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.

========

C is the intended answer in the legacy SMC question bank, but the wording is technically defective because of the word “only.” Older SMC practice material keys C because SBOK historically described approximately 6–10 members as the ideal Scrum Team size. The intended concept is therefore that a typical individual Scrum Team should remain relatively small.

However, this must not be interpreted to mean Scrum itself can only be used when an entire project contains 6–10 people. Current SCRUMstudy guidance explicitly states that Scrum can be applied to projects of any size or complexity and can scale to large projects containing many Scrum Teams.

Options A, B, and D are clearly false: Scrum is not restricted to small projects, software development, or large corporations.

Thus, for the historical SMC item, C is the expected exam answer, but the accurate SBOK interpretation is: a Scrum Team is ideally small; Scrum as a framework is not limited to projects having only 6–10 total participants.

Study Guide reference: Introduction to Scrum - > Applicability of Scrum; Organization - > Scrum Team Size and Scaling.

========

A Burndown Chart is the appropriate artifact for comparing work remaining over time with the expected or planned rate of completion. The chart normally plots remaining work against the Sprint timeline and therefore makes deviations from the planned trajectory visible.

If the actual remaining-work line stays above the planned line, the team may be progressing more slowly than expected. If it is below the planned trajectory, work is being completed faster than originally anticipated. The objective is not to measure individual performance but to provide transparent team-level information that supports inspection and adaptation.

A Scrumboard visualizes task status through workflow columns such as To Do, In Progress, and Done, but it does not inherently plot planned versus actual progress over time. A Cumulative Flow Diagram visualizes work distribution across workflow states and can reveal bottlenecks. A Kanban Board similarly focuses on workflow visualization.

The Burndown Chart therefore provides the clearest direct representation of planned versus actual remaining work, making C correct.

Study Guide reference: Implement/Plan and Estimate - > Sprint Burndown Chart; Transparency and Progress Tracking.

========

Option A does not correctly represent Scrum collaboration because it assigns business prioritization authority to the Scrum Team. Determining which User Stories are most important is principally the Product Owner's responsibility through management of the Prioritized Product Backlog. The Scrum Team subsequently estimates, commits to, and determines how to implement the selected work.

Options B, C, and D are genuine examples of collaborative behavior. Discussing the best implementation approach represents joint problem solving by a self-organizing team. Helping another team member overcome task difficulty demonstrates collective ownership rather than rigid individual specialization. Interacting with the Product Owner for requirement clarification enables the Scrum Team to understand intended value and Acceptance Criteria.

SBOK defines collaboration around awareness, articulation, and appropriation, treating delivery as shared value creation among team members and stakeholders.

The Scrum Team participates heavily in planning and can influence what it can realistically commit to, but it does not take over Product Owner accountability for ranking User Stories according to business value.

Study Guide reference: Principles - > Collaboration; Organization - > Product Owner versus Scrum Team Responsibilities.

========

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.

========

A risk threshold identifies the point or level at which exposure changes from being acceptable to unacceptable. SCRUMstudy distinguishes risk threshold from the related concepts of risk appetite and risk tolerance. Risk appetite reflects the overall amount of uncertainty an organization is willing to pursue or accept, while risk tolerance describes the degree or volume of variation the stakeholder can withstand. The threshold establishes the boundary at which action or rejection becomes necessary.

In this scenario, some defects remain acceptable and do not prevent release. Once the defect level rises beyond a specified point, however, the deliverables will be rejected. This establishes a clear acceptance boundary, making it a textbook example of a risk threshold.

Risk seeking is a behavioral attitude in which a stakeholder is willing to accept greater uncertainty in pursuit of additional benefits. That concept does not apply here.

The decisive phrase is effectively “acceptable until this level is exceeded.” Once that boundary is crossed, the response changes. Therefore, the scenario illustrates Risk Threshold.

Study Guide reference: Risk - > Risk Attitude - > Risk Appetite, Risk Tolerance, Risk Threshold, Utility Function.

========

In the legacy SBOK Create Sprint Backlog process represented by this question, important inputs include the Effort Estimated Task List, Length of Sprint, Previous Sprint Velocity, Dependencies, and Team Calendar, together with the Scrum Core Team. Therefore, the four factors listed in option C are all legitimate inputs.

Length of Sprint defines the available time-box. Previous Sprint Velocity provides historical evidence of how much work the team has been able to complete and therefore supports realistic commitment. Dependencies influence the order in which work should be executed. The Team Calendar records member availability, including leave, holidays, and other events affecting capacity.

The remaining options introduce artifacts that do not constitute this specific combination of Sprint Backlog creation inputs, such as Proof of Concept or Done Criteria.

In newer SBOK editions, the terminology has evolved toward Update Sprint Backlog, because an initial Sprint Backlog is created when User Stories are committed and is subsequently enriched with task-level information. The underlying capacity concepts—Sprint length, dependencies, team availability, and historical performance—remain relevant.

Therefore, C is the verified legacy SMC answer.

Study Guide reference: Plan and Estimate - > Create/Update Sprint Backlog - > Inputs; Sprint Planning.

The incorrect statement targeted by this question is statement II. A Scrumboard is fundamentally a Scrum Team information radiator used to visualize and track Sprint work. SCRUMstudy explains that the team uses the Scrumboard to plan and track progress and that it can be maintained manually on paper or a whiteboard, or electronically.

Stakeholders may be able to observe the board because Scrum promotes transparency, but the board is not described as a stakeholder-owned planning and progress-control mechanism. Sprint execution remains with the self-organizing Scrum Team.

The exact number of columns has varied across SBOK editions and examples. Typical layouts include To Do, In Progress, Testing, and Done; other representations may include an additional Stories column. Therefore, the essential exam concept is not a rigid visual format but the board's role in transparently showing Sprint task status. During implementation it is continually updated as work progresses, and a fresh board is used for the subsequent Sprint.

Thus statement II incorrectly assigns ownership/use to stakeholders rather than the Scrum Team.

Study Guide reference: Implement - > Create Deliverables - > Scrumboard; Empirical Process Control - > Transparency.

========