• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Scaling up product manager/product owner organizations
 

Scaling up product manager/product owner organizations

on

  • 754 views

This talk identifies that product ownership AND product management are both critical to success of commercial agile software companies; that they are NOT identical, but strongly overlapped; and that ...

This talk identifies that product ownership AND product management are both critical to success of commercial agile software companies; that they are NOT identical, but strongly overlapped; and that selecting/hiring/training/managing/organizing a product team team is very necessary. No cookie-cutter algorithms for assigning people to product roles.

Picked by Portland Product Camp attendees as "best of camp," and adapted from a talk I gave for Cisco IPTV on 4 April 2014.

Statistics

Views

Total Views
754
Views on SlideShare
607
Embed Views
147

Actions

Likes
5
Downloads
0
Comments
0

5 Embeds 147

http://www.mironov.com 94
http://feedly.com 32
http://www.scoop.it 13
http://digg.com 7
https://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • HIPPO: highest paid person’s opinion <br /> Engineering-driven, purely logical decision-making isn’t enough. Different goals, different opinions, timelines (current quarter), asking for more investigation as a way to veto proposals…
  • It’s not that a product owner is unable to do this much longer list of things. It’s that we don’t choose, train, mentor, measure or reward them for the broader set of things. And we keep them very busy with the short list. <br /> That’s one of the reasons why agile delivers more/better – because they can finally get enough product ownership to build more of the right things.
  • Huge positive Dev feedback <br /> 8.1 release: how many PMs are there on this effort? <br /> “User First” is pulling PMs in another direction: more emphasis on customer needs, rather than detailed tech specs <br /> ENG product managers have $150M to $300M each in product sales. There’s no way they can ignore Cisco sales, marketing and administrative demands. And a ton of customers they are each big enough to deserve special treatment <br /> <br /> I’ve successfully handled all of product management and all of product ownership for one dev team of 11, at a great Bay Area startup. But that was with less corporate overhead, and a lot of experience.
  • TMEs may be good candidates, but they already have more-than-full-time jobs to do closing business.
  • Pulled into exec briefing center, out on sales calls, into planning/management sessions <br /> Q for devs: how many of expect your PM to reliably be in 80% of your standups?
  • Degenerative case: one person has to do it all. Suck it up.
  • How many POs does this imply for a division with 2500 engineers, likely 250 scrum teams? <br /> Unworkable: lack of overall product coordination, typical for many PO slots to be unfilled <br /> Scrum of scrums is primarily to address TECHNICAL issues, TECHNICAL dependencies, TECHNICAL architecture. Not impact on customers and markets of many subtle choices made daily. <br /> <br />
  • Unworkable: lack of overall product coordination, typical for many PO slots to be unfilled <br /> Scrum of scrums is primarily to address TECHNCIAL issues, TECHNICAL dependencies, TECHNICAL architecture. Not impact on customers and markets of many subtle choices made daily.
  • Holding back on determining if one PO can cover two teams. Still shows that we need a PM/PO team of around 6 to handle a project with 8 teams.
  • Negotiate explicit working agreements <br /> <br /> If we have 2500 engineers in the division, that implies ~ 250 scrum teams, ~200 full-time PM+PO. Staying out of the politics of budgets and open reqs (who finds the heads), but someone may be 50 headcount short. <br /> This entire go-agile (dEV Escape Velocity) effort is at risk if we ignore this problem

