Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Improve your Product Backlog Refinement (PBR) Process

482 vues

Publié le

Experiments, ideas, don'ts...

Publié dans : Logiciels
  • Soyez le premier à commenter

  • Soyez le premier à aimer ceci

Improve your Product Backlog Refinement (PBR) Process

  1. 1. Learn to Learn with healthy Product Backlog Refinement process. 2020
  2. 2. A multi-team pbr
  3. 3. Groups of Teachers and learners
  4. 4. A team learning from an expert
  5. 5. The Scrum Guide Says… “Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. … During Product Backlog refinement, items are reviewed and revised.”
  6. 6. ”Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog... “
  7. 7. Try USE TEACHING/LEARNiNG TOOLS youtube.com/watch?v=NLn_mzCfhKw
  8. 8. Try not usingEpics (because they make you focus on wrong things)
  9. 9. ???
  10. 10. Instead: (maybe) think of stones Boulders Rocks Stones Pebbles Gems
  11. 11. Size and value don’t corelate really
  13. 13. Try teachingsplitting https://twitter.com/alexeykri/status/1272452120965459968
  15. 15. Product Backlog Dev Team Payment DB Payment API Payment Validation Payment UI Technical Split one sprint one more sprint one more sprint ???
  16. 16. Complex negative scenarios Complex negative scenarios User is informed if card is not valid INSTEAD Split BY BUSINESS VALUE Payment Payment with Visa Payment with MasterCard Payment with PayPal First positive scenario Complex negative scenarios User can store card data for further usageToo big for a sprint User is informed if card is not valid Still too big for a sprint Card validations
  17. 17. Stakeholders “Buying” Features id theme title estimate sprint bigger picture url 101 payments Visa: expired card 5 s-5 confluence/payments 102 payments Visa: blocked card 8 s-5 confluence/payments 103 payments Visa: success (no fund check) 5 s-5 confluence/payments 104 user profile Avatar: upload (fixed size) 5 s-6 confluence/avatars 105 user profile Avatar: upload (cropping) 13 s-6 confluence/avatars 106 user profile Password: auto expiration 2 s-7 confluence/pwd_rules Flat backlog example
  18. 18. VALUE MINING
  19. 19. https://www.slideshare.net/kentjmcdonald/21-story-splitting-patterns-49940134
  20. 20. https://www.slideshare.net/kentjmcdonald/21-story-splitting-patterns-49940134
  21. 21. Try visual splitting (at awhite-board) linkedin.com/pulse/what-i-tell-yourequirements-like-bubbles-alexey-krivitsky/
  22. 22. Ablack hole
  23. 23. Splitting in action - certainty and value are clear
  24. 24. Try collaboratingwithyour stakeholders https://agilemanifesto.org/
  25. 25. PBR sessions are events inLeSS! Thanks god! http://www.less.works/
  26. 26. IMPORTANT keep satisfied INFLUENCE INTEREST OTHERS monitor KEY PLAYERS manage closely AFFECTED keep informed Simplified stakeholder map “Bad guys”
  27. 27. Turn stakeholders into collaborators That guy
  28. 28. Classical Scrum Dilemma (coming from misunderstanding the PO role) Product Owner vs Stakeholders “How to make sure PO doesn’t lose control when the teams are in direct contact with stakeholders and experts?”
  29. 29. try focus on the bigger picture This guy
  30. 30. try focus on the bigger picture Agenda of a PBR session: Step 1: Bigger Picture (by PO) Step 2: Idea Pitching (by Stakeholders) Step 3: Forming Mixed Groups and Agenda (with the little help of Scrum Masters) Step 4: Learning Starts (Team Members and Stakeholders) This guy This guy
  31. 31. Try facilitating PBRs as interactive workshops “World Café” style 1. Stakeholders as station hosts. 2. A topic per station. 3. Groups rotate across all stations and all learn and contribute to all topics (every 12-20 minutes). 4. => Everyone knows all the topics but in some details. Good stuff! “Open Space” style 1. Stakeholders as session hosts. 2. A topic per session. 3. Groups decide which topics they are interested in and attend those sessions (45-60 minutes). 4. => Only some people know specific topics but in greater details. Good stuff!
  32. 32. Try focusing on the outcome (instead of features) Features (Output) 1. Focus is on features. 2. Discussions are around scope, schedules, estimates… 3. Game is about bargaining (zero-sum game). Can lead to mediocre solutions and boredom in teams due to lack of freedom and creativity. Impact (Outcome) 1. Focus is on user behavior and metrics. 2. Discussions are around impact and desired change. 3. Game is about coming up with minimal product changes to trigger desired behavior impact (win-win-win). Can lead to more employee engagement, cooler solutions and better scope management (surprise!).
  33. 33. https://www.youtube.com/watch?v=kEZIMzIXMmc
  34. 34. Learn to Learn with healthy Product Backlog Refinement process. 2020 Thank you. This was: