The government Product Owner is responsible for designating a story as ‘Complete’ based on
acceptance criteria1. The Product Owner is the primary representative of the customer and
stakeholder needs, and has the authority to accept or reject the work done by the team2. The
Product Owner reviews the acceptance criteria for each user story and verifies that they are met by
the working software. The Product Owner also ensures that the work meets the definition of done,
which is a shared understanding of the quality standards for the team3.
1: Government - Building in Quality and Compliance - Scaled Agile Framework 2: Product Owner -
Scaled Agile Framework 3: When is a User Story “Done?”— Acceptance Criteria and the Definition of
“Done” [Article] | Treehouse Blog