In today’s world, software development is an indispensable element for companies of all sizes and industries. In traditional approaches, software is often developed by self-contained teams and departments without actively considering the reusability of the developed programmes within the company. However, this brings with it a number of challenges, including high costs due to the repeated development of identical components, low flexibility and limited speed of innovation. In this context, inner source is becoming increasingly important. Inner source refers to the application of open source principles and methods within an organisation [1]to promote internal software development. In contrast to conventional development, with inner source all employees have access to the source code of various projects, can modify it, make suggestions for improvement and reuse code for their own projects. This approach promotes collaboration, improves the quality of the software and accelerates the speed of innovation [2]. Inner source also influences the company and its processes [3] from management decisions to product and financial planning. It initially requires a rethink of the corporate culture, clear governance structures and precise control of activities, but the potential efficiency and innovation benefits justify this effort.
Transparency and collaboration
A key feature of Inner Source is the promotion of transparency and collaboration within the organisation. By making the source code accessible to all employees, barriers between different departments and teams are broken down. This allows knowledge and skills to be shared freely, which in turn leads to an increase in ideas and new innovations. By sharing source code, documentation and tools and collaborating on different projects, companies can create synergies and reduce costs.
Flexibility and adaptability
Another advantage of Inner Source is its flexibility and adaptability to changing requirements and market conditions. As the source code is open and can be modified by any employee in the company, development teams can react quickly to feedback from customers and other departments or implement new functions and customise the software according to their wishes. This enables companies to become more agile and continuously improve their products or services without long development cycles or bureaucratic processes.
Promoting innovation and talent development
By promoting an open and collaborative working culture, Inner Source also contributes to fostering innovation and developing talent. Employees have the opportunity to actively participate in the further development of software projects and contribute their skills and ideas. This not only promotes the personal development and satisfaction of employees, but can also contribute to the development of new innovative solutions and products that offer a competitive advantage for the company.
Current challenges
The introduction of Inner Source in the company can be associated with various challenges that need to be carefully addressed to ensure a smooth transition and maximise the long-term benefits.
One such challenge concerns the taxation of inner source activities and the calculation of the value of contributions that flow across company boundaries (so-called transfer prices). As inner-source developers from different departments work on joint projects and share resources, the correct allocation of costs and benefits is often complex [4]. Companies need to develop suitable mechanisms to record and fairly distribute the financial impact of inner source activities.
Another challenge is to promote an open culture of collaboration [5]. Although the idea of knowledge sharing and collaboration is at the centre of Inner Source, existing hierarchies, silo thinking and competitive thinking can hinder the adoption of this approach. It therefore requires a conscious commitment from management to create an environment in which openness, trust and common goals are encouraged.
The integration of inner source into existing business processes poses a further challenge [3]. Many organisations already have established development processes and tools that may not be best suited to the requirements of Inner Source. Adapting Inner Source and integrating it into existing structures requires careful planning and coordination to avoid conflicts and ensure a smooth process.
Finally, measuring collaboration is a challenge in Inner Source [3], [4], [6]. Since the success of Inner Source depends heavily on the active participation and collaboration of employees, the development of appropriate metrics and tools to assess and improve collaboration is crucial. This includes assessing the quality and quantity of contributions, identifying bottlenecks and barriers, and continuously monitoring the progress and impact of Inner Source on organisational performance.
Comparability with analogue phenomena
Similar to open source software projects, where a large number of developers around the world work together to improve a solution, inner source promotes collaboration within an organisation and makes it possible to access the collective knowledge and skills of employees. This can be compared to the concept of crowdsourcing, where companies utilise the creativity of a broad mass of people to solve problems or generate ideas for products. Also comparable is the concept of coworking spaces, where shared office space is provided that start-ups and freelancers, for example, can rent in order to network, benefit from each other and work together on products and solutions.
Despite these similarities, however, inner source is only comparable with analogue phenomena to a very limited extent, as the core aspect of inner source is collaboration in software development within company boundaries. Open collaboration such as crowdsourcing, on the other hand, goes beyond company boundaries, which is why this phenomenon is more comparable to open source. Coworking spaces also involve collaboration and exchange beyond legal company boundaries, which is why, strictly speaking, this concept would also be more comparable to open source. However, it is important to note that when comparing open source, inner source, crowdsourcing and coworking spaces, we only looked at the way in which people interact with each other. Legal aspects (e.g. licence law, which plays a particularly important role in inner source) were not compared here for reasons of simplicity.
Inner source, crowdsourcing and the concept of coworking spaces, on the other hand, are identical in terms of networking, albeit at different levels. While various development processes, workflows and data are standardised and
-processes, workflows and data are standardised and made more efficient (higher development speed), coworking spaces bring people and ideas together in the analogue world.
Similar to scientific communities, in which knowledge is openly shared and jointly developed, Inner Source creates a culture of knowledge transfer and continuous improvement within the company. The aim is therefore to make companies more open and flexible and to enable easier, increased changeability of the software and processes to be developed.
Social relevance
The use of inner source in software development not only has an economic impact on companies, but also a broad social significance. By promoting openness, transparency and collaboration, inner source helps to make the development of software more democratic. Furthermore, the reuse and sharing of development resources helps to increase efficiency, enabling companies to respond more quickly to changing market conditions and deliver innovative solutions. In addition, Inner Source paves the way for companies to not only collaborate openly within the organisation in further steps, but also to make the software as a whole available as open source software and thus demonstrate transparency.
Sources
- Stol, K. J. et al. (2011). A comparative study of challenges in integrating open source software and inner source software. In: Information and Software Technology 53(12), 1319–1336.
- Capraro, M./Dorner, M./Riehle, D. (2018, May). The patch-flow method for measuring inner source collaboration. In: Proceedings of the 15th International Conference on Mining Software Repositories, 515–525.
- Buchner, S./Riehle, D. (2023). The Business Impact of Inner Source and How to Quantify It. In: ACM Computing Surveys 56(2), 1–27.
- Buchner, S./Riehle, D. (2022, January). Calculating the Costs of Inner Source Collaboration by Computing the Time Worked. In: Proceedings of the 55th Hawaii International Conference on System Sciences (HICSS), 1–10.
- Edison, H. et al. (2020). Inner source software development: Current thinking and an agenda for future research. In: Journal of Systems and Software 163, 110520.
- Hirsch, J./Riehle, D. (2022, October). Management Accounting Concepts for Inner Source Software Engineering. In International Conference on Software Business, 101–116.