Own the Team Backlog - accountable for stories, enablers and defects in Team Backlog to be ‘ready’ for planning sessions and refinement meetings - including coordination of content dependencies with other Product Owners, prioritized user stories with well-defined acceptance criteria, accepts or rejects work results per iteration.
Team Backlog prioritization considers scope vs. cost vs. schedule decisions.
Attends scrum meetings, planning sessions, retrospectives (as invited by team), and facilitates demos.
Continuously communicates and executes the Product Management vision, goals and roadmap to the development teams, customers and stakeholders.
Owns the delivery plan and progress to the plan (Feature Complete and Iteration Objectives) to the Product Manager.
Work with Product Management to understand strategic objectives, budget, epics, and Features.
Understands enabler work and other technical needs and can effectively prioritize against new feature work and negotiate with architects to determine capacity proportions.
May write and track vendor contracts, ensure that vendor deliverables and milestones are clear - track their progress towards feature completion and adjust the team backlog accordingly.
At scale - heavily involved in PI Planning and System Demo.
Helps remove roadblocks the team cannot resolve on their own.
The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner.