How can open source software development help requirements management gain the potential of open innovation

Wnuk, Krzysztof; Pfahl, Dietmar; Callele, David; Karlsson, Even-André

doi:10.1145/2372251.2372301

Cited by 28 publications

(80 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The fear that the community was moving in another direction, rendering in a costly need of patch-sets and possible risk of an internal fork, was one reason for giving the plug-in to the community (Ven and Mannaert 2008). Wnuk et al (2012) reason in a similar manner in their study where they differentiate between contributing early or late to the community in regards to specific features. By going with the former strategy, one may risk losing the competitive edge, however the latter creates potentially high maintenance costs.…”

Section: Determinants Of Opennessmentioning

confidence: 93%

“…For example, by correcting bugs, actively participating in discussions and contributing new features, a software organization might reduce maintenance cost compared to proprietary software development (Stuermer et al 2009). Hence, in order for a firm to gain the expected benefits of products, OI process innovations may be a required step on the way forward (Lakhani and von Hippel 2003;Wnuk et al 2012;Rolandsson et al 2011). Existing literature does not particularly focus on how these internal SE process adaptions should be structured or executed (Munir et al 2016).…”

Section: Explains the Term Open Innovation (Oi) As "A Paradigm That Amentioning

confidence: 99%

“…Related to that is the challenge of what requirements should be selected, when these should be released and how an internal roadmap should be synchronized with the OSS project's roadmap (Wnuk et al 2012;Linåker et al 2016). These challenges highlight the need for a clear contribution strategy that software organizations should create to focus their internal resources on value-creating activities, rather than contributing unnecessary patches or differentiating features (Wnuk et al 2012).…”

Section: Related Workmentioning

confidence: 99%

“…We cannot afford to re-work everything". Due to these reasons, the Tools department is keen on not keeping stuff for themselves, but contributing everything (Ven and Mannaert 2008;Wnuk et al 2012). An issue in Jenkins is that there exist numerous combinations and settings of plug-ins.…”

Section: When Developers Upload a Change Which Can Have Several Revmentioning

confidence: 99%

“…Although the adoption of Jenkins and Gerrit came along with an adaption to the Android development, it was also driven bottom-up by the engineers since they felt the need for easing off the complex integration tool chain and building process as mentioned by Wnuk et al (2012). As described in Section 5.1, this process was not free of hurdles, one being the cultural and managerial aspect of giving away internally developed intellectual property (Huesig and Kohn 2011).…”

Section: Opening Upmentioning

confidence: 99%

See 4 more Smart Citations

Open innovation using open source tools: a case study at Sony Mobile

et al. 2017

Self Cite

View full text Add to dashboard Cite

Despite growing interest of Open Innovation (OI) in Software Engineering (SE), little is known about what triggers software organizations to adopt it and how this affects SE practices. OI can be realized in numerous of ways, including Open Source Software (OSS) involvement. Outcomes from OI are not restricted to product innovation but also include process innovation, e.g. improved SE practices and methods. This study explores the involvement of a software organization (Sony Mobile) in OSS communities from an OI perspective and what SE practices (requirements engineering and testing) have been adapted in relation to OI. It also highlights the innovative outcomes resulting from OI. An exploratory embedded case study investigates how Sony Mobile use and contribute to Jenkins and Gerrit; the two central OSS tools in their continuous integration tool chain. Quantitative analysis was performed on change log data from source code repositories in order to identify the top contributors and triangulated with the results from five semi-structured interviews to explore the nature of the commits. The findings of the case study include five major themes: i) The process of opening up towards the tool communities correlates in time with a general adoption of OSS in the organization. ii) Assets not seen as competitive advantage nor a source of revenue are made open to OSS communities, and gradually, the organization turns more open. iii) The requirements engineering process towards the community is informal and based on engagement. iv) The need for systematic and automated testing is still in its infancy, but the needs are identified. v) The innovation outcomes included free features and maintenance, and were believed to increase speed and quality in development. Adopting OI was a result of a paradigm shift of moving from Windows to Linux. This shift enabled Sony Mobile to utilize the Jenkins and Gerrit communities to make their internal development process better for its software developers and testers.

show abstract

Section: Determinants Of Opennessmentioning

confidence: 93%

Section: Explains the Term Open Innovation (Oi) As "A Paradigm That Amentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Section: When Developers Upload a Change Which Can Have Several Revmentioning

confidence: 99%

Section: Opening Upmentioning

confidence: 99%

See 3 more Smart Citations

Open innovation using open source tools: a case study at Sony Mobile

et al. 2017

Self Cite

View full text Add to dashboard Cite

show abstract

A Path for the Implementation of Best Practices for Software Requirements Management Process Using a Multimodel Environment

Gasca‐Hurtado

Muñoz²

2020

Computational Science and Its Applications – ICCSA 2020

View full text Add to dashboard Cite

Continuous improvement is one of the topics of interest for organizations seeking positioning opportunities in the world market. However, software development organizations have high levels of difficulty to implement best practices that address continuous improvement. This paper presents a path to follow to facilitate the work of continuous improvement in a software development organization and that seeks to implement best practices in the software requirements management process. The path is drawn from an analysis of software process improvement models and standards related to software development best practices, under a multimodel environment. The path is structured with a set of techniques, tools, activities, and outputs associated with identified best practices, to facilitate the implementation of improvements in the software requirements management process. Besides, the established path is proposed as an alternative to facilitate the process improvement using a multimodel environment, this way allows establishing balance and instances of collaboration among best practices independent of the model or standard to be implemented.

show abstract

Investigating Open Innovation Practices to Support Requirements Management in Software Ecosystems

Malcher,

Viana,

Antonino

et al. 2024

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Software ecosystems (SECO) affect requirements management when considering multiple actors (i.e., keystone, third-party developer, users) from different organizations using several communication channels such as issue trackers and forums. To deal with this scenario, professionals involved in requirements management in SECO have resorted to several open innovation (OI) practices. Our study aims to investigate OI practices applied to support requirements management in SECO. We conducted a field study based on interviews with 21 professionals involved in requirements management activities in SECO. We identified 10 OI practices to support requirements management in SECO and 14 communication channels to receive/provide requirements from/to external actors. OI practices identified in this study can help practitioners manage requirements in the SECO context in which they are engaged, making this process more informal, open, and collaborative.

show abstract

How can open source software development help requirements management gain the potential of open innovation

Cited by 28 publications

References 8 publications

Open innovation using open source tools: a case study at Sony Mobile

Open innovation using open source tools: a case study at Sony Mobile

A Path for the Implementation of Best Practices for Software Requirements Management Process Using a Multimodel Environment

Investigating Open Innovation Practices to Support Requirements Management in Software Ecosystems

Contact Info

Product

Resources

About