It seems quite well understood who a ScrumMaster is, who a developer or tester is but what about the Product Owner. People often seem to fall into this role without a full understanding of what it's all about.
I frequently find myself wondering what the perfect Product Owner would look like. Where do they come from, what qualities and experience do they have and why are they so hard to find! What makes a good product owner and try and where can we find or how can we create this rare creature.
3. http://www.meetup.com/Agile-North-East/
ScrumMaster
The Mythical Product Owner
What do they do? Servant Leader, Understands
the Scrum process, Unblocks the blockers. Helps
the team to realise the benefit of working in an
Agile fashion.
Where do they come from? Often comes from a
TL, might still be a member of the team. Can
eventually be rotated through the
Development Team.
4. http://www.meetup.com/Agile-North-East/
Development Team Member
The Mythical Product Owner
What do they do? Developer, Analyst, Tester, UX
Designer, Cheese monger, etc. Should really be
cross functional but in reality people with a
diverse set of skills to deliver software.
Where do they come from? Wherever they
come from.
5. http://www.meetup.com/Agile-North-East/
Product Owner
The Mythical Product Owner
What do they do? The one with the vision, the
person responsible for the product. Not the
boss, not the slave driver with the whip but
seeking the most value in the shortest time.
Where do they come from? Often come from
the sales channel, sometimes business analysts,
sometimes project managers. Sometimes a
very senior manager.
6. http://www.meetup.com/Agile-North-East/
What’s up with our POs?
The Mythical Product Owner
• Often a neglected role. An afterthought to the
agile process and someone is offered up to
provide some guidance part time.
• Training is not common, proper commitment
to the role is not common.
300,000
CSM
50,000
CSPO
vs
7. http://www.meetup.com/Agile-North-East/
Where have they come from?
The Mythical Product Owner
• Often still seen as a traditional boss. "This
must get done by X".
• Role doesn't really exist in a waterfall world.
• There are instead huge long documents that
may be briefly reviewed by senior
stakeholders. We're turning that document
into a person.... It's a new role.
9. http://www.meetup.com/Agile-North-East/
Product Owner Personas
The Mythical Product Owner
• Name your product owner
• A paragraph about their back story
• Three positive attributes that help them to be
a good Product Owner
• Three negative attributes that make them a
bad Product Owner
11. http://www.meetup.com/Agile-North-East/
Let’s build one
The Mythical Product Owner
• All knowing about the product, the market
and the users.
• All powerful when it comes to decisions and
the clout to follow through.
• Committed and available to the team at all
times.
• Respects the process and the team.
12. http://www.meetup.com/Agile-North-East/
How do we make do?
The Mythical Product Owner
• Get the time and the commitment. Product
owner isn't a small job. They are the conduit
for everything the team is asked to deliver.
Such an important role.
• Gain the respect by getting someone bought
into the benefits of the process.
• Understanding how to identify value
• Find a good negotiator.
13. • The Product Owner is part of the
team(!) Include them however
possible.
• If they don't have the product knowledge
spending time with the users is key. Users and
stakeholders can be won over with rapid
progress.
The Mythical Product Owner http://www.meetup.com/Agile-North-East/
Grow the Product Owner
14. Grow the Product Owner
• Get executive sponsorship by proving
the process.
• Demonstrate the value delivered
each Sprint.
The Mythical Product Owner http://www.meetup.com/Agile-North-East/
• Show the agility and ability to change
direction.
• Above all else ScrumMaster has to support
the Product Owner.
Three key roles of Scrum.
I’ve always been comfortable with ScrumMaster and Developer as they have been my background. The Product Owner has always been a bit ellusive.
Business knowledge?
The MD?
Standups, working on stories, having ‘the conversation’ about each story to elicit and agree requirements. Answering questions during work on the backlog to allow estimation.
Has a different agenda to the team (realisation of most value) but understands they cannot tell the team what to do. The team agrees and accepts work. Solid understanding of the development process and a trust that what they’re being told is correct.
TIME: I've heard 50% for a well oiled machine / mature team. Expect more initially.
BUY IN: Training? Shadowing others? Seeing success?
VALUE: They don’t need to know everything. They need to be able to work out when something is valuable though. From the point of view of the end users, collaboration is key. User research skills?
NEGOTIATOR: Proxy can work. They hide the pain from the team.
Controversial! Bear in mind the PO can have a conflict of interest with the team but the overal agenda for everyone is the same. Retrospectives are a big deal. They’re not about blame but including the PO helps them understand the issues and often how they can be part of them.
Helps them to understand the development process too.
Way to build the clout earn the trust that is needed. Scrum in a bubble is possible, consultancy gaining trust with clients is key.
Agility: Can always say 'Yes' to being asked to do anything and quickly show the cost.
Every good Product Owner needs a good ScrumMaster to ensure that the team can be as productive as they want and need to be.