Po is dead, long live the po
Cosa succederebbe se i prodotti non fossero gestiti dai manager? O addirittura, cosa se i manager non ci fossero proprio? Chi si prenderebbe la responsabilità di definire la priorità nel backlog? In Particular Software non c’è una struttura gerarchica. La gestione dei prodotti, intesa come vera e propria product ownership, è responsabilità di tutti. Sembra quasi che gli internati siano anche i gestori del manicomio. Non è proprio distante dalla realtà. Oggigiorno sempre più aziende si stanno orientando verso strutture organizzative fluide. Che cosa si può fare per abilitare chiunque a prendere decisioni a qualsiasi livello? C’è un modo per condividere il processo decisionale? Guarderemo come è strutturata Particular Software al fine di abilitare tutto ciò. Analizzeremo come vengono risolti i problemi e quali processi e strumenti utilizziamo per prendere decisioni. Tutto senza infermieri, ooops, senza manager.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie Po is dead, long live the po
Ähnlich wie Po is dead, long live the po (20)
Mehr von Mauro Servienti
Mehr von Mauro Servienti (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Po is dead, long live the po
- 1. PO is dead, long live the PO Mauro Servienti - @mauroservienti
- 2. dispersed across 17 time zones
- 3. A long time ago…
- 4. no hierarchy but we’re not flat
- 5. no budgets it’ll be a number out of the blue
- 6. no estimates make no sense
- 7. no deadlines we’re quality driven
- 10. diverse and distant customers base
- 11. Move fast and break things Seems to be the obvious choice
- 14. The larger the backlog, the nicer the graveyard.
- 15. Prioritization is a nightmare
- 18. To provide the best developer experience we can
- 19. To let customers take care of their business
- 20. To react to a shifting marketplace
- 21. To keep the lights on
- 22. purpose
- 23. purpose tool
- 27. squads
- 28. process
- 29. triage is it a problem?
- 30. “why bucket” - assigned -
- 31. prioritization
- 34. task force • Diverse skillset • Different time zones • Facilitator • Reviewer(s) • Report to the squad
- 35. RFC
- 36. is the problem addressed? Tackle next chunk…
- 37. retrospective
- 40. Mauro Servienti Solution Architect @ Particular Software mauro.servienti@gmail.com @mauroservienti //milestone.topics.it
Hinweis der Redaktion
- Near to zero feedback If we have feedback it’s “apples and oranges” Both are valid, from different contexts
- Customers are far away Little feedback Long term support
- We have to carefully select what to work on next
- Making a decision is very hard
- No way the PO can make a decision
- Back to the drawing board
- Why do we do what we do? What’s the purpose?
- Ktlo -> patch criteria/severity DX -> usuability eurisitcs/personas BV -> system categories, platform map Shift -> tech radar
- Ktlo -> patch criteria/severity DX -> usuability eurisitcs/personas BV -> system categories, platform map Shift -> tech radar
- Ktlo -> patch criteria/severity DX -> usuability eurisitcs/personas BV -> system categories, platform map Shift -> tech radar
- We can segment who is impacted We can predict the impact Is this enough?
- Lack of skills Responsibilities No debate
- Squad per Why: 4/5 people Diverse skillset A mix between a PO/Scrum Master Long living body First come first served
- Nothing is left over