Contenu connexe Similaire à Success Factors of FOSS Adoption Similaire à Success Factors of FOSS Adoption (20) 1. Success Factors for
Open Source Adoption
Claus von Riegen
Program Director Industry Standards and Open Source
SAP AG
Andrew Aitken
GM & SVP, Olliance Group
A Black Duck Software company
2. Copyright © 2011 Black Duck Software, Inc. All Rights Reserved. 2
Open Source and Innovation
Andrew Aitken
GM & SVP, Olliance Group,
A Black Duck Software company
Open Source Strategy: Our Experience, Your Success
– The industry’s leading open source
business consultancy
– Over 600 engagements to date
– A Trusted Advisor to leading Fortune
2000 companies
3. Copyright © 2011 Black Duck Software, Inc. All Rights Reserved.
Open Source and Innovation
Open Source
developing, licensing, distributing and
consuming software
Open Source Drivers
collaboration, transparency, meritocracy
and licensing model
Open Source Innovation
The collaborative and transparent
creation or improvement of products,
technologies or ideas.
4. Copyright © 2011 Black Duck Software, Inc. All Rights Reserved. 4
Innovation By Industry
5. Copyright © 2011 Black Duck Software, Inc. All Rights Reserved. 5
Today’s Speaker
Claus von Riegen
Program Director Industry Standards and Open Source
SAP AG
6. Claus von Riegen, Vice President Industry Standards and Open Source
SAP AG
February 14th, 2012
Success Factors for Open Source Adoption
7. © 2012 SAP AG. All rights reserved. 7
Innovation Can Come From Anywhere
INNOVATION SAP Employees
Academic PartnersCustomers
Industry Partners
Research Labs
Development Labs
SAP Innovation Programs
8. © 2012 SAP AG. All rights reserved. 8
SAP and Open Source
100s
Open Source
Usages
>50
Open Source
Contributions
9. © 2012 SAP AG. All rights reserved. 9
What Our Customers Say
“NetWeaver's support for common standards and Open
Source is very important to Siemens because it helps to
protect investments, reduce costs, and increase flexibility
for both ourselves and our customers. For example, due to
SAP's usage of technologies like Eclipse as well as SAP’s
support for SOA standards, users of the Siemens Energy
Management Suite can reuse their existing Java EE, SOA
and Eclipse skills.”
Jens Neuhaus
Solution Architect, Siemens AG
10. © 2012 SAP AG. All rights reserved. 10
Why It Is Not A Good Idea Trying To Prevent Open Source
11. © 2012 SAP AG. All rights reserved. 11
But You Better Know What You Are Doing
Customer expectations
Functional scope
Usability
Quality
Reliability
Security
… and more
Open source quality
Software is not necessarily good just
because it is open source!
Like with any third-party product, all usage of open source software should
be managed
12. © 2012 SAP AG. All rights reserved. 12
And now?
What are the success
factors of open source
adoption?
13. © 2012 SAP AG. All rights reserved. 13
Three Stages Of Open Source Adoption In The Enterprise
Select
Functional /
non-functional fit
Future-proof
License
Manage
Reuse
Security
Maintenance /
Support
Engage
Roadmap
Investment
protection
Standardization
14. © 2012 SAP AG. All rights reserved. 14
Open Source Selection Criteria
Software
Fit with functional and non-functional requirements
Fit with product architecture / product strategy
License
Freedoms / constraints and obligations
Community
Contributors, users, and service providers
Usage Scenario
Product that make use of the open source software
Type of integration (embedded, linked, etc.)
Modification / enhancement / contribution
requirements
Software distribution channel
Community
License
Software
Usage Scenario
15. © 2012 SAP AG. All rights reserved. 15
Legal Risks
16. © 2012 SAP AG. All rights reserved. 16
Open Source Licenses 101
Proprietary licensesPermissive licenses “Copyleft” licenses
Apache
MIT
BSD
Eclipse
Mozilla
Affero
GPL
LGPL GPL Commercial license
Open source license constraints need to be understood in the context of
deployment model, integration scenario and need for adaptation/modification
Less freedom
17. © 2012 SAP AG. All rights reserved. 17
Open Source is NOT for free
18. © 2012 SAP AG. All rights reserved. 18
Best Practices For Open Source Selection
Define
Establish corporate open source policy1
Know
Obtain information about available open source software
Check maturity – select robust and well-adopted open source technologies
Build or buy legal practice for open source licensing
Govern
Define and run open source governance process
Establish cost/benefit metrics
Include relevant stakeholders (product units, CTO office, legal/IP teams, etc.)
Inform & Educate
Train product owners / architects about need for balanced due diligence
Inform decision makers about their role in governance process
Capture corporate intelligence (what – where – why)
1 See, for example, A Practical Guide to Leveraging Open Source in Business, Heather J. Meeker, John Wiley & Sons, 2008
19. © 2012 SAP AG. All rights reserved. 19
Open Source Management – Key Challenges
Security
How do we find and manage security
vulnerabilities that may exist?
Long-Term Support
How can we ensure dedicated long-term
support ?
7
Release Plans
How can we align release strategies and plans between
open source technologies and own products?
Reuse
How can we avoid the proliferation of different
technologies for the same requirement?
2
SAP
Customer
20. © 2012 SAP AG. All rights reserved. 20
Synchronisation
of release plans can be
challenging
22. © 2012 SAP AG. All rights reserved. 22
SAP products are supported
for at least 9 years
23. © 2012 SAP AG. All rights reserved. 23
Best Practices For Open Source
Management
Reuse
Establish corporate open source standards
Security
Apply same scrutiny for open source products as for in-house development
Monitor open source project for available patches
In case vulnerabilities are detected
Fix immediately
Provide patch for own customers
Contribute solution to open source project
Support
Option 1: open source product is very mature – no dedicated support needed
Option 2: develop skills internally
Option 3: establish maintenance activity as part of open source community
Option 4: procure third-party support services
24. © 2012 SAP AG. All rights reserved. 24
Reasons For Community Engagement
Contribute to existing open source projects
New requirements
Bug fixes
Enhancements / extensions
Initiate new open source projects
Depends on business goals
Scenarios Benefits
Influence future direction
Increase productivity
Share cost of development
Solicit early feedback
Motivate external contributions
Create industry standards
25. © 2012 SAP AG. All rights reserved. 25
Sometimes pulling in
different directions
27. © 2012 SAP AG. All rights reserved. 27
Best Practices For Open Source
Engagement
Beginners
Identify non-critical project and try it out
Intermediates
Understand how open source projects work
Don’t underestimate soft skills (negotiation, consensus-building, patience, etc.)
Gradually increase commitment
Regularly check cost/benefit equation
Professionals
Appoint contribution manager per project
One voice
Scope of contribution
Interactions with legal / intellectual property team
28. © 2012 SAP AG. All rights reserved. 28
Summary
Open Source Has Distinct Benefits
It is there – and growing
Utilize external innovation
Increased productivity
Short time-to-value
Reuse of skills
Open Source Needs To Be Managed
Quality
License
Direction
Participate!
Start small & build an open source practice
30. Copyright © 2011 Black Duck Software, Inc. All Rights Reserved. 30
Questions?
31. Copyright © 2011 Black Duck Software, Inc. All Rights Reserved. 31
The Industry’s Most Unique Event: Now in its 7th year
– Invitation-only
– Global participation
– Real-world case study format
GENIVI
U.S. Department of Veterans Affaires
Spring April 12th – 14th, 2012, Napa, CA
– Theme: Industry-Driven Community Innovation
Fall, Oct 2012, Paris, France
http://thinktank.olliancegroup.com
