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