At the end of a Sprint Product Backlog item worked on during the Sprint does not meet the definition of “Done”. What two things should happen with the undone Product Backlog item? (Choose two.)
A.
If the stakeholders agree, the Product Owner can accept it and release it to the users.
B.
Put it on the Product Backlog for the Product Owner to decide what to do with it.
C.
Review the item, add the “Done” part of the estimate to the velocity and create a Story for the remaining work.
D.
Do not include the item in the Increment this Sprint.
According to the Scrum Guide1, the definition of “Done” is a formal description of the state of the Increment when it meets the quality measures required for the product. The definition guides the Development Team in creating a “Done” Increment. The definition of “Done” is created by the development organization (or Development Team if none is available from the development organization). The definition of “Done” may vary significantly per Scrum Team, depending on the context. One aspect of Scrum Teams inspecting how they work toward their Product Goal is that they improve their definition of “Done” over time. Therefore, if a Product Backlog item worked on during the Sprint does not meet the definition of “Done”, two things that should happen with the undone Product Backlog item are:
Put it on the Product Backlog for the Product Owner to decide what to do with it, as they are accountable for effective Product Backlog management and ordering.
Do not include the item in the Increment this Sprint, as it does not meet the quality standards and may compromise value.
The other options are not appropriate, as they may compromise transparency, inspection, or adaptation.
References: Scrum Guide
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit