Justifying an OSPO in Dollars and Cents
summary
Shows concrete wins: a new contribution policy drives a 40 point NPS increase that is estimated to avoid about $2M in hiring and retraining costs by retaining six to eight engineers; an open source funnel yields that 90% of paid contracts begin with an OSS evaluation and assigns an approximate $50 implied value per GitHub download; community goodwill alone produced an $8.2M acquisition outcome. Tools and metrics tracked: downloads, forks, stars, issue retention and conversion.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:18Value provided by the OSPO
- 1:36Driving business value
- 2:21Disclaimers
- 3:24Why do people get into open source
- 4:44How do OSPOs create value
- 5:29How many people remember Open Office
- 7:05Open Office has become irreversible
- 8:24Hudson
- 10:00Elastic Search
- 10:46Retention
- 11:26Value
- 11:59Compliance
- 12:50Employee Retention
- 15:45Cost of Retraining
- 17:00OSPO is part of your funnel
- 20:07The selection effect
- 21:20Goodwill
- 23:54Metrics
- 24:21Functional Areas
- 25:11Compliance and Opportunities
- 25:57Takeaways
related talks
34mJustifying an OSPO in Dollars and Cents
22mThe OSPO Playbook: Supercharging Open Source at Scale
40mHow Can Your OSPO Drive Open Source Business Value for Your Organization?
32mOSPOs: Key Lever for Open Source Sustainability
41mHow Your Company Can Help Sustain Open Source
40mEngagement of Open Source Communities – A Deep-dive Into EPAM’s OSPO
24mAchieving the Tipping Point for Open-source Software: Making the Business Value Obvi...
39mHow Can Your OSPO Maximize Open Source Business Value for the Organization?