A Scrum Master is working with a Development Team that has members in different physical locations. The Development Team meets in a variety of meeting rooms and has much to do logistically (for example, set up conference calls) before the Daily Scrum. What action should the Scrum Master take?
Correct Answer: A
According to the Scrum Guide 1 , only people who are actively working on items in the Sprint Backlog participate in updating it during a Sprint; this includes tracking progress made on those items. This is typically done by Developers updating their remaining work every day after their Daily Scrum. The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving their Sprint Goal. The Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. Therefore, the Scrum Master should allow the Development Team to self-manage and determine for itself what to do regarding the logistical challenges of meeting in different locations. References: Scrum Guide
Question 67
Several Sprints into a project, the Product Owner tells the Scrum Master that a key stakeholder just started using the product. The stakeholder is unhappy with the quality of the product, and the Product Owner agrees with the stakeholder's assessment that the quality is low. How should the Scrum Master respond to the Product Owner? (choose the best two answers)
Correct Answer: A,C
Several Sprints into a project, a key stakeholder begins using the product and finds the quality lacking. The Product Owner (PO) agrees and shares this concern with the Scrum Master (SM). The Scrum Master needs to determine the best way to respond. Scrum emphasizes empiricism , which is based on transparency, inspection, and adaptation . This means that if quality concerns arise, the Scrum Team must inspect the issue, adapt accordingly, and ensure quality is built into the product incrementally. # A. Encourage the Product Owner to include quality specifications in the Product Backlog and to communicate the stakeholders ' concerns to the Developers. # Reference from the Scrum Guide : * " The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. " * " The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. " # Why is this Correct? * Since the Product Owner represents the stakeholders , they should translate the stakeholder's concerns into actionable Product Backlog Items (PBIs) that reflect quality improvements. * Developers can refine and plan these PBIs in upcoming Sprints to ensure quality is systematically addressed. * The Product Backlog is the single source of work , meaning all quality requirements should be made explicit there. * This approach aligns with Scrum's empirical process of making work transparent so that the team can inspect and adapt. # C. Work with the Product Owner to understand their desired resolution and help formulate an approach for raising the concern with the Developers. # Reference from the Scrum Guide : * " The Scrum Master serves the Product Owner in several ways, including: Helping find techniques for effective Product Goal definition and Product Backlog management. " * " The Scrum Master serves the Scrum Team in several ways, including: Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done. " # Why is this Correct? * The Scrum Master is a servant leader , responsible for facilitating collaboration between the Product Owner and Developers so that the concern is effectively addressed. * Instead of dictating a solution, the Scrum Master guides discussions and enables the team to decide how best to improve quality. * The Definition of Done (DoD) should be reviewed to ensure it is clear, measurable, and includes quality standards . * This approach ensures that all stakeholders-Developers, Product Owner, and Scrum Master- collaborate in a self-managing way to improve quality. Incorrect Answers with Explanations # B. Bring the concern to the testers to improve how the Product is verified. # Reference from the Scrum Guide : * " Developers are always accountable for: Instilling quality by adhering to a Definition of Done. " # Why is this Incorrect? * Scrum does not have a separate testing team ; instead, the Developers are responsible for all aspects of quality (coding, testing, integration, etc.). * Quality should not be " verified " by an external group; rather, it must be built into the Increment from the start . * Instead of passing the issue to testers, the Scrum Team should improve their Definition of Done to ensure the product meets the necessary quality standards. # D. Tell the Product Owner they have noted the concern and will raise this issue at the Sprint Retrospective. # Reference from the Scrum Guide : * " The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. " # Why is this Incorrect? * While the Sprint Retrospective is useful for discussing improvements , waiting until the Retrospective delays the resolution of a critical issue. * The Scrum Team should act immediately by addressing quality issues in the Product Backlog and adapting their work in upcoming Sprints. * Transparency and fast feedback are key principles in Scrum- delaying discussions goes against empiricism . # E. Explain to the Product Owner that it is up to the Developers to decide on acceptable quality standards. # Reference from the Scrum Guide : * " The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. " * " If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. " # Why is this Incorrect? * While the Developers are responsible for meeting the Definition of Done , quality is a shared responsibility across the Scrum Team . * The Product Owner must ensure that the product delivers value to stakeholders , which includes meeting their quality expectations. * Ignoring the Product Owner's concerns contradicts Scrum's emphasis on collaboration and transparency.
Question 68
When might a Sprint be abnormally cancelled?
Correct Answer: B
According to the Scrum Guide1, a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Developers, or the Scrum Master. A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.
Question 69
(What is the Scrum Master responsible for during the Sprint Retrospective? Choose the best answer.)
Correct Answer: D
The correct answer is D because the Scrum Master participates in the Sprint Retrospective as a member of the Scrum Team and facilitates the event when needed. According to the Scrum Guide, the Sprint Retrospective exists so the Scrum Team can inspect how the last Sprint went regarding individuals, interactions, processes, tools, and their Definition of Done, and then identify improvements to increase quality and effectiveness. The Scrum Master helps ensure that Scrum events take place and are positive, productive, and kept within the timebox. That includes helping the team use the Retrospective effectively. Option A is incorrect because the Scrum Master is not merely a note-taker or scribe. Option B is incorrect because the Sprint Retrospective is for the Scrum Team, not a management reporting session. Option C is incorrect because action items are not "prioritized" by the Scrum Master alone; improvements are identified collaboratively by the Scrum Team. The Scrum Master's role is to support meaningful reflection, encourage openness, and help the team turn insights into practical improvements within the Scrum framework.
Question 70
When do Development Team members take ownership of a Sprint Backlog item?
Correct Answer: C
According to the Scrum Guide, the Sprint Backlog is the property of the Developers and no one else can tell them which items they should work on. The Developers can select any item from the Product Backlog that they forecast they can complete within a Sprint. The Developers are self- organizing and decide how to turn Product Backlog items into an Increment of value. Therefore, no one owns a Sprint Backlog item, but the entire Development Team is accountable for it.
