How to Own a Really Big Complex Product v3

852 views
781 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
852
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • So here is our small agile team.
  • Agile teams are cross functional units that have everything they need to deliver some increment of business value. In a software organization… the agile team is going to have one or more developers…
  • They will have one or more QA testers. Sometimes teams have technical testers that are responsible for writing unit tests… sometimes this is left up to the developers. Sometimes teams have manual testers… possibly exercising the UI. Many teams will do both kinds of testing.
  • Sometimes a team will someone playing the role of business analyst. This can be a dedicated position on the team… or it might be blended with some other role… maybe a lead developer. Often times teams will have a BA that is serving as a proxy product owner for the real customer or product owner. Dedicated or blended Custome proxy
  • Small agile teams don’t typically have or need a project manager. I believe that there is a place for project management on an agile teams… but often project managers are coordinating the activities of several teams and doing some higher level planning activities and providing.
  • Agile teams will usually have someone in the role of ScrumMaster or Agile process coordinator. This can be a dedicated position on the team or a role that is shared with another role on the team. Sometimes you have a dedicated ScrumMaster but they are working with more than one agile team at a time.
  • Last but not least we have a product owner. They are the interface between the team and the business. They are the single wringable neck and responsible for the business outcomes of the product. They define requirements, set the priorties, and othewise help the team converge on the best possible outcome to meet the business objectives. Agile teams have all these roles in some form or fashion… they are self contained and independent. This kind of team is the backdrop to almost everything you read about adopting agile. This is such an important concept because if this isn't’ the kind of team you are building as you adopt agile… some of the things you are learning about just aren’t going to work.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • 11. We start with high level requirements that become more detailed as we learn more about the product we are building.  We start with high level architectural representations that emerge toward detailed design as we actually begin developing the working product.  You might think of this as rolling wave planning or progressive elaboration.  The idea is that we plan based on what we know, and plan more as we learn more.  
  • 12. Our goal is to recognize, that on projects where we have a tremendous amount of uncertainty... we don't want to create plans that don't reflect our current understanding of reality.  We don't want to assume the process overhead of change management, when change is going to be the norm.  Agile gives us a way to manage our projects, in the face of uncertainty, while aggressively working to reduce risk and uncertainty.   
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • This slide sequence is mainly to setup the talk. Prior to this I want to go through an introduction, talk about how this talk builds on the talk I did yesterday, how it is an experience report where I started developing and writing about some of these ideas around scaling agile across multiple teams.
  • Setup:Get blue tapeCreate a backlog sheetTape up cardsCreate a story boardCreate 4 sprint boardsCreate an impediments boardCreate a parking lot boardCreate a Birthday card
  • How to Own a Really Big Complex Product v3

    1. 1.
    2. 2. How to Own a Really Big Complex Product<br />Presented by: Mike Cottmeyer<br />
    3. 3. Mike CottmeyerEnterprise Agile Coachmike@cottmeyer.com404.312.1471leadingagile.comfacebook.com/leadingagiletwitter.com/mcottmeyerlinkedin.com/in/cottmeyer<br />
    4. 4. Agenda<br />
    5. 5. Agenda<br />Product Owner Basics<br />
    6. 6. Agenda<br />Product Owner Basics<br />Complex Products in Large Enterprises<br />
    7. 7. Agenda<br />Product Owner Basics<br />Complex Products in Large Enterprises<br />Exploring Product Ownership<br />
    8. 8. Agenda<br />Product Owner Basics<br />Complex Products in Large Enterprises<br />Exploring Product Ownership<br />Managing the Enterprise Backlog<br />
    9. 9. The Product Owner in Scrum<br />
    10. 10. Team<br />
    11. 11. Developers<br />
    12. 12. Testers<br />Developers<br />
    13. 13. Analyst<br />Testers<br />Developers<br />
    14. 14. Analyst<br />PM<br />Testers<br />Developers<br />
    15. 15. Analyst<br />CSM<br />Testers<br />Developers<br />
    16. 16. Product Owner<br />Analyst<br />CSM<br />Testers<br />Developers<br />
    17. 17. The Product Owner in Scrum<br />Creates the PPBL<br />
    18. 18. The Product Owner in Scrum<br />Creates the PPBL<br />Prioritizes the PPBL<br />
    19. 19. The Product Owner in Scrum<br />Creates the PPBL<br />Prioritizes the PPBL<br />Elaborates the requirements<br />
    20. 20. The Product Owner in Scrum<br />Creates the PPBL<br />Prioritizes the PPBL<br />Elaborates the requirements<br />Communicate vision<br />
    21. 21. The Product Owner in Scrum<br />Creates the PPBL<br />Prioritizes the PPBL<br />Elaborates the requirements<br />Communicate vision<br />Represents the customer<br />
    22. 22. The Product Owner in Scrum<br />Creates the PPBL<br />Prioritizes the PPBL<br />Elaborates the requirements<br />Communicate vision<br />Represents the customer<br /><ul><li>Participates in the Scrum meetings</li></li></ul><li>The Product Owner in Scrum<br />Creates the PPBL<br />Prioritizes the PPBL<br />Elaborates the requirements<br />Communicate vision<br />Represents the customer<br /><ul><li>Participates in the Scrum meetings
    23. 23. Inspects the product</li></li></ul><li>The Product Owner in Scrum<br />Creates the PPBL<br />Prioritizes the PPBL<br />Elaborates the requirements<br />Communicate vision<br />Represents the customer<br /><ul><li>Participates in the Scrum meetings
    24. 24. Inspects the product
    25. 25. Changes direction</li></li></ul><li>The Product Owner in Scrum<br />Creates the PPBL<br />Prioritizes the PPBL<br />Elaborates the requirements<br />Communicate vision<br />Represents the customer<br /><ul><li>Participates in the Scrum meetings
    26. 26. Inspects the product
    27. 27. Changes direction
    28. 28. Communicates progress</li></li></ul><li>The Product Owner in Scrum<br />Creates the PPBL<br />Prioritizes the PPBL<br />Elaborates the requirements<br />Communicate vision<br />Represents the customer<br /><ul><li>Participates in the Scrum meetings
    29. 29. Inspects the product
    30. 30. Changes direction
    31. 31. Communicates progress
    32. 32. Terminates the sprint</li></li></ul><li>The Single Wringable Neck<br />
    33. 33. Product Owner is a BIG Job!<br />
    34. 34. Product Owner is a BIG Job!<br />Product Manager… vision and direction<br />
    35. 35. Product Owner is a BIG Job!<br />Product Manager… vision and direction<br />Project Manager… sequence and status<br />
    36. 36. Product Owner is a BIG Job!<br />Product Manager… vision and direction<br />Project Manager… sequence and status<br />Business Analyst… elaborating requirements<br />
    37. 37. Product Owner is a BIG Job!<br />Product Manager… vision and direction<br />Project Manager… sequence and status<br />Business Analyst… elaborating requirements<br />Quality Assurance… inspecting outcomes<br />
    38. 38. Product Owner is a BIG Job!<br />Product Manager… vision and direction<br />Project Manager… sequence and status<br />Business Analyst… elaborating requirements<br />Quality Assurance… inspecting outcomes<br />Management… terminating and changing<br />
    39. 39. Product Owner is a BIG Job!<br />Product Manager… vision and direction<br />Project Manager… sequence and status<br />Business Analyst… elaborating requirements<br />Quality Assurance… inspecting outcomes<br />Management… terminating and changing<br />User Experience… usability<br />
    40. 40. Product Owner is a BIG Job!<br />Product Manager… vision and direction<br />Project Manager… sequence and status<br />Business Analyst… elaborating requirements<br />Quality Assurance… inspecting outcomes<br />Management… terminating and changing<br />User Experience… usability<br />Team Member… participates with the team<br />
    41. 41. Owning Complex Products<br />
    42. 42. Owning Complex Products<br />
    43. 43. Owning Complex Products<br />Biller Transactions<br />Fin Inst. Transactions<br />Credit Card Payments<br />ACH Payments<br />Fraud/Risk<br />Identity/ Enrollment<br />SAS<br />SAP<br />Corporate Billing<br />Web<br />IVR<br />Payments<br />Risk<br />Business Intelligence<br />Corporate Financials<br />Partner Communication<br />Bus Intel/ Reporting<br />
    44. 44. User Story<br />Screen<br />User Story<br />Team<br />User Story<br />Report<br />User Story<br />User Story<br />Database<br />User Story<br />User Story<br />
    45. 45. User Story<br />Screen<br />User Story<br />Team<br />User Story<br />Report<br />User Story<br />User Story<br />Database<br />User Story<br />User Story<br />
    46. 46. Team 1<br />
    47. 47. Team 2<br />Team 1<br />
    48. 48. Team 2<br />Team 1<br />Team 3<br />
    49. 49. Team 2<br />Team 1<br />Team 3<br />Product<br />A<br />
    50. 50. Team 2<br />Team 1<br />Team 3<br />Product<br />B<br />Product<br />A<br />
    51. 51. Team 2<br />Team 1<br />Team 3<br />Product<br />B<br />Product<br />A<br />
    52. 52. Biller Transactions<br />Fin Inst. Transactions<br />Credit Card Payments<br />ACH Payments<br />Fraud/Risk<br />Identity/ Enrollment<br />SAS<br />SAP<br />Corporate Billing<br />Web<br />IVR<br />Payments<br />Risk<br />Business Intelligence<br />Corporate Financials<br />Partner Communication<br />Bus Intel/ Reporting<br />
    53. 53. Biller Transactions<br />Fin Inst. Transactions<br />Credit Card Payments<br />ACH Payments<br />Fraud/Risk<br />Identity/ Enrollment<br />SAS<br />SAP<br />Corporate Billing<br />Web<br />IVR<br />Payments<br />Risk<br />Business Intelligence<br />Corporate Financials<br />Partner Communication<br />Bus Intel/ Reporting<br />
    54. 54. Biller Transactions<br />Fin Inst. Transactions<br />Credit Card Payments<br />ACH Payments<br />Fraud/Risk<br />Identity/ Enrollment<br />SAS<br />SAP<br />Corporate Billing<br />Web<br />IVR<br />Payments<br />Risk<br />Business Intelligence<br />Corporate Financials<br />Partner Communication<br />Bus Intel/ Reporting<br />
    55. 55. Biller Transactions<br />Fin Inst. Transactions<br />Credit Card Payments<br />ACH Payments<br />Fraud/Risk<br />Identity/ Enrollment<br />SAS<br />SAP<br />Corporate Billing<br />Web<br />IVR<br />Payments<br />Risk<br />Business Intelligence<br />Corporate Financials<br />Partner Communication<br />Bus Intel/ Reporting<br />
    56. 56. Biller Transactions<br />Fin Inst. Transactions<br />Credit Card Payments<br />ACH Payments<br />Fraud/Risk<br />Identity/ Enrollment<br />SAS<br />SAP<br />Corporate Billing<br />Web<br />IVR<br />Payments<br />Risk<br />Business Intelligence<br />Corporate Financials<br />Partner Communication<br />Bus Intel/ Reporting<br />
    57. 57. Biller Transactions<br />Fin Inst. Transactions<br />Credit Card Payments<br />ACH Payments<br />Fraud/Risk<br />Identity/ Enrollment<br />SAS<br />SAP<br />Corporate Billing<br />Web<br />IVR<br />Payments<br />Risk<br />Business Intelligence<br />Corporate Financials<br />Partner Communication<br />Bus Intel/ Reporting<br />
    58. 58. Managing the Enterprise Backlog<br />
    59. 59. Epic<br />Epic<br />Epic<br />Epic<br />
    60. 60. Feature<br />Epic<br />Feature<br />Feature<br />Feature<br />Epic<br />Feature<br />Epic<br />Feature<br />Epic<br />
    61. 61. Team 1<br />User Story<br />Feature<br />Epic<br />User Story<br />Feature<br />User Story<br />Team 2<br />Feature<br />User Story<br />Feature<br />Epic<br />User Story<br />User Story<br />Feature<br />Epic<br />User Story<br />Feature<br />Team 3<br />User Story<br />User Story<br />Epic<br />User Story<br />
    62. 62. The performance of one team can starve Value Creation<br />
    63. 63. Context<br />Team 2<br />Team 1<br />Team 3<br />
    64. 64. Context<br />Coordination<br />Team 2<br />Team 1<br />Team 3<br />
    65. 65. Manage the system, identify and elevate constraints<br />
    66. 66. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />
    67. 67. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 1<br />Feature 2<br />Feature 2<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 1<br />Feature 1<br />Feature 2<br />
    68. 68. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 1<br />Feature 2<br />Feature 2<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />
    69. 69. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 1<br />Feature 2<br />Feature 2<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 3<br />Feature 2<br />Feature 2<br />Feature 3<br />Feature 2<br />Feature 3<br />Feature 3<br />Feature 2<br />Feature 2<br />Feature 2<br />
    70. 70. Feature 1<br />Feature 1<br />Feature 1<br />3 months<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 3<br />Feature 3<br />Feature 3<br />
    71. 71. Feature 1<br />Feature 1<br />Feature 1<br />3 months<br />Feature 2<br />Feature 2<br />Feature 2<br />6 months<br />Feature 3<br />Feature 3<br />Feature 3<br />
    72. 72. Feature 1<br />Feature 1<br />Feature 1<br />3 months<br />Feature 2<br />Feature 2<br />Feature 2<br />6 months<br />Feature 3<br />Feature 3<br />9 months<br />Feature 3<br />
    73. 73. Feature 1<br />Feature 2<br />Feature 3<br />Feature 1<br />Feature 2<br />Feature 3<br />Feature 1<br />7 months<br />Feature 2<br />Feature 3<br />
    74. 74. Feature 1<br />Feature 2<br />Feature 3<br />Feature 1<br />Feature 2<br />Feature 3<br />Feature 1<br />7 months<br />Feature 2<br />10 months<br />Feature 3<br />
    75. 75. Feature 1<br />Feature 2<br />Feature 3<br />Feature 1<br />Feature 2<br />Feature 3<br />Feature 1<br />7 months<br />Feature 2<br />10 months<br />13 months<br />Feature 3<br />
    76. 76. Feature 1<br />Feature 2<br />Feature 3<br />Feature 1<br />Feature 2<br />Feature 3<br />Feature 1<br />7 months<br />Feature 2<br />10 months<br />13 months<br />Feature 3<br />
    77. 77. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />
    78. 78. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />
    79. 79. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />
    80. 80. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />
    81. 81. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />
    82. 82. Team 1<br />Team 2<br />Team 3<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 1<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 2<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />Feature 3<br />
    83. 83. Product Ownership in the Large<br />
    84. 84. Product Ownership is a set of organizational capabilities…<br />
    85. 85. …not a person!<br />
    86. 86. Team 1<br />Team<br />
    87. 87. Team 2<br />Team 1<br />
    88. 88. Team 2<br />Team 1<br />Team 3<br />Across Teams<br />
    89. 89. Project<br />Team 2<br />Team 1<br />Team 3<br />Project <br />A<br />
    90. 90. Portfolio<br />Team 2<br />Team 1<br />Team 3<br />Project <br />B<br />Project <br />A<br />
    91. 91. That get expressed differently depending on your level of scale<br />
    92. 92. Product Owner Capabilities<br />
    93. 93. Product Owner Capabilities<br />Agile as Business Analysis<br />
    94. 94. Product Owner Capabilities<br />Agile as Business Analysis<br />Agile as Engineering<br />
    95. 95. Product Owner Capabilities<br />Agile as Business Analysis<br />Agile as Engineering<br />Agile as Leadership & Coordination<br />
    96. 96. Business Analysis CapabilitiesHelping organizations develop the capabilities to achieve Enterprise Agility<br />Product Development<br />Product Strategy<br />Solution Requirements<br />Develop Product<br />Launch Product<br />Operate and Support Product<br />Understand Needs of the Customer <br />Establish Product Vision<br />Plan Launch <br />Establish Development Environment <br />Support Operations <br />Understand Requirements <br />Develop Product Strategy<br />Define Product Roadmap<br />Coordinate Launch <br />Provide Customer Support<br />Maintain Architecture <br />Integration Testing <br />Manage Product Portfolio <br />Define Business Requirements <br />Support Implementation <br />Coordinate Work <br />Achieve Customer Acceptance <br />Perform Maintenance and Customizations <br />Define Product Backlog <br />Design and Engineer Solution<br />Deploy Product <br />Environment <br />Planning <br />Manage Suppliers <br />Maintain Product Quality <br />Maintain Work Environment<br />Learn from Outside Sources<br />Develop Team<br />Commit To Agility<br />Everyone<br />Engage Stakeholders<br />Ensure Process Adherence<br />Identify and Remove Impediments<br />Ensure Internal Communication<br />Manage Risks <br />Provide Job Training<br />
    97. 97. Engineering CapabilitiesHelping organizations develop the capabilities to achieve Enterprise Agility<br />Product Development<br />Product Strategy<br />Solution Requirements<br />Develop Product<br />Launch Product<br />Operate and Support Product<br />Understand Needs of the Customer <br />Establish Product Vision<br />Plan Launch <br />Establish Development Environment <br />Support Operations <br />Understand Requirements <br />Develop Product Strategy<br />Define Product Roadmap<br />Coordinate Launch <br />Provide Customer Support<br />Maintain Architecture <br />Integration Testing <br />Manage Product Portfolio <br />Define Business Requirements <br />Support Implementation <br />Coordinate Work <br />Achieve Customer Acceptance <br />Perform Maintenance and Customizations <br />Define Product Backlog <br />Design and Engineer Solution<br />Deploy Product <br />Environment <br />Planning <br />Manage Suppliers <br />Maintain Product Quality <br />Maintain Work Environment<br />Learn from Outside Sources<br />Develop Team<br />Commit To Agility<br />Everyone<br />Engage Stakeholders<br />Ensure Process Adherence<br />Identify and Remove Impediments<br />Ensure Internal Communication<br />Manage Risks <br />Provide Job Training<br />
    98. 98. Leadership & Coordination CapabilitiesHelping organizations develop the capabilities to achieve Enterprise Agility<br />Product Development<br />Product Strategy<br />Solution Requirements<br />Develop Product<br />Launch Product<br />Operate and Support Product<br />Understand Needs of the Customer <br />Establish Product Vision<br />Plan Launch <br />Establish Development Environment <br />Support Operations <br />Understand Requirements <br />Develop Product Strategy<br />Define Product Roadmap<br />Coordinate Launch <br />Provide Customer Support<br />Maintain Architecture <br />Integration Testing <br />Manage Product Portfolio <br />Define Business Requirements <br />Support Implementation <br />Coordinate Work <br />Achieve Customer Acceptance <br />Perform Maintenance and Customizations <br />Define Product Backlog <br />Design and Engineer Solution<br />Deploy Product <br />Environment <br />Planning <br />Manage Suppliers <br />Maintain Product Quality <br />Maintain Work Environment<br />Learn from Outside Sources<br />Develop Team<br />Commit To Agility<br />Everyone<br />Engage Stakeholders<br />Ensure Process Adherence<br />Identify and Remove Impediments<br />Ensure Internal Communication<br />Manage Risks <br />Provide Job Training<br />
    99. 99. Team 1<br />
    100. 100. Team 2<br />Team 1<br />
    101. 101. Team 3<br />Team 2<br />Team 1<br />
    102. 102. Scrum of Scrums<br />Team 2<br />Team 1<br />Team 3<br />
    103. 103. Product Owner Team<br />Team 2<br />Team 1<br />Team 3<br />
    104. 104. Product Owner Team with<br />Architects<br />Team 2<br />Team 1<br />Team 3<br />
    105. 105. Integration Team<br />Team 2<br />Team 1<br />Team 3<br />
    106. 106. Alignment and culture trump people, process, and tools<br />
    107. 107. Summary<br />
    108. 108. Summary<br />Product Owners don’t scale<br />
    109. 109. Summary<br />Product Owners don’t scale<br />Common strategies don’t work<br />
    110. 110. Summary<br />Product Owners don’t scale<br />Common strategies don’t work<br />It takes more than one team to deliver value<br />
    111. 111. Summary<br />Product Owners don’t scale<br />Common strategies don’t work<br />It takes more than one team to deliver value<br />By thinking about organizational capabilities<br />
    112. 112. Summary<br />Product Owners don’t scale<br />Common strategies don’t work<br />It takes more than one team to deliver value<br />By thinking about organizational capabilities<br />We can create situationally specific strategies<br />
    113. 113. Mike CottmeyerEnterprise Agile Coachmike@cottmeyer.com404.312.1471leadingagile.comfacebook.com/leadingagiletwitter.com/mcottmeyerlinkedin.com/in/cottmeyer<br />
    114. 114. How to Own a Really Big Complex Product<br />Presented by: Mike Cottmeyer<br />

    ×