SMC Scrum Master Certified (SMC) Free Practice Exam Questions (2026 Updated)

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.

========

Within the SBOK framework reflected by this SMC question set, the recommended Scrum Team size is six to ten members. This range is intended to provide enough cross-functional capability to create the Sprint deliverables while keeping coordination and communication manageable.

If a team becomes too large, communication channels increase rapidly, meetings become more difficult to manage, self-organization becomes less efficient, and individual accountability can become diluted. Large projects are therefore normally handled through multiple Scrum Teams coordinated using mechanisms such as Scrum of Scrums rather than by constructing a single excessively large team.

Conversely, a very small team may not contain sufficient breadth of skills to function cross-functionally or may become vulnerable when one person is unavailable.

Therefore, among the choices presented, six to ten is the intended SBOK answer.

Study Guide reference: Organization - > Scrum Team - > Team Size and Personnel Selection; Scaling Scrum - > formation of multiple Scrum Teams for larger projects.

========

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.

========

Ownership of grooming—or in current terminology, refining—the Prioritized Product Backlog belongs primarily to the Product Owner, not the Scrum Master. SCRUMstudy explicitly states that the Product Owner leads backlog refinement, adds or revises User Stories, reprioritizes work, and ensures upcoming requirements are sufficiently refined.

The Scrum Master may facilitate Prioritized Product Backlog Review Meetings and help ensure that communication, estimation, and Scrum practices remain effective, but facilitation is not the same as owning or grooming the backlog.

The Scrum Master also coordinates creation of the Release Planning Schedule as part of Conduct Release Planning. SCRUMstudy's role mapping explicitly lists that responsibility.

Similarly, the Scrum Master can represent Scrum Core Team experience and lessons learned so that organizational knowledge and Scrum Guidance Body recommendations can improve.

The critical distinction is between facilitating backlog refinement and being accountable for the contents and prioritization of the backlog. The latter belongs to the Product Owner.

Therefore, A is the activity that is not a Scrum Master responsibility.

Study Guide reference: Organization - > Scrum Master Responsibilities; Implement - > Groom/Refine Prioritized Product Backlog.

========

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.

========

Statements II and IV are correct.

SBOK describes the Retrospect Project Meeting as a forum where the project participants examine positives, negatives, and potential opportunities for improvement. The meeting also explicitly captures and documents lessons learned so that they can be internalized and applied to future projects.

Statement III is false because the Retrospect Project Meeting is not Time-boxed, although it may indeed be conducted physically or virtually. Because the statement combines one false and one true condition, the complete statement is false.

Statement I is not an accurate description of the principal meeting objective. Scrum Guidance Body recommendations may address mechanisms for maintaining organizational knowledge, but the Retrospect Project Meeting itself primarily examines overall project experience, team effectiveness, collaboration, lessons, and improvement opportunities.

This meeting differs from Retrospect Sprint in scope. Retrospect Sprint seeks improvements for subsequent Sprints within an ongoing project, whereas Retrospect Project captures broader learning after completion.

Therefore, statements II and IV are the supported pair.

Study Guide reference: Release - > Retrospect Project - > Retrospect Project Meeting and Lessons Learned.

========

Earned Value Analysis (EVA) does not primarily increase awareness of the components, activities, and development sequence of a product. EVA is fundamentally a performance-measurement technique that compares planned value, earned value, and actual cost to assess cost and schedule performance.

By contrast, a Product Breakdown Structure decomposes the product into constituent components, increasing understanding of what must be created. A Work Breakdown Structure organizes the work required to create project outputs, improving awareness of activities and relationships. A Product Flow Diagram illustrates the sequence in which product components are created or integrated.

These techniques support the awareness dimension of collaboration because team members can understand what work exists, how components relate, and how activities interact. SBOK defines collaboration in terms of awareness, articulation, and appropriation, with awareness involving knowledge of one another's work and the overall project environment.

Earned Value Analysis instead measures performance against a baseline and therefore does not directly perform the structural or workflow-visualization function described in the question.

Study Guide reference: Principles - > Collaboration - > Awareness; project/product visualization techniques.

========

The standard SBOK User Story format is:

As a < role/persona > , I should be able to < requirement > so that < benefit > .

A User Story therefore expresses three essential dimensions: Who, What, and Why. The “Why” component identifies the benefit or value expected from satisfying the requirement.

Option D directly corresponds to that third component: What benefit is expected from the requirement? This helps ensure that functionality is connected to user or business value rather than being treated simply as an isolated technical request.

Cost of development is addressed through estimation and business-justification activities rather than the core User Story template. The specific individual responsible for performing the work is not embedded in a User Story because Scrum Teams are self-organizing and determine task ownership during planning and execution. Testing techniques may influence tasks or Acceptance Criteria but are not one of the three core User Story template elements.

Therefore, the expected benefit is the relevant question.

Study Guide reference: Plan and Estimate - > Create User Stories - > User Story Template: Role/Persona, Requirement, Benefit.

========

Statements I and II correctly describe how the Scrum Core Team can originate proposed changes. SBOK explains that ongoing interaction among the Product Owner, Scrum Master, Scrum Team, and stakeholders may lead Scrum Core Team members to suggest changes or product improvements. Recommendations commonly arise while creating deliverables, during Daily Standups, and particularly through the Retrospect Sprint process.

Statement IV is incorrect because the Scrum Master does not finalize formal Change Requests. The Product Owner has the decision authority to determine which suggested changes should become formal Change Requests and how approved changes should be prioritized in the Prioritized Product Backlog.

Statement III is not the applicable SBOK responsibility in the form stated here. Escalation beyond defined tolerances can involve other organizational authorities, but that does not make the Scrum Master the authority for finalizing or approving the change.

Thus, the technically supported statements are I and II. This also reinforces Scrum's separation between proposing/facilitating change and business prioritization/approval.

Study Guide reference: Change - > Change Requests - > Scrum Core Team; Retrospect Sprint; Product Owner authority over Prioritized Product Backlog.

========