Motivating the contributions: An Open Innovation perspective on what to share as Open Source Software

Abstract Open Source Software (OSS) ecosystems have reshaped the ways how software-intensive firms develop products and deliver value to customers. However, firms still need support for strategic product planning in terms of what to develop internally and what to share as OSS. Existing models accurately capture commoditization in software business, but lack operational support to decide what contribution strategy to employ in terms of what and when to contribute. This study proposes a Contribution Acceptance Process (CAP) model from which firms can adopt contribution strategies that align with product strategies and planning. In a design science influenced case study executed at Sony Mobile, the CAP model was iteratively developed in close collaboration with the firm’s practitioners. The CAP model helps classify artifacts according to business impact and control complexity so firms may estimate and plan whether an artifact should be contributed or not. Further, an information meta-model is proposed that helps operationalize the CAP model at the organization. The CAP model provides an operational OI perspective on what firms involved in OSS ecosystems should share, by helping them motivate contributions through the creation of contribution strategies. The goal is to help maximize return on investment and sustain needed influence in OSS ecosystems.

[1]  Madeleine Järsjö,et al.  Purchasing Must Become Supply Management , 2013 .

[2]  Claes Wohlin,et al.  Software component decision-making: In-house, OSS, COTS or outsourcing - A systematic literature review , 2016, J. Syst. Softw..

[3]  Alan R. Hevner,et al.  Design Science in Information Systems Research , 2004, MIS Q..

[4]  Richard Kemp Open source software (OSS) governance in the organisation , 2010, Comput. Law Secur. Rev..

[5]  Jan Bosch,et al.  Achieving Simplicity with the Three-Layer Product Model , 2013, Computer.

[6]  Mats Magnusson,et al.  How do firms make use of open source communities , 2008 .

[7]  Joel West,et al.  How open is open enough?: Melding proprietary and open source platform strategies , 2003 .

[8]  Daniela E. Damian,et al.  Stakeholders in Global Requirements Engineering: Lessons Learned from Practice , 2007, IEEE Software.

[9]  A. Salter,et al.  Open for innovation: the role of openness in explaining innovation performance among U.K. manufacturing firms , 2006 .

[10]  Tony Gorschek,et al.  A Model for Technology Transfer in Practice , 2006, IEEE Software.

[11]  Björn Lundell,et al.  Commodification of Industrial Software: A Case for Open Source , 2009, IEEE Software.

[12]  Walt Scacchi,et al.  Understanding the requirements for developing open source software systems , 2002, IEE Proc. Softw..

[13]  Marjo Kauppinen,et al.  Roadmapping problems in practice: value creation from the perspective of the customers , 2013, Requirements Engineering.

[14]  Per Runeson,et al.  A Survey on the Perception of Innovation in a Large Product-Focused Software Organization , 2015, ICSOB.

[15]  Henry Chesbrough,et al.  Open Innovation: The New Imperative for Creating and Profiting from Technology , 2003 .

[16]  Manfred Broy,et al.  A meta model for artefact-orientation: fundamentals and lessons learned in requirements engineering , 2010, MODELS'10.

[17]  Sebastian Spaeth,et al.  Extending Private-Collective Innovation: A Case Study , 2009 .

[18]  Joachim Henkel,et al.  The Emergence of Openness: How and Why Firms Adopt Selective Revealing in Open Innovation , 2013 .

[19]  J. Henkel Selective revealing in open innovation processes: the case of embedded Linux (gekürzte Version) , 2006 .

[20]  Francisco José García-Peñalvo,et al.  Preface of Open Source Solutions for Knowledge Management and Technological Ecosystems , 2016 .

[21]  Linus Dahlander,et al.  Relationships Between Open Source Software Companies and Communities: Observations from Nordic Firms , 2005 .

[22]  Kouichi Kishida,et al.  Evolution patterns of open-source software systems and communities , 2002, IWPSE '02.

[23]  Per Runeson,et al.  Open innovation using open source tools: a case study at Sony Mobile , 2017, Empirical Software Engineering.

[24]  Björn Regnell,et al.  Requirements engineering challenges in market-driven software development - An interview study with practitioners , 2007, Inf. Softw. Technol..

[25]  Joachim Henkel,et al.  Champions of Revealing - the Role of Open Source Developers in Commercial Firms , 2008 .

[26]  H. Chesbrough,et al.  A Fad or a Phenomenon?: The Adoption of Open Innovation Practices in Large Firms , 2014 .

[27]  J. West,et al.  Challenges of Open Innovation: The Paradox of Firm Investment in Open-Source Software , 2006 .

