SMC Leak Questions

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.

========