Scrum Team Accountabilities Flashcards
7 cards from real Professional Scrum Master practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Scrum Team Accountabilities flashcards as text
A company has two Scrum Teams working on the same product. How should they handle the Product Backlog?
Answer: There is one Product Backlog for the product, managed by one Product Owner
A single product has one Product Backlog and one Product Owner, regardless of how many Scrum Teams work on it.
Which scenario BEST demonstrates a Scrum Master acting as a 'servant leader'?
Answer: Removing an organizational impediment after the team identified it at the Retrospective
Servant leadership in Scrum means enabling the team's success — removing impediments they surface is a prime example.
Developers say they need specialized knowledge that no team member currently has. What is the CORRECT Scrum approach?
Answer: The Developers identify the gap; the team adapts by learning or collaborating with specialists
Scrum Teams are accountable for being cross-functional; they must proactively address skill gaps through learning, coaching, or temporary collaboration.
What is the Scrum Team's accountability regarding the Sprint Backlog?
Answer: Developers own the Sprint Backlog and update it throughout the Sprint
The Sprint Backlog is owned by Developers, who update it throughout the Sprint to reflect their current plan for achieving the Sprint Goal.
How should a Scrum Team handle work that emerges during a Sprint that was not anticipated in Sprint Planning?
Answer: Developers negotiate with the Product Owner and may add it to the Sprint Backlog if aligned with the Sprint Goal
Developers collaborate with the Product Owner to incorporate unplanned work into the Sprint Backlog when it aligns with and supports the Sprint Goal.
A Product Owner tries to dictate the technical approach Developers should use. What should the Scrum Master do?
Answer: Coach the Product Owner to respect Developers' autonomy over technical decisions
Developers are accountable for technical decisions; the Scrum Master should help the Product Owner understand the boundaries of each accountability.
At the end of a Sprint, Developers complete work but it does not meet the Definition of Done. What happens to this work?
Answer: It is not included in the Increment and returns to the Product Backlog
Work that does not meet the Definition of Done cannot be included in the Increment and must be returned to the Product Backlog for future consideration.