The product owner is responsible for maintaining the product vision, prioritizing the backlog, accepting or rejecting work in sprint reviews, and being accountable for the project's success. They represent stakeholders and have deep product knowledge. The product owner is also responsible for continuous backlog refinement, defining features and success criteria, deciding on release scope and schedule, and being available to provide guidance to the development team.
2. agile
Aware and committed to the four agile values:
1. People over processes and tools
2. Working software over documentation
3. Collaboration over negotiation
4. Responding to change over planning
4. mandated
Aligned with the sponsor on
expectations and by
this, mandated to take
big, fast, brave decisions
within given boundaries.
Single point of contact for
the product (including new
requirements prioritizing
backlog items).
Accepts and rejects work in
the sprint reviews.
5. a true visionary
Maintaining the vision for the
product and keeps it aligned
with the company vision.
Focus on WHY we are doing
this.
Example:
xxxs vision is to be earths
most customer centric
company; to build a place
where people can come to find
and discover anything they
might want to buy online.
6. a true visionary (cont.)
Purpose:
Vision: World Peace
Objective 1: Balance welfare
Objective 2: Get religions to co-exist.
Objective 3: Exterminate terrorism
Mission 1: Set up posters on terrorists
Mission 2: Get Bin Ladin
損 My assignment: I will look out from the hill while the
team storm the Bin Ladin house.
7. present
Always (101%) available for the team for their
questions and product guidance.
If not 101% then two Pos sharing 75% + 75% is
equal.
8. signing off
Accepts and rejects work in the sprint reviews.
Makes sure tests are done according to QA
plan.
Does not allow defects or bad usability to
impact the customer.
9. value focused
Keeps a focus on speedy and continuous
delivery of business value.
10. showing the way
Decides on release date, scope and
budget.
Sets delivery schedule by
managing the backlog creates
and updates the release plan.
Planning
Low level (week): Team responsible
Mid level (month): PO+team
responsible
High level (project): PO+Sponsor
responsible
11. a business expert
Voice of the Stakeholders, represents the
business and have deep product knowledge.
12. eating the shit
Accountable for the
project success (together
with the team) and eats
the shit afterwards.
<> being present.
Is passionate about the
product.
Consultant
13. groomer of the backlog
Continuously refines and
prioritizes requirements.
Defines key features of the
product and success criteria.
Aware of how risks affect
prioritization.
Comfortable with Minimum
Viable Product
Use a tool for the purpose
(Excel, Jira, Rally etc).
15. working In WITH the team
Does not disturb a team under
commitment and if so - understand
the effects by doing this.
Does not belong to the team but are
their best friend.
Understand the need for refactoring,
retrospectives, NFR, planning and
other "non-value creating stuff".
Takes advice from the team on
backlog dependencies and the HOW
of doing things.
16. The PO cycle
Iteration 1 (2-4 weeks)
Morning standups and continuous presence
Plan it 1
with the
team
Backlog grooming
Preplanning &
Spike
Review
Accept.
Test previous
delivery
Stakeholder meetings
Retrospective
Goal for iteration 2 set
Wireframes
accepted for
Iteration 3
Goal for
Iteration 3
Sponsor
update