Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Product Management With Product Developed By Many Teams

3,112 views

Published on

Presentation for my talk at ALE 2011 conference in Berlin, 2011-09-07. I talked about Product Management in Agile organization with product developed by many teams. In the talk i covered 4 main topics: organizing teams, getting Product Owners, planning cross team features, and fitting research into all of this.

Published in: Technology, Design
  • Be the first to comment

Product Management With Product Developed By Many Teams

  1. 1. Product Management <br />with product developed by many teams<br />Vaidas Adomauskas<br />2011-09-07<br />
  2. 2. Vaidas Adomauskas<br />Blog: http://scrum.agile.lt<br />Twitter: @adomauskas<br />SlideShare: http://www.slideshare.net/vaidasa<br />LinkedIn:http://www.linkedin.com/in/vaidas<br />
  3. 3. Agenda<br />Context<br />Teams<br />Product Owners / Managers<br />Features<br />Research<br />Summary and Q/A<br />Disclaimer<br />
  4. 4. Context<br />Adform system<br />
  5. 5. Just online <br />
  6. 6. Everyone sees banners…<br />
  7. 7. Planning<br />
  8. 8. Optimization<br />
  9. 9. Reporting<br />
  10. 10. Publisher Web<br />Advertiser Web<br />Search Engine<br />Banner<br />Searched keyword<br />Click<br />Click<br />Page<br />Banner<br />Page<br />Landing Page<br />…….<br />Text Ad<br />Browsing Tracking Transactions<br />Impressions, clicks, other transactions<br />Impressions, clicks, other transactions<br />Internet<br />Anyone in the room has similar system?<br />IN: Request or Event<br />OUT: Content<br />Ad Serving and Web Analytics Front End<br />Middleware, Databases, DataWarehouses, BI Back End<br />Management and Planning Tools, Reporting, BI Tools<br />Partners<br />Agencies<br />Publishers<br />Creative Agencies<br />Advertisers<br />Operators<br />
  11. 11. Scrum implementation<br />
  12. 12. Teams<br />How to organize?<br />
  13. 13. Feature Team<br />Component Team<br />Highest valuefeatures<br />Less delay<br />Familiar or “fast” features<br />Increased delay<br />Craig Larman, Bas Vodde - “Practices for Scaling Lean & Agile Development”, http://www.craiglarman.com/<br />
  14. 14. Feature or component teams?<br />
  15. 15. Component Teams…<br />Good<br />Consider<br />Easy start - developers know components, not features<br />Testers/analysts divided to teams<br />How to divide components?<br />How to run valuable sprint reviews?<br />How to plan features?<br />
  16. 16. Publisher Web<br />Advertiser Web<br />Search Engine<br />Banner<br />Searched keyword<br />Click<br />Click<br />Page<br />Team<br />Team<br />Team<br />Team<br />Team<br />Team<br />Team<br />Team<br />Banner<br />Page<br />Landing Page<br />…….<br />Text Ad<br />Browsing Tracking Transactions<br />Impressions, clicks, other transactions<br />Impressions, clicks, other transactions<br />Internet<br />IN: Request or Event<br />OUT: Content<br />Ad Serving and Web Analytics Front End<br />Middleware, Databases, DataWarehouses, BI Back End<br />Management and Planning Tools, Reporting, BI Tools<br />Partners<br />Agencies<br />Publishers<br />Creative Agencies<br />Advertisers<br />Operators<br />
  17. 17. Start with component teams<br />Move to feature teams<br />
  18. 18. Product Owners / Managers<br />How to start?<br />
  19. 19. Where did POs come from?<br />
  20. 20. POs from development…<br />Good<br />Consider<br />Easy start<br />System Analyst – Product Owner<br />Project Manager – Scrum Master<br />Easy synchronization<br />Knows domain/people<br />Choose people, not their titles<br />No real ROI decisions<br />No direct contact with customers<br />
  21. 21. Scrum start<br />
  22. 22. Birth of Product Areas<br />… and PM department<br />
  23. 23. Director - Product Management<br />Start with PM from development<br />Create new (or educate existing) PM department<br />Education<br />1 CSPO in 2010<br />7 CSPOs in 2011<br />PMs trainings<br />
  24. 24. Features<br />How to plan?<br />
  25. 25. Video cube – new event (e.g. banner turn)<br />Planning – set in UI<br />Banner – handle event and pass it<br />Serving – accept and record<br />Warehouse – store and attribute<br />Reporting – add to report (create new)<br />How to plan/execute this?<br />
  26. 26. Feature with few teams<br />Plan:<br />Reality:<br />
  27. 27. Feature with few teams<br />What works:<br />Assign clear “main (feature)” PM (PO)<br />Main PM drives this process<br />Cross-functional “teams of teams”!<br />
  28. 28. Research<br />How to fit?<br />
  29. 29. Research<br />Software projects<br />http://lunar.lostgarden.com/uploaded_images/essay-DiscovertheFunEarly-ScrumComplexity-729863.jpg<br />
  30. 30. Scrum start<br />Who does research?<br />
  31. 31. Scrum start – in component team<br />
  32. 32. Research (RnD)<br />Scrum now – in “consultants” team<br />
  33. 33. Research in “consultants” team…<br />Good<br />Consider<br />Dedicated time to try new technologies<br />Review of legacy applications<br />Consultant likequestions<br />Agree on research priorities (with PMs)<br />Involve relevant teams<br />Communicate results<br />Treat research differently than development<br />
  34. 34. Summary<br />What can I use from this talk?<br />
  35. 35. Start with component teamsMove to feature teams<br />Start with PM from developmentCreate new (or educate existing) PM department<br />Cross-functional “teams of teams”!<br />Treat research differently than development<br />
  36. 36. Thank you<br />Let’s Scrum!<br />Vaidas Adomauskas<br />v.adomauskas@gmail.com<br />http://scrum.agile.lt<br />

×