Scaling up product manager/product owner organizations Scaling up product manager/product owner organizations Presentation Transcript

  • Product Managers, Product Owners, and Scalable Models for Agile Product Teams 1 © 2014. This presentation and all derivative works copyright Rich Mironov | mironov.com
  • About Rich Mironov • Veteran product manager/exec/strategist • Business models, agile, organizing product teams • 6 startups as “product guy” or CEO • Ran first Product Camp, first agile product manager/owner tracks 2
  • Agenda 1. Product Managers ≠ Product Owners 2. Failure Modes 3. Small and Large Organizational Maps 3
  • Organizational Context • “Product manager” is a job title • “Product owner” is an agile team role • Overlapping, but very different scope and skills • “One-per-scrum-team” does not match complexity of large-scale commercial software • Work has to get done, regardless of title 4
  • What Does a Product Manager Do? For revenue software… • Drives delivery and market acceptance of whole products • Targets market segments, not individual customers 5
  • What Does a Product Manager Do? market information, priorities, requirements, roadmaps, epics, user stories, backlogs, personas, MRDs… product bits strategy, forecasts, commitments, roadmaps, competitive intelligence… budgets, staff, targets field input, market feedback segmentation, messages, benefits/features, pricing, qualification, demos… Markets & Customers Development Marketing& Sales Executives Product Management 6
  • Product Management: Inherently Political • Logic and facts are not sufficient • Sales teams get paid for closing individual deals • Regional and vertical groups focus on their narrow needs • HIPPO • Responsibility without authority • Keep the process moving 7
  • What PM Hiring Managers Want Tech product manager job postings • 76% want 3+ years PM experience • 93% want excellent verbal and written communication skills • 93% want a BS (68% prefer CS/EE) • 32% want MBAs • 88% want experience in their segment 8
  • Agile Methodology with Scrum 9 Product Backlog Features & User Stories Release Backlog Features & User Stories Sprint Backlog User Stories Potentially releasable software Software release Accepted story (“DONE”) Review Demo, feedback Retrospective Process improvement 1 day Daily Standup Sprint: 1 to 3 weeks No changes in duration or goal Release planning Sprint planning Charter Release Retrospective Process improvement N sprints
  • What does a Product Owner Do? • “…represents the customer’s interest in backlog prioritization and requirements questions... available to the team at any time.” • Provides intense sprint-level focus: stories, backlog, prioritization, acceptance • One product owner per team, not per product • Wins development admiration and inclusion • Feeds the hungry agile beast 10
  • Feeding the Agile Beast Steam engine “fireman” needs to constantly shovel coal, otherwise the train will stop 11
  • ‘small p’ Product Owner 12 backlog, priorities, epics, user stories, personas, demo feedback Markets & Customers Development Marketing& Sales Executives Product Owner showcase customers
  • PO/PM Scope 13 Product Backlog Features & User Stories Release Backlog Features & User Stories Sprint Backlog User Stories Potentially releasable software Software release Accepted story (“DONE”) Review Demo, feedback Retrospective Process improvement 1 day Daily Standup Sprint: 1 to 3 weeks No changes in duration or goal Release planning Sprint planning Charter Release Retrospective Process improvement N sprints product manager focus product owner focus
  • Product Manager Has More Levers • Engineering Output • Product features • Order of delivery • Product / Market / Business Model • Pricing • Competitive positioning • Partners and Channels • Services and Support • Fit with corporate strategy • Product split, merge or EOL 14 Product manager After: Greg Cohen Product owner
  • Agenda 1. Product Managers ≠ Product Owners 2. Failure Modes 3. Small and Large Organizational Maps 15
  • Product Management: Oversubscribed, Overcommitted, Burning Out • Most product management teams are already understaffed • Product ownership adds 40-60% more critical work • Urgency of stories, backlog grooming, sprint planning, standups, acceptance • One product manager can “do it all” for a single team • But typical Dev:PM ratio is 35:1, not 10:1 16
  • How Development Organizations Typically Pick Product Owners • SMEs with technical chops, story writing experience, “already know” the market • Rarely demand market-side experience • Undervalue organizational blocking skills • Belief in rational/unemotional/technical customers • Slant toward smartest users 17
  • Product Management Failure Mode Product Manager fails agile team when… • Part-timer, not engaged with team • Lack of detail on stories • Stale backlog • Handwaving and bluster • Best of intentions, but pulled in too many directions • “Build what I meant” 18
  • Product Owner Failure Modes Product Owner fails markets when… • Weak on market realities: pricing, packaging, selling cycle, upgrades, discounting, competitive dynamics • Disconnected from Marketing, Sales, Support • Trades off company strategy for product features • Sees showcase customers as typical 19
  • Agenda 1. Product Managers ≠ Product Owners 2. Failure Modes 3. Small and Large Organizational Maps 20
  • Minimal PM/PO “Organization” 21 VP or Founders Heroic Single Product Manager/Owner more technical more market-focused “management”
  • Dysfunctional PO/PM Organization 22 VP Eng Product Owners VP Marketing Product Managers more technical more market-focused “management”
  • PM/PO Product Peers 23 PM Director/ Product Strategist GM / VP Eng / VP Products / CPO more technical more market-focused “management”
  • PM/PO: Market Mentoring 24 GM / VP Eng / VP Products / CPO more technical more market-focused “management”
  • 90 Person Project (1 Product, 8 Teams) 25 Product Manager TEAM PO SM TEAM PO SM TEAM PO SM TEAM PO SM TEAM PO SM TEAM PO SM TEAM POSM TEAM PO SM
  • What Does Each Team Do? 26 Product Manager HEADLINE FEATURES PERFORMANCE RE-ARCH DRIVERS & CONNECTORS UX/UI TEAM PO SM TEAM PO SM TEAM PO SM TEAM PO SM TEAM PO SM TEAM PO SM TEAM POSM TEAM PO SM
  • Right Product Owners? 27 Lead Prod Manager PERFORMANCE RE-ARCH DRIVERS & CONNECTORS UX/UI TEAM SM TEAM SM TEAM SM TEAM SM TEAM SM TEAM SM TEAM SM Product Mgr? HEADLINE FEATURES TEAMSM UX Lead? Sales Eng? Two Performance Architects?
  • Wrong Product Owners! 28 PERFORMANCE RE-ARCH DRIVERS & CONNECTORS UX/UI TEAM SM TEAM SM TEAM SM TEAM SM TEAM SM TEAM SM TEAM SM UX Lead HEADLINE FEATURES TEAMSM Sales Eng Perf Arch Product Mgr Lead Prod Manager
  • Delegating Product Ownership • No cookie-cutter solution, no magic formula • Varies with scope, teams, technical depth, skills… • What is this team working on? Who brings right talent mix? • Full-time product owners, not borrowed 10% • Solid or strong dotted line to product management • Vigorous daily discussion among product team • Product management keeps whole-product responsibility 29
  • Takeaways 1. Must fully staff product owner roles • Not a sideline, not an add-on, not an afterthought 2. On large projects, product managers are not default product owners for every team 3. Need to thoughtfully select/hire/train POs and PMs 4. IMHO, cookie-cutter assignments endanger products 30
  • Rich Mironov Mironov Consulting 233 Franklin Street, Suite 308 San Francisco, CA 94102 31 /in/RichMironov @RichMironov Rich@Mironov.com +1-650-315-7394