When is a Product Backlog item considered complete?

A Product Backlog item is considered complete when all work in the Sprint Backlog related to the item is finished. This aligns with the principles of Scrum, which emphasize that the team must complete all the tasks necessary to meet the definition of “Done” for that item.

In Scrum, the Definition of Done is a shared understanding among the team and stakeholders of what “complete” means for work items. This typically involves not just programming or development work but also necessary tasks such as testing, documentation, and integration.

When all work associated with the item in the Sprint Backlog is completed according to the agreed-upon Definition of Done, then the item is truly considered done. This ensures that the work item provides value as intended and can be potentially released or delivered if necessary.

Other options reflect different aspects of the development process but do not fully encapsulate when a Product Backlog item is considered complete. For example, verification by the Product Owner or demonstrating to stakeholders may indicate that work is nearing completion but does not necessarily mean all the necessary work has been performed. Additionally, the decision of the team alone does not ensure that the completion criteria have been met without objective measures or agreed-upon definitions.