PO vs PM, How to scale Product Ownership within a large enterprise and move traditional BAs into Product Owners.

1. Scaling Agile Product Ownership
- Nitin Ramrakhyani | Head of Products | TESCO
Image Source: :- ://http://beekn.net/wp-content/uploads/2014/01/growth-hacking-retail.jpg
TESCO Agile Day, 2016

2. Not so long ago….in the S/W World
Image Source:- https://i.ytimg.com/vi/lcL678AASFc/maxresdefault.jpg

5. Image Source :- http://www.scrumprojectmanagement.net/wp-content/gallery/Scrum%20Project%20Management%20Framework/800px-IS480_LittleTeam_SCRUM.jpg

6. Image Source :- http://www.scrumprojectmanagement.net/wp-content/gallery/Scrum%20Project%20Management%20Framework/800px-IS480_LittleTeam_SCRUM.jpg

7. Source : Versionone State of Agile Survey 2015

8. Source : Versionone State of Agile Survey 2015

9. We now know “How to Build” awesome software…
Image Source http://www.idgconnect.com/IMG/426/4426/agile-thurs-am-620x354.jpg?1368077781

10. Defines “What to build”?

11. Knows we are building the “right” stuff?

12. “THE” PRODUCT OWNER

13.  Understands Customers / End users
 Understands and manages stakeholders
 Has required domain Knowledge
 Knows “What” the customer wants ,
 “Sequence” in which customer wants it
 “When” the customer wants it.
 Can “Effectively” translate what he knows into what dev
team can understand.
 Know the “business value” of the work being delivered
 Ensures the Development Team understands items in the
Product Backlog to the level needed.
PO Knows It All..

14. Really?

16. Source: Strategic Product Management
PO Focus Area in Scrum Team

19. WHAT TOOLS AGILE PO’S GOT?
 Writing User Stories
 Writing Definition of Done
 Being Co-located? ( really?)
 Sprint/Release Planning
Anything else that they get trained on?

20. And we expect them to win the war?

21. Agile’s focus is on “How”, assuming “Why/What” is figured!

29. Information Silos
Unclear Accountability
Dependencies/Bottlenecks
Slow Decision Making
Expectation Mismatch

30. How do we enable POs to “really own” the product?

31. Scaling Product Ownership
Structure Tools Frameworks Skills

32. #1. Structure

39. #2. PO Tools/ New Weapons

40. Why only for startups?
Image Source: : https://speckyboy.com/2014/09/18/building-minimum-viable-products-spotify/

42. User Story Delivered ≠ Value Delivered

43. Data-driven Decision Making
Image Source: : http://cdn.americanbanker.com/media/newspics/woman-graphs-ts-365.jpg

44. Image Source: :http://www.whymeasurethat.com/wp-content/uploads/2013/09/example-lean-analytics-cycle.png

45. Image Source: http://www.grisanik.com/static/images/47-MVP-cars.jpg:
#Minimum Viable Products

46. #Lean Canvas

47. #Better Prioritization

48. #Impact Mapping

49. #3. Frameworks

50. #SAFe

51. #LeSS

52. #4. Skills

54. SUMMARY
• Focus not just on “How”, but also “Why” & “What”
• Break Products into smaller, manageable chunks based
on Customers/ Modules/ Components and assign
Product ownership.
• Have clear end-2-end accountability.
• Enable POs to take up higher challenges using
– Right Product Management structures & mentoring
– Lean Tools
– Enterprise Agile Frameworks – SAFe/DAD/LeSS etc
– Skills ( Behavioral, Collaboration & Functional)

55. Thank you!Image Source: : http://d33wubrfki0l68.cloudfront.net/09a56d7722727ebcf92fa872b37e349471bbad7b/d64bd/images/articles/keep-calm-and-ship-it-09a56d77.png