The Lie of the Benevolent Dictator - Randy Bias, CEO, CloudScaling - OpenStackSV 2014
•Download as PPTX, PDF•
1 like•3,925 views
The document discusses the need for product leadership in OpenStack. Currently, OpenStack lacks a clear strategic product vision and direction. While it has governance structures like a Board and Technical Committee, no single entity is responsible for the overall product strategy. The document suggests establishing an Architecture Review Board and appointing Product Managers to fill this gap. The Board would provide architectural guidance and help prioritize work, while Product Managers would own setting priorities and negotiating requirements across stakeholders. This would give OpenStack stronger leadership without requiring a "dictator," maintaining its democratic meritocracy approach.
Report
Share
The Lie of the Benevolent Dictator - Randy Bias, CEO, CloudScaling - OpenStackSV 2014
- 1. The Lie of The Benevolent Dictator The Truth of a Democratic Meritocracy Randy Bias, CEO openstacksv.com SEPTEMBER 2014
- 2. Do we need a benevolent dictator? SEPTEMBER 2014
- 3. OpenStack *has* a leadership, or at least governance/ management structure SEPTEMBER 2014
- 4. Strategic Business Direction Tactical Software Dev Life Cycle Board Plat. Gold Ind. PTLs Ind. Foundation TC Developer Community ED Rel Mgr Ind. Corp. Subcommittees • legal • finance • DefCore • etc. User Committee • nascent • user survey RM SEPTEMBER 2014 volunteer elected appointed hired
- 5. But is it the right kind of leadership? SEPTEMBER 2014
- 6. Does OpenStack have a vision and product strategy? NO! SEPTEMBER 2014
- 7. The Gap Strategic Business Direction Tactical Software Dev Life Cycle Strategic Product Vision & Direction? Board TC No one owns!! SEPTEMBER 2014
- 8. “product strategy” for open source project(s) ? SEPTEMBER 2014
- 9. Product strategy and vision will not “emerge” from a group SEPTEMBER 2014
- 10. SEPTEMBER 2014
- 11. We are a democratic meritocracy We are not the Linux community We don’t need a dictator, but we do need product leadership SEPTEMBER 2014
- 12. Some Product Leadership Requirements not a complete list, OK? SEPTEMBER 2014
- 13. Some Product Leadership Requirements • OpenStack is NOT a Product, BUT … It Must Be Managed Like One • Long term vision + long term prioritization & planning • Corporate independence • Work for the community: developers, operators, and end-users • Focus on end-user needs and requirements • Working with the user committee, obviously… • Ability to work closely with the Board and the TC • Priority setting, vision, etc. • Architectural oversight and leadership SEPTEMBER 2014
- 14. What does AWS do? SEPTEMBER 2014
- 15. What does Amazon do for product leadership? • Small architecture review board • Werner Vogels, James Hamilton, etc. • Product management function • Team of product managers per product line SEPTEMBER 2014
- 16. What *might* we do? SEPTEMBER 2014
- 17. What could we do? (Just a SUGGESTION) • Arch Review Board (ARB) • Elected for 2-4 years • Small # of seats • Wide set of domain expertise • Remit is: • work with TC on BP/Specs • help PMs validate priority • Product Management (PM) • Not elected • 1+ per program • Specific domain expertise • Work for the Foundation • Annual 360° feedback • Remit is: • priority setting & negotiation SEPTEMBER 2014
- 18. Board TC Plat. Gold Ind. PTLs Ind. Prod. Mgrs Foundation Developer Community ED Rel Mgr Ind. Corp. Subcommittees • legal • finance • DefCore • etc. User Committee • nascent • user survey Strategic Business Direction Tactical Software Dev Life Cycle ARB • Shared chair? • Elected PTL seat? • Independents • Long term Architects SEPTEMBER 2014 volunteer elected appointed hired
- 19. Product leadership the issue; NOT dictatorship Product leadership cannot be emergent Many paths forward; *all* require creating ownership Collective responsibility to fix this Failure to fix may result in insurmountable challenges SEPTEMBER 2014
- 20. Thank you @randybias SEPTEMBER 2014