The technically relevant principle is that business justification must be reassessed whenever major issues or risks threaten viability, making D the intended answer. SBOK states that business justification is initially assessed before project initiation and continuously verified throughout the lifecycle. Verification occurs at predefined intervals or milestones and also whenever significant issues or risks arise that could undermine the rationale for continuing the investment.

Option C overstates “continuous” by interpreting it as literal day-to-day formal review. Continuous Value Justification means that viability remains subject to ongoing validation; it does not require a complete business-case reassessment every working day. Option A is too late because justification must be maintained while investment decisions can still be changed. Option B imposes an every-Sprint portfolio review requirement that SBOK does not establish universally.

The question's repeated use of “portfolio business justification” is imperfectly aligned with the opening reference to a Product Owner. Strictly, project-level business justification is owned primarily by the Product Owner, while portfolio-level justification belongs to the Portfolio Product Owner. Nevertheless, the substantive business-justification trigger described in D is correct.

Study Guide reference: Business Justification - > Continuous Value Justification; Project Viability; Major Issues and Risks.

========

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.

========

The technique described is Expected Monetary Value (EMV). EMV translates an uncertain event into a monetary risk exposure by multiplying its probability of occurrence by its financial impact.

For the scenario:

EMV = Probability × Monetary Impact

EMV = 0.45 × (-$800,000) = -$360,000

The negative sign represents an expected loss. Thus, the risk contributes an expected monetary exposure of $360,000 to the economic analysis of the project. EMV is particularly useful when comparing uncertain alternatives or integrating risk into business-justification calculations.

A Probability Impact Grid classifies risks according to probability and impact, typically for prioritization; it does not primarily calculate monetary expectation. Pareto Analysis identifies the relatively small number of causes responsible for the largest proportion of effects. A Risk Breakdown Structure categorizes risks hierarchically according to source or similarity.

Because the question explicitly supplies both a percentage probability and a monetary loss, EMV is the technique being applied.

Study Guide reference: Business Justification/Risk - > Risk Assessment Techniques - > Expected Monetary Value; financial analysis of uncertainty.

========

The intended exam answer is A — Better Team Coordination. In the legacy SBOK structure from which this question originates, Better Team Coordination is identified as a principal output of Convene Scrum of Scrums, not Demonstrate and Validate Sprint. That process focuses on coordination and integration among multiple Scrum Teams.

Demonstrate and Validate Sprint instead centers on showing completed Sprint work to the Product Owner, applying Acceptance Criteria, and obtaining acceptance or rejection. Legacy SBOK editions list Accepted Deliverables and Updated Dependencies among its outputs.

There is an important technical issue with this older question: the same legacy SBOK process tables also place Updated Impediment Log under Convene Scrum of Scrums rather than Demonstrate and Validate Sprint. Consequently, the question bank contains an overlapping distractor and is not perfectly constructed when checked literally against those process-output tables.

For exam-intent purposes, A is the expected response because Better Team Coordination is the distinctive mandatory output associated with Scrum of Scrums. Current SBOK editions have also revised process terminology and outputs, reinforcing the need to interpret this as a legacy SMC item.

Study Guide reference: Review and Retrospect - > Demonstrate and Validate Sprint; legacy Convene Scrum of Scrums outputs.

========

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.

========

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 Prioritized Product Backlog is based primarily on value, risk or uncertainty, and dependencies. SCRUMstudy explicitly identifies these three factors when explaining the structure and prioritization of the backlog.

Value represents the business benefit expected from delivering the functionality. Higher-value items may be prioritized earlier so that useful business outcomes begin to accrue sooner. Risk and uncertainty are considered because addressing uncertain or high-risk work earlier can expose assumptions, enable mitigation, and prevent late discovery of critical problems. Dependencies influence sequencing because some requirements cannot be effectively developed before prerequisite functionality is available.

“Deliverables” are results produced through execution of backlog items; they are not one of the three primary prioritization factors specified in the SBOK model.

The combination of value, risk, and dependencies reflects Scrum's broader principles of value-based prioritization and adaptive planning. Prioritization is therefore more sophisticated than merely ordering requirements by desired functionality.

Consequently, statements I, II, and III are correct.

Study Guide reference: Business Justification - > Value-based Prioritization; Initiate - > Create Prioritized Product Backlog; Risk - > Risk-adjusted Backlog.

========

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.

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

========