Category: 2. Building Products
-
Inner source definition, benefits, and challenges [CSUR Journal]
Abstract Inner Source (IS) is the use of open source software development practices and the establishment of an open source-like culture within organizations. The organization may still develop proprietary software but internally opens up its development. A steady stream of scientific literature and practitioner reports indicates the interest in this research area. However, the research…
-
Platforms but no platform organizations
One result of our recent case study research on inner source is that companies may not always need platform organizations to get to a platform of shared reusable assets. They will certainly need platforms, but they won’t need a dedicated organizational unit to develop and maintain this platform. You don’t have to read the research…
-
Invited research talk on inner source at FSE 2016
I’ll be giving an invited research talk (“journal-first”) at FSE 2016 in Seattle today, Nov 15, 2016. It is in Session 5, right after lunch. The underlying Transactions on Software Engineering (TSE) paper is available here. More on inner source here.
-
An example charter for inner source programs [Technical Report]
Abstract Inner source software development is firm-internal software development that uses the principles of open source software development to collaborate across intra-organizational boundaries that would otherwise hinder any such collaboration. Inner source breaks down the barriers to collaboration across development silos by setting up an internal ecosystem of readily available software components. To get started…
-
Inner source in platform-based product engineering [TSE Journal]
Abstract Inner source is an approach to collaboration across intra-organizational boundaries for the creation of shared reusable assets. Prior project reports on inner source suggest improved code reuse and better knowledge sharing. Using a multiple-case case study research approach, we analyze the problems that three major software development organizations were facing in their product line…
-
That new agile delivery terminology
Old New Engineering Manager Delivery Lead Director of Engineering Delivery Head Vice President of Engineering Delivery Hero I see a trademark conflict brewing… (not really, trademarks are scoped by domain, there probably is little confusion between a retail service and a corporate role).