[28]  Walt Scacchi,et al.  Ongoing software development without classical requirements , 2013, 2013 21st IEEE International Requirements Engineering Conference (RE).

[29]  B. Flyvbjerg Five Misunderstandings About Case-Study Research , 2006, 1304.1186.

[30]  Slinger Jansen,et al.  A Framework for Software Ecosystem Governance , 2012, ICSOB.

[31]  Klaus Marius Hansen,et al.  Software ecosystems - A systematic literature review , 2013, J. Syst. Softw..

[32]  Slinger Jansen,et al.  Shades of gray: Opening up a software producing organization with the open software enterprise model , 2012, J. Syst. Softw..

[33]  Stefan Wagner,et al.  Field study on requirements engineering: Investigation of artefacts, project parameters, and execution strategies , 2012, Inf. Softw. Technol..

[34]  Youngdae Lee,et al.  Voice over LTE (VoLTE) , 2012 .

[35]  Dietmar Pfahl,et al.  How can open source software development help requirements management gain the potential of open innovation: An exploratory study , 2012, Proceedings of the 2012 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement.

[36]  W. Stam When Does Community Participation Enhance the Performance of Open Source Software Companies? , 2008 .

[37]  H. Chesbrough,et al.  Open Innovation and Strategy , 2007 .

[38]  O. Gassmann,et al.  Open R&D and Open Innovation: Exploring the Phenomenon , 2009 .

[39]  Björn Regnell,et al.  Scaling Up Requirements Engineering - Exploring the Challenges of Increasing Size and Complexity in Market-Driven Software Development , 2011, REFSQ.

[40]  Claes Wohlin,et al.  A Value-Based Approach in Requirements Engineering: Explaining Some of the Fundamental Concepts , 2007, REFSQ.

[41]  Tony Gorschek,et al.  The software value map — an exhaustive collection of value aspects for the development of software intensive products , 2013, J. Softw. Evol. Process..

[42]  H. Kittlaus,et al.  Software Product Management and Pricing: Key Success Factors for Software Organizations , 2009 .

[43]  Bashar Shaya,et al.  Process handling : A study for optimizing the processes for sourcing IT and managing software licenses , 2012 .

[44]  Per Runeson,et al.  Open innovation in software engineering: a systematic mapping study , 2015, Empirical Software Engineering.

[45]  Björn Regnell,et al.  Market-Driven Requirements Engineering for Software Products , 2005 .

[46]  Pär J. Ågerfalk,et al.  Outsourcing to an Unknown Workforce: Exploring Opensourcing as a Global Sourcing Strategy , 2008, MIS Q..

[47]  Marjolein C. J. Caniëls,et al.  Purchasing strategies in the Kraljic matrix—A power and dependence perspective , 2005 .

[48]  Kris Ven,et al.  Challenges and strategies in the use of Open Source Software by Independent Software Vendors , 2008, Inf. Softw. Technol..

[49]  W. Vanhaverbeke,et al.  When Research Meets Development : Antecedents and Implications of Transfer Speed , 2014 .

[50]  Cees J. Gelderman,et al.  Handling measurement issues and strategic directions in Kraljic's purchasing portfolio model , 2003 .

[51]  Inge van de Weerd,et al.  A Framework for Process Improvement in Software Product Management , 2010, EuroSPI.

[52]  Slinger Jansen,et al.  Business Network Management as a Survival Strategy: A Tale of Two Software Ecosystems , 2009, IWSECO@ICSR.

[53]  Klaus Pohl,et al.  Software Product Line Engineering - Foundations, Principles, and Techniques , 2005 .

[54]  Christof Ebert,et al.  Software Product Management , 2014, IEEE Software.

[55]  Andrey Maglyas,et al.  The Preliminary Results from the Software Product Management State-of-Practice Survey , 2014, ICSOB.

[56]  J. West,et al.  Leveraging External Sources of Innovation: A Review of Research on Open Innovation , 2013 .

[57]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[58]  Pauliina Ulkuniemi,et al.  Purchasing as market-shaping: The case of component-based software engineering , 2015 .

[59]  Neil A. Ernst,et al.  Case studies in just-in-time requirements analysis , 2012, 2012 Second IEEE International Workshop on Empirical Requirements Engineering (EmpiRE).

[60]  Slinger Jansen,et al.  A sense of community: A research agenda for software ecosystems , 2009, 2009 31st International Conference on Software Engineering - Companion Volume.

[61]  Austen Rainer,et al.  Case Study Research in Software Engineering - Guidelines and Examples , 2012 .

[62]  Paul Oude Luttighuis,et al.  Sourcing Requirements and Designs for Software as a Service , 2016, Int. J. Syst. Serv. Oriented Eng..