Authentic Scrum Certification Exam SMC Questions Answers

The Prioritized Product Backlog is not a tool of the Create Deliverables process. In the legacy SBOK process structure underlying this question, the principal Create Deliverables tools include Team Expertise, Software, Other Development Tools, and Scrum Guidance Body Expertise. Other Development Tools may include techniques such as refactoring and Design Patterns.

Team Expertise represents the collective technical and functional knowledge used by Scrum Team members to transform Sprint work into finished deliverables. Software tools may support scheduling, collaboration, tracking, information distribution, and project execution. Design Patterns provide reusable approaches for resolving recurring design problems and can therefore support creation of deliverables.

The Prioritized Product Backlog serves a different function: it represents the prioritized project requirements maintained by the Product Owner. During the Sprint itself, the Scrum Team executes work from the Sprint Backlog, which contains the committed work for that Sprint.

Therefore, although the Prioritized Product Backlog ultimately drives what enters future Sprints, it is not classified as a Create Deliverables tool.

Study Guide reference: Implement - > Create Deliverables - > Inputs and Tools.

========

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.

========

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.

========