Creating an organized comprehensive open source software strategy and policy can potentially lead to more use of open source software and delivery of several benefits.
Your Challenge
- An ineffective open source software strategy can be characterized by either an overly cautious approach that fails to take advantage of open source solutions or an overly loose approach that fails to take into account legal, technical, and business risks.
- Failure to understand open source contractual obligations may be unwittingly exposing your company to risk. Failure to take steps to adequately support your open source software can expose your company to business and technical risk.
- Failing to further embrace open source software may lead to a loss of competitive advantage and/or a disengaged development team.
Our Solution
Step 1. Project rationale for revising OSS strategy.
Step 2. Launch the OSS revision project.
Step 3. Assess current state of OSS in your organization (policies, processes, and software inventory).
Step 4. Create/prioritize OSS issue/risk mitigation initiatives.
Step 5. Define target state for OSS policies and processes.
Step 6. Identify and prioritize policy/process initiatives.
Step 7: Document and communicate the road map of initiatives to mitigate risk and revise policies and processes.
Talk to our analyst about this research
This research isn't live yet, but if you would like to speak to someone about this topic early, we're happy to connect you with an analyst.
Book an Analyst CallIf you are a media professional who would like to cover this research upon its release, please contact pr@infotech.com.