A Scrum Team at a financial services company is consistently failing to complete all committed User Stories within a Sprint. During the Sprint Retrospective, the team discovers that mid-sprint changes requested by a key stakeholder are causing significant rework. As the Scrum Master, which action best aligns with the principle of servant-leadership and protecting the team?
Answer and explanation
Correct answer: B
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.
Question 2
Multiple answers
According to the SBOK® Guide, the 'Groom Prioritized Product Backlog' process is an ongoing activity. Which of the following statements are true regarding this process? (Select TWO)
Answer and explanation
Correct answers: B, C
Question 3
True or False: In a scaled Scrum environment with multiple teams working on a single product, it is a recommended practice for all teams to have the exact same Definition of Done (DoD).
Answer and explanation
Correct answer: A
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.
Question 4
During the 'Create Project Vision' process, the primary tool used to capture the desired business outcome and serve as a guide for the Scrum Team is the ______.
Answer and explanation
Correct answer: C
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.
Question 5
A new Scrum Team has been formed with members from different departments who have not worked together before. The Product Owner is struggling to get the team to provide reliable estimates during the 'Approve, Estimate, and Commit User Stories' process. What is the most likely reason for this challenge?
Answer and explanation
Correct answer: C
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.
Question 6
Case Study: HealthFirst Diagnostics
HealthFirst Diagnostics, a medical technology startup, is developing a new AI-powered platform to analyze patient test results. They have adopted Scrum for this high-stakes project. The project is currently in its fourth Sprint. The Product Owner, Dr. Evans, is a renowned medical expert but has limited experience with software development processes. The Scrum Team is highly skilled technically but is accustomed to traditional waterfall projects where requirements are fixed upfront.
The initial Sprints have been challenging. Dr. Evans frequently provides feedback directly to individual developers, leading to un-tracked work and deviations from the Sprint Goal. The Development Team, in turn, has been building features with extensive, 'gold-plated' engineering that far exceeds the immediate need defined in the User Stories, causing them to miss their Sprint commitments. The Scrum Master, Sarah, has observed that Sprint Reviews are becoming tense, as stakeholders are confused by the features delivered versus what was planned.
Question: As the Scrum Master, what is the most critical, immediate action Sarah should take to address the root causes of these issues?
Answer and explanation
Correct answer: C
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.
Question 7
The SBOK® Guide defines six Scrum Principles. Which principle underscores the idea that Scrum Teams are empowered to make local decisions and manage their own work to achieve the project's objectives?
Answer and explanation
Correct answer: C
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.
Question 8
A project is transitioning from a traditional management approach to Scrum. A manager asks the Scrum Master how risks are handled without a formal, upfront risk management plan and a dedicated Risk Manager. Which Scrum aspect and related practices should the Scrum Master highlight?
flowchart TD
A[Identify Risks] --> B{Assess & Prioritize}
B --> C[Develop Mitigation Plan]
C --> D[Implement & Monitor]
D --> A
subgraph Scrum Integration
E(Daily Standup) -.-> A
F(Backlog Grooming) -.-> A
G(Sprint Retrospective) -.-> A
end
Answer and explanation
Correct answer: C
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.
Question 9
Multiple answers
What are the primary outputs of the 'Demonstrate and Validate Sprint' process? (Select THREE)
Answer and explanation
Correct answers: A, C, E
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.
Question 10
A Product Owner wants to ensure a new feature is not only functionally correct but also meets specific performance benchmarks before it can be considered complete. Where should these performance benchmarks be documented?
Answer and explanation
Correct answer: B
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.
