Team, I am your Product Owner
Product
Owner
· Manage the stakeholders requirements
· Represents the users of the system
· Communicates the vision to the Scrum team
· Sets the goal of each Sprint
Vision
· Owns & maintains the Product Backlog
· Understands and articulates to the team the
requirements in user stories
· Makes key decisions & prioritizes work for the
team
· Sets the acceptance criteria for each story
Scope
· Attends the daily standup to LISTEN
· Provides guidance and clarification when sought
· Ensures the Product backlog is maintained and
current
· Provides authoritative knowledge on the system
being developed
Facilitate
· Promote continuous improvement methods
· Commit to continued self learning of Agile
· Coach and mentor stakeholders on Scrum
practices
· Yokoten (share across the organization your
improved processes)
· Promote standardized repeatable processes
· Observe, listen, evaluate and provide feedback
Improve
· Shields the team from users, stakeholders, and
requirements engineering
· Shields the team from business influences that
impact scope and delivery
Protect· Establishes the release plan goals
· Maintains the scope for each release
· Approves the release
· Communicates new functionality of changes to
stakeholders
Releases
Prepared by: Nigel Thurlow
Last Updated: April 10th
2015
Version: 3

The Product Owner Role

  • 1.
    Team, I amyour Product Owner Product Owner · Manage the stakeholders requirements · Represents the users of the system · Communicates the vision to the Scrum team · Sets the goal of each Sprint Vision · Owns & maintains the Product Backlog · Understands and articulates to the team the requirements in user stories · Makes key decisions & prioritizes work for the team · Sets the acceptance criteria for each story Scope · Attends the daily standup to LISTEN · Provides guidance and clarification when sought · Ensures the Product backlog is maintained and current · Provides authoritative knowledge on the system being developed Facilitate · Promote continuous improvement methods · Commit to continued self learning of Agile · Coach and mentor stakeholders on Scrum practices · Yokoten (share across the organization your improved processes) · Promote standardized repeatable processes · Observe, listen, evaluate and provide feedback Improve · Shields the team from users, stakeholders, and requirements engineering · Shields the team from business influences that impact scope and delivery Protect· Establishes the release plan goals · Maintains the scope for each release · Approves the release · Communicates new functionality of changes to stakeholders Releases Prepared by: Nigel Thurlow Last Updated: April 10th 2015 Version: 3