Score Higher on Verified SMC | Scrum Master Certified (SMC) Exam Questions with Answers

A Gap Analysis is specifically used to compare the organization's current or actual state with a desired future state. SCRUMstudy defines it as identifying and documenting the difference between existing business capabilities and the final desired set of capabilities.

That wording directly matches the scenario.

A SWOT Analysis examines strengths, weaknesses, opportunities, and threats and is useful when establishing context, priorities, risks, and strategic direction. A Joint Application Development (JAD) session is a facilitated workshop used to gather and refine requirements through direct collaboration. A Trial Project may be used to test an approach, but it does not specifically quantify or document capability differences.

Gap Analysis helps decision-makers determine what capabilities are missing, where improvement is required, and therefore why a project or program may be needed. The results can contribute directly to development of the Project Vision and later business requirements.

Therefore, because the scenario asks for comparison between current capability and desired capability, Gap Analysis is unambiguous.

Study Guide reference: Initiate - > Create Project Vision - > Gap Analysis.

========

The Create Deliverables process is an Implement-phase activity in which the Scrum Team executes the tasks contained in the Sprint Backlog and creates the Sprint Deliverables. SCRUMstudy describes this process as the team working on Sprint Backlog tasks to produce deliverables while using mechanisms such as the Scrumboard and Impediment Log to manage execution.

Options A, C, and D can represent tangible or project-specific results produced through Sprint execution. Construction work, an updated engineering blueprint, and completed seismic retrofit work can each constitute deliverables when they correspond to committed Sprint Backlog items and satisfy the applicable Done Criteria.

Raw materials acquired for the next Sprint, however, represent preparation or resource procurement for future work rather than a deliverable generated from execution of the current Sprint Backlog. The defining output of Create Deliverables is completed work resulting from the current Sprint's committed tasks, not inventory accumulated for subsequent iterations.

Therefore, B is the exception.

Study Guide reference: Implement - > Create Deliverables - > Sprint Backlog execution, Sprint Deliverables, Scrumboard, Impediment Log.

========

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.

========