EVERYTHING WE AS PRODUCT OWNERS DO DRIVES THE DIRECTION OF THE PRODUCTS WE CREATE AND INSPIRES THE TEAM TO WORK ON A TRANSCENDENTAL GOAL. WE DO THAT BY ACTING AS AN INCREDIBLY AWESOME TEAM THAT WORKS ACROSS FUNCTIONS, LISTENING TO OUR CUSTOMERS AND EACH OTHER. WANNA BE A REALLY AWESOME PRODUCT OWNER TEAM? THIS SESSION WILL EXPLAIN THE NEED FOR PRODUCT OWNERS TO WORK TOGETHER AS A COLLABORATIVE TEAM, VISITING CUSTOMERS, LEARNING FROM THE MARKET, DEVELOPING NEW BACKLOG AND BECOMING MORE CROSS FUNCTIONAL IN ORDER TO DELIVER REALLY IMPACTFUL SOLUTIONS TO OUR CUSTOMERS.
9. Examples
• Waze
• Spotify
Driving
• Order Management
• Supply Chain
• Finance
Enterprise
Resource Planning
• Technical documents
• e-commerce
• Inquiries
Customer Support
Site
10
10. What is a
team?
Work
together to
remove
impediments
Grow each other
through technical
excellence
Breadth of
Knowledge
EXPERTISE
Two or more people
who come together to
achieve a common
goal
What characteristics do we
look for in teams?
13. 15
• Peyton Manning- OMAHA
• Time to make a decision is the primary driver of
project failure and budget overrun
• Scrum pushes decisions down to the team and
small teams reduce “decision latency”
• Strong, decisive, available Product Owner is critical
to short decision latency
Why the Standish Group thinks Scrum Works
Decision latency is directly related to Process Efficiency!
14. Team of PO
responsibilities
• Create an inspirational vision for
products & make it visible to the
organization
• Generate a single prioritized backlog
of products
• Consider dependencies raised by the
teams to prevent impediments at the
team level
• Decide upon and monitor metrics
that give insight into the products
16
15. Scaled Backlog Refinement and Review
C
CPO
SH
Stakeholders
PO
Product
Owners
C
SH
Sprint/Time
C
Aligned
Product
Backlog
C
SH
SH
SH SH
PO PO PO
Vision
Validated
Learning
Validated
Learning
17
Aligned
Product
Backlog
Aligned
Product
Backlog
16. 19
PO Team
Executive Leadership
PO (Head PO)
SM
Team – PO from SoS,
other people as needed
Vision – WHY
Servant Leadership
Review + Sprint
Planning
Team of Teams
PO (CPO)
SM
Team – PO from teams,
other people as needed
Items to create the
backlog
Roadmap
Scaled Events: Planning,
Daily, Refinement,
Review, Retro
Teams
Cross Functional
Do the work
Sprints
Validated Learning
3-5-3
Product
Focus
Organization
Focus
Customer Field Trips
Regulation
Getting Sales
Time with teams
Leadership accountability
Create/Kill products
Change management
Provide Incremental
Funding
17. •Create and Kill products
•Aligns enterprise around single
backlog
•Restructure network of teams
20
MetaScrum - Event
• Who: Key Stakeholders, Leadership, Product Owners, and Team members.
• Run by Chief Product Owner
• Topics:
See the Scrum plop pattern
•Did anything change that would
change the strategy or
priorities?
•Incremental funding
18. MetaScrum- See ScrumPlop Pattern
Case Study by Kim Antelo
21
Quality
Test
PLM
Diag
Fin
Model
PLM
• Build Knowledge across silos
• What did we learn that would impact our priorities?
• Understand interdependencies and re-use
opportunities
• Each product deep dives at least every 90 days
• Build network of teams to address a “mission”
• Meet every week for 2-4 hours
• How are we going to address the next most important
thing?
PLM
19. Bring all of the superpowers of your
product owners together to solve
bigger problems better
22
20. Food and Fun Festival
Product – Brochure and Map of Festival
• Includes Cover Page
• Includes 6-20 station descriptions
Definition of Done
• Meets Acceptance Criteria.
• Includes Cover Page
• Common copyright and logo, bottom left of page (Legal)
• Adjacent pages may not be of the same color (UX)
23
21. Wrap
• PO Teams have
superpowers
• Perspectives
• Functional/domain
knowledge
• Solving the right
problems
• Constantly learning
and sharing
24