16
Being an Effective Product Owner Being an Effective Product Owner Roman Pichler
Being an EffectiveProduct Owner
Being an EffectiveProduct Owner
Roman Pichler
© 2007 Pichler Consulting Ltd 2
The Many Views of a ProductThe Many Views of a Product1 2 3
4 5 6
How the customer described it
1
How the project manager understood it
2
How the programmer wrote it
4
How the architect designed it
3
What operations installed
5
What the customer really needed
6
© 2007 Pichler Consulting Ltd 3
The Product OwnerThe Product Owner• Traditionally, the Product Owner is used to
– Describe requirements completely and precisely upfront and then to
– “Throw the requirements over the wall” and hold development responsible for meeting needs
• Scrum put this responsibility back on the Product Owner; requirements are now detailed just in time
© 2007 Pichler Consulting Ltd 4
Scrum FlowScrum Flow
Max. 30Days
Sprint
Create documentation
for remote service
components
Create design forremote service
componentsExecute tests forremote service components
Sprint Backlog ShippableProduct Increment
Daily Scrum
1Teste, dass die Änderun-gen persistiert wurden.
Als Basis-anwender möchte ich eine Besprech-ung ändern
Calendar3
3Teste, dass dieselbe Besprechung nicht zweimal gelöscht werden kann.
Als Basis-anwender möchte ich eine Besprech-ung stornieren
Calendar2
2Teste das Eingeben ungültiger Werte, z.B. Endzeit liegt vor Startzeit.
Als Basis-anwender möchte ich eine Besprech-ung anlegen
Calendar1
EffortCOSItemThemePrio
Product Backlog
© 2007 Pichler Consulting Ltd 5
Product Owner ResponsibilitiesProduct Owner Responsibilities• Voice of the customer• Defines customer
value-added and the key features of the product
• Describes, priorities and refines requirements continuously
© 2007 Pichler Consulting Ltd 6
Product Owner ResponsibilitiesProduct Owner Responsibilities• Responsible for the
project success and ROI
• Decides on release date, content and budget
• Creates and updates the release plan and reports
• Manages stakeholders and interests proactively
© 2007 Pichler Consulting Ltd 7
Product Owner ResponsibilitiesProduct Owner Responsibilities• Selects the sprint
goal, steers and guides the work, answers questions on a daily basis
• Attends all Scrum meetings
• Accepts or rejects work results in the sprint review meeting
© 2007 Pichler Consulting Ltd 8
Desirable Product Owner Characteristics
Desirable Product Owner Characteristics
• Understands customer needs thoroughly• Able to create and communicate the
product vision• Empowered to make decisions, is decisive
and knows when to say no• Has good working relationships with the
stakeholders• Understands value creation• Leader and facilitator
© 2007 Pichler Consulting Ltd 9
A Day in the Life of the Product OwnerA Day in the Life of the Product Owner
Catch up with emails, then leave the office early to recover from a busy and intensive day
17:00 – 17:30
Run the estimation workshop and facilitate planning poker15:00 – 17:00
Prepare upcoming sprint planning meeting; flesh out conditions of satisfaction for new user stories
13:00 – 15:00
Lunch with Sarah, the portfolio manager, to discuss product roadmap and upcoming releases
12:00 – 13:00
Meet with stakeholders and discuss product backlog modifications and priorities
11:00 – 12:00
Sit with the team and answer questions10:15 – 11:00
Attend the Daily Scrum10:00 – 10:15
Work through new requirements and add them to the product backlog
09:00 – 10:00
ActivityTime
© 2007 Pichler Consulting Ltd 10
The Two PerspectivesThe Two Perspectives
Outward lookingVoice of the customer
Inward lookingValue stream manager
© 2007 Pichler Consulting Ltd 11
Common Product Owner PitfallsCommon Product Owner Pitfalls• Not empowered
– Lack of guidance, direction and decision making
• Poor availability– Collaboration with the team suffers; lack of direction and
decision delayed– Poor prep work for the next sprint
• Poorly trained– Lack of Scrum knowledge and useful techniques such as
user stories
There is a strong correlation between a Product Owner who is trained, available and empowered
and a successful Scrum project
© 2007 Pichler Consulting Ltd 12
The Lean Product OwnerThe Lean Product Owner• Lean companies like Toyota have used a
Product Owner role successfully for decades
• Toyota’s Product Owner is called the Chief Engineer
• The Chief Engineer plays a key role in Toyota’s product development system
• The Chief Engineer is appointed by and reports to senior management
© 2007 Pichler Consulting Ltd 13
The Lean Product OwnerThe Lean Product Owner• The Chief Engineer combines the following
traditional roles in one person– Product manager– Project manager– Chief architect
• The Chief Engineer is an outstanding, highly regarded senior engineer
© 2007 Pichler Consulting Ltd 14
The New Value StreamThe New Value Stream
ProductManagement Development QA/Test
Traditional Processes
Scrum
PortfolioManagement
The Product Owner manages the value stream from concept to cash!
© 2007 Pichler Consulting Ltd 15
The EndThe End
© 2007 Pichler Consulting Ltd 16
Contact InformationContact Information
Roman PichlerConsultant, Certified Scrum TrainerTel.: +44 7974 203772Email: [email protected]
Upcoming Certified Scrum Product Owner courses:• 22-23 Nov 2007, London, UK• 06-07 Dec 2007, Munich, Germany
![Alois Pichler March 28, 2013 arXiv:1303.6675v1 … · arXiv:1303.6675v1 [math.FA] 26 Mar 2013 The Natural Banach Space for Version Independent Risk Measures Alois Pichler ∗ March](https://static.documents.pub/doc/80x56/5b5f06667f8b9a415d8d8a17/alois-pichler-march-28-2013-arxiv13036675v1-arxiv13036675v1-mathfa-26.jpg)
