Free Scrum-Master-Certified sample questions

Correct answer: Coach the Product Owner on techniques for managing stakeholder expectations and explaining the impact of mid-sprint changes on the Sprint Goal.

The Scrum Master's role is to facilitate and coach, not dictate. The Product Owner is responsible for managing the Product Backlog and stakeholder communication. The most effective, long-term solution is to empower the Product Owner with better techniques to handle these situations, thus protecting the Sprint, respecting the PO's role, and improving the overall process.

Correct answers: The primary responsibility for this process lies with the Product Owner.; This process ensures that User Stories at the top of the backlog are ready for the next Sprint Planning meeting.

Correct answer: True

To create a potentially shippable, integrated increment at the end of each Sprint, all teams must adhere to a common, minimum Definition of Done. While individual teams can have a more stringent DoD for their own work, they must all meet the shared baseline to ensure consistency and quality across the entire product.

Correct answer: Project Vision Statement

The Project Vision Statement is a key output of the 'Create Project Vision' process. It is a high-level summary that articulates the project's goals and what it aims to achieve, providing a clear direction for the entire project.

Correct answer: The team has not yet established a baseline velocity and a common understanding of relative effort.

For a new team, estimation is challenging because they have no historical data (velocity) to base their estimates on. Furthermore, techniques like Story Points rely on a shared, relative understanding of effort, which takes time for a new team to develop through collaboration and experience over a few Sprints.

Correct answer: Organize a workshop for both the Product Owner and the Development Team focused on clarifying Scrum roles, responsibilities, and the importance of adhering to the Sprint Goal.

The core problem stems from a misunderstanding of Scrum roles and principles by both the Product Owner and the Development Team. The PO is bypassing the backlog process, and the team is not focusing on delivering value as defined by the User Stories (gold-plating). A dedicated workshop facilitated by the Scrum Master is the most effective way to educate both parties, re-establish the proper communication channels (PO to team via backlog), and reinforce the concept of the Sprint Goal to prevent scope creep and over-engineering.

Correct answer: Self-organization

Self-organization is the principle that recognizes that team members are best equipped to manage their own work. It promotes ownership, creativity, and motivation by trusting the team to determine how to best accomplish their goals, leading to higher efficiency and effectiveness.

Correct answer: The Risk aspect, which is managed iteratively through risk-adjusted backlogs, frequent reviews, and making risks visible in meetings like the Daily Standup.

The SBOK® Guide explicitly defines Risk as one of the five Scrum Aspects. In Scrum, risk management is not a separate, upfront phase but an iterative and continuous activity. Risks are identified and assessed throughout the project, prioritized, and their mitigation can be incorporated into the Prioritized Product Backlog. The transparency of Scrum events helps in making risks visible early and often.

Correct answers: Accepted Deliverables; Updated Prioritized Product Backlog; Updated Release Plan

The 'Demonstrate and Validate Sprint' process (Sprint Review) results in the Product Owner formally accepting deliverables that meet the Acceptance Criteria. Based on the demonstration and stakeholder feedback, both the Prioritized Product Backlog and the high-level Release Plan may be updated to reflect new insights, changed priorities, or adjusted timelines.

Correct answer: In the Acceptance Criteria for the specific User Story or Epic.

Acceptance Criteria are specific to a single User Story and define the conditions that must be met for that story to be accepted by the Product Owner. Non-functional requirements like performance benchmarks that are unique to a feature belong here. The Definition of Done is a broader checklist that applies to ALL User Stories to ensure a baseline level of quality.