Question 21 - When is ownership of individual items, in the Sprint Backlog, assigned to Development Team members?

  • When the Scrum Master assigns it.

  • During Daily Scrum.

  • Any time during Sprint Planning.

  • Never. Even if individuals work on specific Sprint Backlog items, the Development Team as a whole remains accountable for the Sprint Backlog in its entirety.

Overall explanation

  • The Development Team is responsible for doing the work in the Sprint Backlog in order to satisfy the Sprint Goal.

Question 27 - What is included in the Sprint Backlog?

  • Use Cases
  • Tests
  • Any of the above (or others) which are a decomposition of the selected Product Backlog items
  • Tasks
  • User Stories

Overall explanation

  • The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.
  • The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.

Question 34: A Development Team decides to divide the Sprint Backlog and assign ownership of every Sprint Backlog items to each member of the team. The Scrum Master should:

  • Coach the team to collectively take ownership of the Sprint Backlog items

  • Encourage this practice as it increases individual accountability

  • Encourage this practice as it increases productivity

Overall explanation

  • The Sprint Backlog is collectively owned by the Development Team.

Question 48 - When does the Development Team create the Sprint Backlog?

  • Along with the creation of the Product Backlog

  • During the Sprint Planning

  • During the review with stakeholders

  • After the Product Backlog Refinement

Overall explanation

  • The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.

Question 59 - A Development Team selects a set of Product Backlog items for a Sprint Backlog with the intent to get the selected Items "Done" by the end of the Sprint. Which three phrases best describes the purpose of a definition of "Done"?

Choose 3 answers

  • It controls whether the developers have performed their tasks

  • It defines what it takes for an increment to be ready for release

  • It guides the Development Team in creating a forecast at the Sprint Planning

  • It tracks the percent completeness of a Product Backlog Item

  • It provides a template for elements that need to be included in the technical documentation

  • It creates transparency over the work inspected at the Sprint Review

Question 79 - During a Sprint, when is new work or further decomposition of work added to the Sprint Backlog?

  • When the Product Owner identifies new work

  • When the Scrum Master has time to enter them

  • During the Daily Scrum after the Development Team approves them

  • As soon as possible after they are identified

Overall explanation

  • The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.
  • This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.

Question 117 - When do Development Team members take ownership of a Sprint Backlog item?

  • Never. All Sprint Backlog Items are "owned" by the entire Development Team, even though each one may be done by an individual development Team member

  • At the Sprint Planning meeting

  • During the Daily Scrum

  • Whenever a team member can accommodate more work

Overall explanation

  • Development Teams have the following characteristics:

    • They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;

    • Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment;

    • Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;

    • Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis; and,

    • Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.