product management with product developed by many teams
DESCRIPTION
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.TRANSCRIPT
Product Management
with product developed by many teams
Vaidas Adomauskas2011-09-07
Vaidas Adomauskas
Blog: http://scrum.agile.lt Twitter: @adomauskas SlideShare: http://www.slideshare.net/vaidasa LinkedIn: http://www.linkedin.com/in/vaidas
Agenda
Context
Teams Product Owners / Managers Features Research
Summary and Q/A
Disclaimer
Context
Adform system
Just online
Everyone sees banners…
Planning
Optimization
Reporting
Management and Planning Tools, Reporting, BI Tools
Middleware, Databases, DataWarehouses, BI Back End
Ad Serving and Web Analytics Front End
Internet
Publisher Web Advertiser Web Search Engine
Banner
Banner
Page
Searched keywordClick Click
Impressions, clicks,
other transactionsImpressions, clicks,
other transactions
Browsing Tracking
Transactions
Text AdLanding
Page
Page
…….
IN: Request or Event
OUT: Content
Agencies Publishers Creative AgenciesAdvertisers Operators Partners
Anyone in the room has
similar system?
Scrum implementation
• 1 team• 1 project
Scrum Pilot 2009-12
• >40 people• 6 Scrum teams
Scrum Start2010-03 • >60 people
• 8 Scrum teams• Research team
Scrum Now2011-09
Teams
How to organize?
Feature Team
Highest value features
Less delay
Component Team
Familiar or “fast” features
Increased delay
Craig Larman, Bas Vodde - “Practices for Scaling Lean & Agile Development”, http://www.craiglarman.com/
Director
Team 1
Product Owner
Scrum Master
Team
Team 2
Product Owner
Scrum Master
Team
Team 3
Product Owner
Scrum Master
Team
Team 4
Product Owner
Scrum Master
Team
Team 5
Product Owner
Scrum Master
Team
Team 6
Product Owner
Scrum Master
TeamFeature or component teams?
Component Teams…
Good
Easy start - developers know components, not features
Testers/analysts divided to teams
Consider
How to divide components?
How to run valuable sprint reviews?
How to plan features?
Management and Planning Tools, Reporting, BI Tools
Middleware, Databases, DataWarehouses, BI Back End
Ad Serving and Web Analytics Front End
Internet
Publisher Web Advertiser Web Search Engine
Banner
Banner
Page
Searched keywordClick Click
Impressions, clicks,
other transactionsImpressions, clicks,
other transactions
Browsing Tracking
Transactions
Text AdLanding
Page
Page
…….
IN: Request or Event
OUT: Content
Agencies Publishers Creative AgenciesAdvertisers Operators Partners
Team
Team
Team
Team Team
Team
Team
Team
Director
Program X Development Manager
Team 1
Product Owner
Scrum Master
Team
Team 2
Product Owner
Scrum Master
Team
Team 3
Product Owner
Scrum Master
Team
Program Y Development Manager
Team 4
Product Owner
Scrum Master
Team
Team 5
Product Owner
Scrum Master
Team
Program Z Development Manager
Team 6
Product Owner
Scrum Master
Team
Team 7
Product Owner
Scrum Master
Team
Team 8
Product Owner
Scrum Master
Team
Start with component teams
Move to feature teams
Product Owners / Managers
How to start?
Director
Team 1
Product Owner
Scrum Master
Team
Team 2
Product Owner
Scrum Master
Team
Team 3
Product Owner
Scrum Master
Team
Team 4
Product Owner
Scrum Master
Team
Team 5
Product Owner
Scrum Master
Team
Team 6
Product Owner
Scrum Master
Team
Where did POs come from?
POs from development…
Good
Easy start System Analyst – Product
Owner Project Manager – Scrum
Master
Easy synchronization
Knows domain/people
Consider
Choose people, not their titles
No real ROI decisions
No direct contact with customers
Scrum start
Birth of Product Areas
Director – Project Management
Director – Product Area 1
Product Owner W
Product Owner Z
…
Director – Product Area 2
Product Owner X
…
…
… and PM department
Director
Program X Development
Manager
Team 1
Product Owner
Scrum Master
Team
Team 2
Product Owner
Scrum Master
Team
Team 3
Product Owner
Scrum Master
Team
Program Y Development Manager
Team 4
Product Owner
Scrum Master
Team
Team 5
Product Owner
Scrum Master
Team
Program Z Development
Manager
Team 6
Product Owner
Scrum Master
Team
Team 7
Product Owner
Scrum Master
Team
Team 8
Product Owner
Scrum Master
Team
Director - Product Management
Education 1 CSPO in 2010 7 CSPOs in 2011 PMs trainings
Start with PM from development
Create new (or educate existing)
PM department
Features
How to plan?
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?
Feature with few teams
Plan:
Reality:
Feature with few teams
What works: Assign clear “main (feature)” PM (PO) Main PM drives this process
Cross-functional “teams of teams”!
Research
How to fit?
Software projects
Research
http://lunar.lostgarden.com/uploaded_images/essay-DiscovertheFunEarly-ScrumComplexity-729863.jpg
Director
Team 1
Product Owner
Scrum Master
Team
Team 2
Product Owner
Scrum Master
Team
Team 3
Product Owner
Scrum Master
Team
Team 4
Product Owner
Scrum Master
Team
Team 5
Product Owner
Scrum Master
Team
Team 6
Product Owner
Scrum Master
Team
Scrum start
Who does research?
Director
Team 1
Product Owner
Scrum Master
Team
Team 2
Product Owner
Scrum Master
Team
Team 3
Product Owner
Scrum Master
Team
Team 4
Product Owner
Scrum Master
Team
Team 5
Product Owner
Scrum Master
Team
Team 6
Product Owner
Scrum Master
Team
Scrum start – in component team
Director
Program X Development
Manager
Team 1
Product Owner
Scrum Master
Team
Team 2
Product Owner
Scrum Master
Team
Team 3
Product Owner
Scrum Master
Team
Program Y Development
Manager
Team 4
Product Owner
Scrum Master
Team
Team 5
Product Owner
Scrum Master
Team
Program Z Development
Manager
Team 6
Product Owner
Scrum Master
Team
Team 7
Product Owner
Scrum Master
Team
Team 8
Product Owner
Scrum Master
TeamResearch
(RnD)
Scrum now – in “consultants” team
Research in “consultants” team…
Good
Dedicated time to try new technologies
Review of legacy applications
Consultant like questions
Consider
Agree on research priorities (with PMs)
Involve relevant teams
Communicate results
Treat research differently
than development
Summary
What can I use from this talk?
Start with component teams
Move to feature teams
Start with PM from development
Create new (or educate existing)
PM department
Cross-functional “teams of teams”!
Treat research differently
than development
