Open Source Program Office Case Study Guidelines

Edit this guide on GitHub

The TODO OSPO Case Study initiative features real-world use cases and the impact OSPO Programs and open source are having on an organization. OSPO Use Cases build narratives around open source organization’s journey that includes Open Source Program Office highlighted activities, organizational structure, best practices, goals, and success stories, showcasing rganizations as leaders in the OSPO and open source management ecosystem.

Requirements

Who can be featured in an OSPO Case Study?

As a rule, OSPO case studies feature:

  • Private and public organizations running an OSPO or an open source initiative
  • TODO Members

All case studies must demonstrate at least one tangible business impact of OSPOs or open source management within the organization and/or the open source ecosystem. Examples from published case studies include:

  • Compliance, legal, and developer education
  • Evangelizing Open Source Culture and Usage
  • Hosting Open Source Projects
  • Growing Open Source Communities
  • Improving leadership and becoming a decision-making partner
  • OSPO or Open Source management Best practices (e.g tooling, documentation, etc)

OSPO Case Study Process

OSPO case studies follow a self-service model with editorial support and guidance provided by TODO Group and the Linux Foundation.

The self-service follows a five-step process:

1. Proposal

Organizations submit a case study proposal via a Github Issue form

IMPORTANT: This form is still in work in progress. Meanwhile, interested participants, please open an issue using the ‘use case’ tag providing a description.

2. Review

  • TODO steering committee team reviews proposal within 30 working days
  • If the proposal meets the criteria, the TODO PM sends a case study pack to the contact info provided
  • If the proposal doesn’t meet the criteria, TODO Program Manager will provide feedback and the organization is invited to resubmit.

3. Creation

Primary contact writes a case study following the required style documented in the case study pack

4. Editing

  • TODO Group reviews the case study and makes any necessary edits as suggestions
  • Edits are based on the style guide.
  • Primary contact is welcome to make further edits or additions to the case study
  • Primary contact confirms when the draft is final and manages any approval processes

5. Publishing

  • TODO and LF prepare the case study for publication
  • Primary Contact will receive a preview link, to view the case study before it goes live.
  • Case Study is published to todogroup.org and OSPO guide
  • Promotion cycle begins

6. Promotion

  • Case studies are published on todogorup.org. TODO Group and LF market the case studies online, through social media, blog promotion, and the TODO OSPO newsletter.

To get started

Propose a case study and send it to the team directly by opening a issue using the use case tag

If you have any questions or feedback about the OSPO Case Study initiative, please send an email to info@todogroup.io.

These resources were created in partnership with the TODO Group: the professional open source program networking group at The Linux Foundation. A special thank you to Pam Baker for writing assistance and the open source program managers who contributed their time and knowledge to making these comprehensive guides. Participating companies include Autodesk, Comcast, Dropbox, Facebook, Google, Intel, Microsoft, Netflix, Oath (Yahoo + AOL), Red Hat, Salesforce, Samsung and VMware. To learn more, visit: todogroup.org.