Business Analyst to Product Owner: Making the Leap

723 views

Published on

Business Analyst to Product Owner: Making the Leap

By Jason Novack and Brian Bozzuto of BigVisible Solutions

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
723
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Business Analyst to Product Owner: Making the Leap

  1. 1. Business Analyst to Product Owner:Making the LeapNovember 2, 2011Jason NovackBrian BozzutoBigVisible Solutions
  2. 2. What is a Product Owner?•  Responsible for the business value of the project (scrumalliance.org)•  Responsible for maximizing the value of the product and the work of the Development Team. (scrum.org) 2
  3. 3. What do we know about PO’s?•  Responsible for defining product vision•  Has to be able to articulate a strategy to achieve the vision•  Defines and prioritizes the product backlog•  Makes decisions on product direction•  Maps the product vision to development stories•  Accepts work results•  Responsible for ROI•  Voice of the customer•  Stakeholder funnel which all requests flow through•  Has to make decisions to move things forward with limited information 3
  4. 4. Where do good PO’s come from? 4
  5. 5. Technology Experience•  Flow of development•  Appreciation for details•  Understanding of team dynamics 5
  6. 6. Decision Making•  Decisive•  Willing to make mistakes•  Rarely have all the data 6
  7. 7. Domain Knowledge•  Knowledge supports speed•  Shortens feedback loops•  Builds trust with customers/users 7
  8. 8. Story time….Question: Can an airplane fly powered only by the pilot’s body power?Kramer Challenge: £50,000 for the first person to build a plane thatcould fly a figure eight around two markers one half-mile apart AND£100,000 for the first person to fly across the English Channel.How would you approach winning this challenge? Keep in mindthe tools of the day… 8
  9. 9. ExerciseThe Kramer challenge: • Build a human powered plane that can fly a figure eight around two markers one half-mile apart • Build a human powered plane that can fly across the English ChannelBreak into groups of 3 – 4 and spend roughly 5 minutes discussing how youwould approach winning this challenge?Keep in mind the tools of the day… 9
  10. 10. Here’s what happened 18 Years Many attempts Source: wikipedia All FailedSource: http://weblab.open.ac.uk/firstflight/ 10
  11. 11. Another angleQuestion: Can an airplane fly powered only by the pilot’s body power?Question: How can you build a plane that could be rebuilt in hours notmonths? 11
  12. 12. Gossamer Condorhttp://en.wikipedia.org/wiki/Gossamer_Condor 12
  13. 13. Gossamer Albatrosshttp://en.wikipedia.org/wiki/Gossamer_Albatross 13
  14. 14. What are the lessons? •  When you are solving something hard, re-ask the problem so your solution helps you learn faster •  Failure is part of innovating 14 http://www.azarask.in/blog/post/the-wrong-problem/
  15. 15. PO Archetypes 15
  16. 16. The Stenographer Key Behaviors •  Limited autonomy •  Documents requirements from other (usually one) source •  Limited strategic thinking Growth Opportunities •  Build Expertise •  Engage a broad range of stakeholders
  17. 17. The Decider Key Behaviors •  Decisive prioritization •  Iteratively build & evaluate product Growth Opportunities •  Learn about domain •  Engage more stakeholders 17
  18. 18. Techniques for Deciders Small Bets Big Hairy Goals Value Stream Analysis 18
  19. 19. The Genius Key Behaviors •  Deep product domain expertise •  Able to develop novel new solutions Growth Opportunities •  Convey complex problems simply •  Continue to learn •  Engage stakeholders 19
  20. 20. The Diplomat Key Behaviors •  Multiple stakeholder engagement •  Work prioritization Growth Opportunities •  Go beyond zero sum negotiations •  Establish a common vision •  Bring disparate groups together 20
  21. 21. Techniques for Diplomats Success Criteria Humanized Customers Rapid Feedback 21
  22. 22. The Alchemist Key Behaviors •  Actively engage numerous stakeholders •  Identify 3rd way solutions Growth Opportunities •  Build further product expertise •  Identify opportunities for innovation
  23. 23. PO Archetypes 23
  24. 24. To re-frameResponsible for Responsible formaximizing the building better value of the and innovativeproduct and the products that are work of the simple and make Development users actually Team. want to use. 24
  25. 25. So, how do you make the leap? 25
  26. 26. Re examine By looking at the problem differently, you can start to seethe different patterns and solutions emerge.problemLearn to Emphasize learning as a key way of being. Don’t be afraid ofLearn being wrong. Learning gives PO’s real empirical data that can be used to iterate quickly. Being able to make quick decisions with limited visibility is aBe Decisive key trait of a good PO. Waiting for all the info or data results in long lead times and missed opportunities. Understanding the problem space you are operating in is key toLearn the moving quickly and speaking to your customers in a way theyDomain can understand, trust and respect. 26
  27. 27. Questions 27
  28. 28. Top 10 Products we never knew we needed 1. Smart phones 2. Google 3. Wireless connections 4. Digital photography 5. Supermarket convenience foods 6. Text Messaging 7. Online shopping 8. Flat Screen TV’s 9. On demand movies and DVR’s 10. GPS and iPod’s Source: ShopSmart Magazine survey 28

×