Bridging the Gap: Incorporate OpenSource In Product Managers Toolbox
summary
Argues product managers can quantify open source by adding concrete inputs to a make-or-buy Excel template, using PESTEL, SWOT, Kano and activity maps, sizing TAM over a 10‑year business case, and tracking upstream and compliance costs; gives concrete results: an RFQ to ~10 vendors cut one supplier’s price ~50%, reuse drove a measured ~30% cost reduction in projects, and license savings initially looked like up to 90% before accounting maintenance to end near 50%.
AI-written summary · about
chapters (14)
- 0:00Open source panel inspiration
- 2:13Open source benefits for PMs
- 4:42Open source risks and myths
- 7:11Automotive proprietary software issues
- 11:25Traditional automotive development
- 13:34PASTEL analysis for open source
- 17:52SWOT for open source integration
- 22:48CANU model for advantage
- 24:17Activity maps for open source
- 28:09Market size for open source
- 30:57Business case for open source
- 35:12Regulatory and compliance
- 38:23Open source compliance costs
- 40:30Final thoughts and Q&A
related talks
28mTalking with management about open source
37mTalking with management about open source
39mTalking with Management About Open Source
35mHow Can Your Organization Maximize Open Source Business Value?
35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..
40mHow Can Your OSPO Drive Open Source Business Value for Your Organization?
23mPutting a Price Tag on Open Source ROI in Enterprise Japan
01h 39mWorkshop: Building and Managing an Open Source Program Office