Inner Source Project Management
Höst, Martin LU ; Stol, Klaas-Jan and Orucevic-Alagic, Alma LU
(2014)
p.343-369
- Abstract
- Software development organizations are continuously looking for better ways to manage their projects. An emerging approach to achieve this is Inner Source, which refers to the adoption of Open Source development practices within the confines of an organization. With an Inner Source approach, individuals, teams, and departments within an organization can start software projects, very similar to the Open Source model. This affects the way projects are managed in a variety of ways. Firstly, it will affect strategic aspects such as a software sourcing strategy that includes decisions on which software can be “Inner-Sourced.” Secondly, at the tactical level, organizations should choose an appropriate Inner Source adoption model that suits the... (More)
- Software development organizations are continuously looking for better ways to manage their projects. An emerging approach to achieve this is Inner Source, which refers to the adoption of Open Source development practices within the confines of an organization. With an Inner Source approach, individuals, teams, and departments within an organization can start software projects, very similar to the Open Source model. This affects the way projects are managed in a variety of ways. Firstly, it will affect strategic aspects such as a software sourcing strategy that includes decisions on which software can be “Inner-Sourced.” Secondly, at the tactical level, organizations should choose an appropriate Inner Source adoption model that suits the goals and scope of the organization. Finally, it will affect the operational aspects of a project, for example, in the way different people across a whole organization can access the source code and make improvements. Furthermore, Inner Source makes communication much more transparent. While Inner Source offers a variety of potential benefits to an organization, there are also a number of challenges to address. This chapter discusses how the introduction of Inner Source may affect conventional software developing environments and especially how it affects software project management aspects. Based on our studies and those presented in the literature, it outlines a number of benefits of Inner Source as well as a number of challenges and some suggestions as to how they can be addressed.
(Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/4249493
- author
- Höst, Martin
LU
; Stol, Klaas-Jan
and Orucevic-Alagic, Alma
LU
- organization
- publishing date
- 2014
- type
- Chapter in Book/Report/Conference proceeding
- publication status
- published
- subject
- keywords
- Open Source, Project Management, Open Source Software, Business Unit, Software Product Line
- host publication
- Software Project Management in a Changing World
- editor
- Wohlin, Claes and Ruhe, Günther
- pages
- 343 - 369
- publisher
- Springer
- external identifiers
-
- scopus:84930714818
- ISBN
- 978-3-642-55034-8
- 978-3-642-55035-5
- DOI
- 10.1007/978-3-642-55035-5_14
- project
- Embedded Applications Software Engineering
- language
- English
- LU publication?
- yes
- id
- 49c4d839-a8a3-4aed-8e87-099d00c869fc (old id 4249493)
- date added to LUP
- 2016-04-04 10:36:39
- date last changed
- 2025-01-06 15:30:44
@inbook{49c4d839-a8a3-4aed-8e87-099d00c869fc,
abstract = {{Software development organizations are continuously looking for better ways to manage their projects. An emerging approach to achieve this is Inner Source, which refers to the adoption of Open Source development practices within the confines of an organization. With an Inner Source approach, individuals, teams, and departments within an organization can start software projects, very similar to the Open Source model. This affects the way projects are managed in a variety of ways. Firstly, it will affect strategic aspects such as a software sourcing strategy that includes decisions on which software can be “Inner-Sourced.” Secondly, at the tactical level, organizations should choose an appropriate Inner Source adoption model that suits the goals and scope of the organization. Finally, it will affect the operational aspects of a project, for example, in the way different people across a whole organization can access the source code and make improvements. Furthermore, Inner Source makes communication much more transparent. While Inner Source offers a variety of potential benefits to an organization, there are also a number of challenges to address. This chapter discusses how the introduction of Inner Source may affect conventional software developing environments and especially how it affects software project management aspects. Based on our studies and those presented in the literature, it outlines a number of benefits of Inner Source as well as a number of challenges and some suggestions as to how they can be addressed.<br/><br/>}},
author = {{Höst, Martin and Stol, Klaas-Jan and Orucevic-Alagic, Alma}},
booktitle = {{Software Project Management in a Changing World}},
editor = {{Wohlin, Claes and Ruhe, Günther}},
isbn = {{978-3-642-55034-8}},
keywords = {{Open Source; Project Management; Open Source Software; Business Unit; Software Product Line}},
language = {{eng}},
pages = {{343--369}},
publisher = {{Springer}},
title = {{Inner Source Project Management}},
url = {{http://dx.doi.org/10.1007/978-3-642-55035-5_14}},
doi = {{10.1007/978-3-642-55035-5_14}},
year = {{2014}},
}