Open source software is fundamentally different from proprietary software. Often, different teams use and/or build open source differently. Because of this variability, it needs to be approached differently. Managing this strategy is the job of the OSPO (Open Source Program Office). But what is an OSPO? And how do you build one? The Rise of the Open Source Program Office discusses:

• Things to know when evaluating your need for an OSPO
• Areas managed by an OSPO
• Roles key to an OSPO's success
• The key pillars of a successful OSPO
• A list of resources to read if you want to build an OSPO

Managing your open source program is all about improving efficiency and decreasing risk. Determining factors such as which open source licenses are appropriate, whether or not your full-time employees should be contributing to a major open source project, and determining what components will best accelerate your products growth, quality, or security all have implications on both your product’s viability and competitiveness, how your internal resources are being used, and what the risk profile of your company. An OSPO helps to define your open source management strategy.