Scrum Updated PSPO-I Exam Questions and Answers by chaim

The Sprint Backlog is created during Sprint Planning, where the Developers select the Product Backlog items that they can deliver in the Sprint and create a plan for how to do the work. The Scrum Guide states that " The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how). " 1 The Sprint Backlog is owned and managed by the Developers, who can update it throughout the Sprint as more is learned.

1: The Scrum Guide2, page 15

2: The Scrum Guide

The Scrum Guide states that " Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. " 1 This means that there is no gap or break between Sprints, and the Scrum Team does not need to spend extra time to prepare for the next Sprint. The Scrum Team should be able to start the next Sprint Planning right after the Sprint Review and Sprint Retrospective of the previous Sprint. The Scrum Team should also ensure that the testing and documentation of the work are done within the Sprint, and not left for later.

1: The Scrum Guide2, page 9

2: The Scrum Guide

 An Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.1 An Increment is a concrete, tangible, and usable outcome of the work done by the Developers in a Sprint. It is not a plan, a mock-up, a design, or a roll-out plan, as these are not valuable or useful products in themselves. An Increment must meet the definition of “Done”, which means it must adhere tothe quality standards agreed upon by the Scrum Team and the stakeholders.1 An Increment must also be potentially releasable, which means it must be in a state that it could be delivered to the customer or user if the Product Owner decides so.1

1: The Scrum Guide2, page 14

2: The Scrum Guide

If a stakeholder is unhappy with the quality of the product, the Scrum Master can coach the Product Owner on how to effectively communicate this concern to the Developers1.The Scrum Master can also encourage the Product Owner to put quality specifications on the Product Backlog1.This allows the Developers to understand the stakeholder’s expectations and work towards meeting them1.The Developers are responsible for building quality into the product, but the stakeholders (through the Product Owner) are responsible for setting what is expected in terms of product and process quality1.