Product Owner

Maintaining the team backlog - Working with other stakeholders and other members of the organization, the PO has the primary responsibility for building, editing, and maintaining the team backlog.

Iteration Planning - The PO reviews and reprioritizes the backlog as part of the prep work for Iteration Planning, including coordination of dependencies with other POs. During the iteration planning meeting, the PO is the primary source for story detail and priorities and has the responsibility of accepting the final iteration plan.

Supporting Acceptance Test-Driven Development (ATDD) - POs participate in the development of story acceptance criteria, draft them when feasible, and provide examples in support of ATDD specification by example.

Accepting stories - The PO is the only team member who can accept stories as done. This includes validation that the story meets acceptance criteria and has the appropriate, persistent acceptance tests, and that it otherwise complies its Definition of Done (DoD). In so doing, the PO also assures a level of quality, focusing primarily on fitness for use.

Understand enabler work - While POs are not expected to drive technological decisions, they are supposed to understand the scope of the upcoming enabler work and to collaborate with System and Solution Architect/Engineering to assist with decision-making and sequencing of the critical technological infrastructures that will host the new business functionality. This can often be best accomplished by establishing a capacity allocation, as described in the team backlog article.

Participate in team demo and retrospective - As the person responsible for requirements, POs have an essential role in the team demo, reviewing and accepting stories. They also participate in the Iteration Retrospective, where the teams gather to improve their processes and are active in the Agile Release Train's (ART's) Inspect and Adapt (I&A) workshop.

POs also participate in the preparation of the PI system demo. PO Sync Meetings