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.

========

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.

========

The Scrum Master facilitates the identification, assessment, communication, and escalation of problems and Change Requests generated by the Scrum Team. The Product Owner then evaluates business impact and determines how approved changes should be prioritized within the Prioritized Product Backlog. This separation preserves both facilitation and business accountability.

Option A is contrary to Scrum. Scrum does not attempt to eliminate change; it deliberately accommodates change while maintaining stability during the active Sprint.

Option C is primarily a Product Owner/business stakeholder responsibility when interpreted as formally submitting project changes. Scrum Team members and the Scrum Master may suggest improvements, but the Scrum Master's principal defined change-management responsibility is facilitation, not ownership of business Change Requests.

Option D incorrectly gives approval authority to the Scrum Master. Formal change approval and prioritization are driven by the Product Owner within organizational tolerance levels and applicable Scrum Guidance Body procedures.

Consequently, B accurately reflects the Scrum Master's servant-leadership role: enabling the Scrum Team to surface necessary changes and ensuring that those changes reach the appropriate Product Owner decision process.

Study Guide reference: Change - > Summary of Responsibilities Relevant to Change; Change Requests; Product Owner prioritization.

========

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.

========

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.

========

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.

========

After development is completed, the increment must be validated and demonstrated. The Scrum Team is responsible for ensuring that Sprint Deliverables satisfy the agreed quality conditions before presenting them in the Sprint Review/Demonstrate and Validate Sprint process. During that review, the team demonstrates completed functionality to the Product Owner and relevant business stakeholders, including customers or users where appropriate.

Acceptance Criteria provide the objective basis for checking whether a User Story satisfies the required functionality. Formal acceptance or rejection authority belongs to the Product Owner, not the Scrum Master.

Consequently, statement II is incorrect: the Scrum Master does not independently deploy the functionality into production merely because Sprint development has finished. Release is a business decision and follows the appropriate Ship Deliverables process. Statement IV is also incorrect because the Scrum Master cannot reject a User Story based on stakeholder feedback.

Statements I and III correctly represent demonstration and validation activities associated with completed Sprint work. Therefore, A is the intended answer.

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

========

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 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.

========

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.

========