PO is dead,
long live the PO
Mauro Servienti - @mauroservienti
dispersed
across 17 time zones
A long time ago…
no hierarchy
but we’re not flat
no budgets
it’ll be a number out of the blue
no estimates
make no sense
no deadlines
we’re quality driven
fail small
learn big
OSS
framework
diverse and distant
customers base
Move fast and
break things
Seems to be the obvious choice
The larger the backlog, the nicer the graveyard.
Prioritization is a nightmare
To provide the
best developer
experience we can
To let customers
take care of
their business
To react to a
shifting marketplace
To keep
the lights on
purpose
purpose
tool
purpose
tool
backlog
we can
compare
things
singletons
are problematic
squads
process
triage
is it a problem?
“why bucket”
- assigned -
prioritization
“chop” the problem
task force
recruitment
announcement
task force
• Diverse skillset
• Different time zones
• Facilitator
• Reviewer(s)
• Report to the squad
RFC
is the problem
addressed?
Tackle next chunk…
retrospective
whole
organization
has to be
agile
agile
was not our
goal
Mauro Servienti
Solution Architect @ Particular Software
mauro.servienti@gmail.com
@mauroservienti
//milestone.topics.it
Po is dead, long live the po

Po is dead, long live the po

Editor's Notes

  • #11 Near to zero feedback If we have feedback it’s “apples and oranges” Both are valid, from different contexts
  • #12 Customers are far away Little feedback Long term support
  • #13 We have to carefully select what to work on next
  • #14 Making a decision is very hard
  • #16 No way the PO can make a decision
  • #17 Back to the drawing board
  • #18 Why do we do what we do? What’s the purpose?
  • #23 Ktlo -> patch criteria/severity DX -> usuability eurisitcs/personas BV -> system categories, platform map Shift -> tech radar
  • #24 Ktlo -> patch criteria/severity DX -> usuability eurisitcs/personas BV -> system categories, platform map Shift -> tech radar
  • #25 Ktlo -> patch criteria/severity DX -> usuability eurisitcs/personas BV -> system categories, platform map Shift -> tech radar
  • #26 We can segment who is impacted We can predict the impact Is this enough?
  • #27 Lack of skills Responsibilities No debate
  • #28 Squad per Why: 4/5 people Diverse skillset A mix between a PO/Scrum Master Long living body First come first served
  • #39 Nothing is left over