What It Takes To Be a Product Owner - Pratap Kumble - Scrum Bangalore 19th Meetup
What it takes to be a
P R A T A P K U M B L E – P R O D U C T O W N E R @ P R O W A R E N E S S
Who or what is a Product Owner
The scrum guide says “The Product Owner is responsible for
maximizing the value of the product and the work of the
Mike Cohn defines “The Scrum product owner is typically a
project's key stakeholder. Part of the product owner
responsibilities is to have a vision of what he or she wishes to
build, and convey that vision to the scrum team.”
Ability to Execute
• Identifying and finding the right signals & opportunities
• Market research
• Are we solving the right problem.
• Asking the right questions and understand the “Why” behind the need.
• Should we build the right thing, build the thing right, build it fast.
• Say no to everything that is not critical or which does not add value
• Interact and engage with different teams and with Stakeholders.
• Understand their needs.
Negotiation – Product owners influence/lead without authority.
Anti Patterns – Types of POs
The no power/half PO/Proxy PO - Let me ask my boss
Too busy PO - Come back Later or tomorrow
Far Away PO
PO by committee
What a great product owner should have
Empowered – Can make decisions on their own
Knowledge – Know the Domain
Time – Time for the users/customers, dev teams, other teams
Tips on becoming a better product
Resonate your product vision
Understand your strengths and weaknesses. Develop your weaker
Earn the authority
Use the right tools to get the job done
Help your stakeholders and teams to achieve a common agreement on
what is valuable