AT2012_Pune_LessonsfromaSuccessfulPO_rathinakumar

586 views

Published on

  • Be the first to comment

  • Be the first to like this

AT2012_Pune_LessonsfromaSuccessfulPO_rathinakumar

  1. 1. Building Great Products Lessons from a Successful Product OwnerRathinakumar Balasubramanian, PMP, PMI-ACP, CSM September, 2012
  2. 2. What Is a Great Product? Examples05/05/09 www.agiletour.com
  3. 3. Role of a Product Owner• Build a product Backlog• Priortize the product backlog items• Clarify the backlog items for the development team• Ensure the ROI of the product15/sep/12 www.agiletour.com
  4. 4. Case Study - Our Agile Team Padma Scrum Master Shan Development Team Product Owner Peter Cathy05/05/09 www.agiletour.com
  5. 5. The ProblemThe Team worked really hard.The Product Owner always ensured that the product backlog isup-to-date and prioritized. He spends a lot of timecollaborating with the team.The Scrum Master felt everything went alright. But Lukewarm Response from the customers. WHY????05/05/09 www.agiletour.com
  6. 6. Challenges in Building Great Products• Should solve the need for the end-users• Should provide easy adoption• Should be ahead of competition• Should provide ROI05/05/09 www.agiletour.com
  7. 7. Challenges for the Product Owner1. Dependent on Product Managers, Users, Customer Survey2. Heavy reliance on user stories3. Scalability Issues4. Translation of mental models15/sep/12 www.agiletour.com
  8. 8. Good Practices – 1 A Product Owner Perspective The hardest single part of building a software system is deciding precisely what to build. - Fed Brooks (1987)05/05/09 www.agiletour.com
  9. 9. Good Practices – 1 A Product Owner Perspective ‘Single Source’ for Requirements is a Myth. Conflicting Requirements are the norm.05/05/09 www.agiletour.com
  10. 10. Good Practices – 2 A Product Owner Perspective User Stories are not requirements. They are starting point for building one.05/05/09 www.agiletour.com
  11. 11. Good Practices – 2 A Product Owner Perspective Some things just aren’t user stories. - Mike Cohn05/05/09 www.agiletour.com
  12. 12. Good Practices – 3 A Product Owner PerspectiveScalability Issues Multiple Forms of requirements Example: Conflicting requirements Complexity and Legacy Example: Interdependencies Large organizations Example: Distributed Teams05/05/09 www.agiletour.com
  13. 13. Good Practices – 4 A Product Owner Perspective Software Requirements is a communication problem. - Mike Cohn05/05/09 www.agiletour.com
  14. 14. Good Practices – 4 A Product Owner PerspectiveRequirements is a SKILL – Cognitive 1. Visualizing 2. Writing 3. Communicating 4. Nurturing05/05/09 www.agiletour.com
  15. 15. Summary 1 Let requirements to evolve throughout the product development. Let the requirements come from a wide-range of stakeholders05/05/09 www.agiletour.com
  16. 16. Summary 2 Agile requirements are essentially conversations between the people who will use the product and the people who build the product. Conversations does not stop with talking.05/05/09 www.agiletour.com
  17. 17. Summary 3 Adopt suitable modes / forms of expressing requirements. If it makes sense to use forms other than user stories, the do so. Realise the ‘scale’ is an important factor.05/05/09 www.agiletour.com
  18. 18. Summary 4 Be cognizant that it takes special skills to be a successful product owner. Good News: It is a skill that can be acquired and strengthened.05/05/09 www.agiletour.com
  19. 19. Questions? THANK YOU05/05/09 www.agiletour.com

×