ISPOs and OSPOs - differences and similarities
summary
Defines an InnerSource Program Office as a designated center of competency for InnerSource analogous to an OSPO, based on interviews with the ISPO Working Group and ongoing research; typical teams run 2–4 people and combine program managers, engineers, comms and advocates; core activities are organizational engagement and removing blockers, practitioner-facing curriculum and community management, hands‑on project support, and building tools such as developer portals and discoverability, metrics and compliance automation; ISPOs appear when executive support exists to scale InnerSource and activities evolve over the program life cycle.
AI-written summary · about
chapters (6)
- 0:00Introduction to ISO and OSPO
- 4:16What is an Inner Source Program Office
- 7:24Roles and teams in an ISO
- 9:32Key activities of an Inner Source Program Office
- 14:25Comparing ISO with OSPO
- 18:16Q&A and research opportunities
related talks
50mThe Parallel Universes of ISPOs an...- 50mPanel Discussion: The Parallel Universes of ISPOs and OSPOs
45mInnerSource and OSPOs: Institutionalizing Open Source Culture Change
26mOpen Source Program Offices
30mDemystifying OSPOs
14mMisconceptions about ways of working: How can OSPO/ISPO help?
30mApproaching OSPO: Steward or Damper?
42mYour Open Source Program Office, Your Program Management Organization, And You