When is a Product Backlog item considered complete?
A)When all work in the Sprint Backlog that is related to it is complete
B)At the end of the Sprint
C)When QA reports that it passes all acceptance criteria
The correct answer and explanation is:
Correct Answer: A) When all work in the Sprint Backlog that is related to it is complete.
Explanation:
In Scrum, a Product Backlog item is considered complete when it meets the Definition of Done (DoD) that has been agreed upon by the Scrum Team. The Definition of Done is a shared understanding within the team of what completeness means, and it ensures quality, consistency, and transparency across all work items. Let’s break this down:
- Related to the Sprint Backlog: When a Product Backlog item is included in a Sprint, it is broken down into tasks and becomes part of the Sprint Backlog. The team then works on these tasks during the Sprint. Completion of the item is directly tied to the completion of all tasks and criteria associated with it. If some work remains unfinished, the item cannot be considered complete.
- Definition of Done (DoD):
Completion is not subjective; the item must meet all criteria defined in the DoD. These criteria may include coding, testing, documentation, and review to ensure the item is potentially shippable. Without meeting these criteria, the item remains incomplete. - QA and Acceptance Criteria:
While QA testing and passing acceptance criteria are part of completion, they alone do not define it. If other elements of the DoD (e.g., code reviews or deployment readiness) are not met, the item is not done, even if QA passes it. - End of the Sprint:
Completion of a Product Backlog item does not depend on the Sprint ending. It can be marked complete anytime during the Sprint, as long as all DoD criteria are met.
Thus, the correct answer is A, as it encompasses the broader context of Scrum principles, emphasizing that completion is tied to all related work being finished per the Definition of Done.