success factors of foss adoption

Download Success Factors of FOSS Adoption

Post on 05-Dec-2014

250 views

Category:

Technology

6 download

Embed Size (px)

DESCRIPTION

 

TRANSCRIPT

  • 1. Success Factors forOpen Source AdoptionClaus von RiegenProgram Director Industry Standards and Open SourceSAP AGAndrew AitkenGM & SVP, Olliance GroupA Black Duck Software company
  • 2. Copyright 2011 Black Duck Software, Inc. All Rights Reserved. 2Open Source and InnovationAndrew AitkenGM & SVP, Olliance Group,A Black Duck Software companyOpen Source Strategy: Our Experience, Your Success The industrys leading open sourcebusiness consultancy Over 600 engagements to date A Trusted Advisor to leading Fortune2000 companies
  • 3. Copyright 2011 Black Duck Software, Inc. All Rights Reserved.Open Source and InnovationOpen Sourcedeveloping, licensing, distributing andconsuming softwareOpen Source Driverscollaboration, transparency, meritocracyand licensing modelOpen Source InnovationThe collaborative and transparentcreation or improvement of products,technologies or ideas.
  • 4. Copyright 2011 Black Duck Software, Inc. All Rights Reserved. 4Innovation By Industry
  • 5. Copyright 2011 Black Duck Software, Inc. All Rights Reserved. 5Todays SpeakerClaus von RiegenProgram Director Industry Standards and Open SourceSAP AG
  • 6. Claus von Riegen, Vice President Industry Standards and Open SourceSAP AGFebruary 14th, 2012Success Factors for Open Source Adoption
  • 7. 2012 SAP AG. All rights reserved. 7Innovation Can Come From AnywhereINNOVATION SAP EmployeesAcademic PartnersCustomersIndustry PartnersResearch LabsDevelopment LabsSAP Innovation Programs
  • 8. 2012 SAP AG. All rights reserved. 8SAP and Open Source100sOpen SourceUsages>50Open SourceContributions
  • 9. 2012 SAP AG. All rights reserved. 9What Our Customers SayNetWeavers support for common standards and OpenSource is very important to Siemens because it helps toprotect investments, reduce costs, and increase flexibilityfor both ourselves and our customers. For example, due toSAPs usage of technologies like Eclipse as well as SAPssupport for SOA standards, users of the Siemens EnergyManagement Suite can reuse their existing Java EE, SOAand Eclipse skills.Jens NeuhausSolution Architect, Siemens AG
  • 10. 2012 SAP AG. All rights reserved. 10Why It Is Not A Good Idea Trying To Prevent Open Source
  • 11. 2012 SAP AG. All rights reserved. 11But You Better Know What You Are DoingCustomer expectationsFunctional scopeUsabilityQualityReliabilitySecurity and moreOpen source qualitySoftware is not necessarily good justbecause it is open source!Like with any third-party product, all usage of open source software shouldbe managed
  • 12. 2012 SAP AG. All rights reserved. 12And now?What are the successfactors of open sourceadoption?
  • 13. 2012 SAP AG. All rights reserved. 13Three Stages Of Open Source Adoption In The EnterpriseSelectFunctional /non-functional fitFuture-proofLicenseManageReuseSecurityMaintenance /SupportEngageRoadmapInvestmentprotectionStandardization
  • 14. 2012 SAP AG. All rights reserved. 14Open Source Selection CriteriaSoftwareFit with functional and non-functional requirementsFit with product architecture / product strategyLicenseFreedoms / constraints and obligationsCommunityContributors, users, and service providersUsage ScenarioProduct that make use of the open source softwareType of integration (embedded, linked, etc.)Modification / enhancement / contributionrequirementsSoftware distribution channelCommunityLicenseSoftwareUsage Scenario
  • 15. 2012 SAP AG. All rights reserved. 15Legal Risks
  • 16. 2012 SAP AG. All rights reserved. 16Open Source Licenses 101Proprietary licensesPermissive licenses Copyleft licensesApacheMITBSDEclipseMozillaAfferoGPLLGPL GPL Commercial licenseOpen source license constraints need to be understood in the context ofdeployment model, integration scenario and need for adaptation/modificationLess freedom
  • 17. 2012 SAP AG. All rights reserved. 17Open Source is NOT for free
  • 18. 2012 SAP AG. All rights reserved. 18Best Practices For Open Source SelectionDefineEstablish corporate open source policy1KnowObtain information about available open source softwareCheck maturity select robust and well-adopted open source technologiesBuild or buy legal practice for open source licensingGovernDefine and run open source governance processEstablish cost/benefit metricsInclude relevant stakeholders (product units, CTO office, legal/IP teams, etc.)Inform & EducateTrain product owners / architects about need for balanced due diligenceInform decision makers about their role in governance processCapture 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. 19Open Source Management Key ChallengesSecurityHow do we find and manage securityvulnerabilities that may exist?Long-Term SupportHow can we ensure dedicated long-termsupport ?7Release PlansHow can we align release strategies and plans betweenopen source technologies and own products?ReuseHow can we avoid the proliferation of differenttechnologies for the same requirement?2SAPCustomer
  • 20. 2012 SAP AG. All rights reserved. 20Synchronisationof release plans can bechallenging
  • 21. QualityGlobalizationSecurity...Product Standards
  • 22. 2012 SAP AG. All rights reserved. 22SAP products are supportedfor at least 9 years
  • 23. 2012 SAP AG. All rights reserved. 23Best Practices For Open SourceManagementReuseEstablish corporate open source standardsSecurityApply same scrutiny for open source products as for in-house developmentMonitor open source project for available patchesIn case vulnerabilities are detected Fix immediately Provide patch for own customers Contribute solution to open source projectSupportOption 1: open source product is very mature no dedicated support neededOption 2: develop skills internallyOption 3: establish maintenance activity as part of open source communityOption 4: procure third-party support services
  • 24. 2012 SAP AG. All rights reserved. 24Reasons For Community EngagementContribute to existing open source projects New requirements Bug fixes Enhancements / extensionsInitiate new open source projects Depends on business goalsScenarios BenefitsInfluence future directionIncrease productivityShare cost of developmentSolicit early feedbackMotivate external contributionsCreate industry standards
  • 25. 2012 SAP AG. All rights reserved. 25Sometimes pulling indifferent directions

Recommended

View more >