Misconceptions about ways of working: How can OSPO/ISPO help? - Shanmugapriya Manoharan (Ikea)
InnerSource is actively embraced by many organizations to promote collaborative development. In organizations that are heavily working in silos, it presents numerous challenges that hinder the adoption of a collaborative development model. This discussion explores the misconceptions or hurdles faced by teams in embracing InnerSource and discusses how a governance model like Open Source Program Office (OSPO) or InnerSource Program Office (ISPO) can help overcome these obstacles. The misconceptions and misinterpretations held by teams often lead to inertia and resistance towards collaborative development. The first and common misconception seen is the fear of losing ownership or control of a project when opening it up to a wider community of external contributors. This misconception arises due to a lack of familiarity with inclusive development models. The essence of InnerSource lies in inclusive decision-making processes, empowering teams to drive projects and implementation collectively. The second misconception revolves around concerns that contributions from the community may introduce errors or break the software. Teams working extensively on a project possess in-depth knowledge of its components, testing procedures, and security aspects. In contrast, external contributors may lack this comprehensive understanding, potentially leading to mistakes. This hurdle is particularly prevalent in projects that are highly siloed, where implementation, testing, and documentation are highly restricted within the team. The third misconception involves teams choosing the least used or least maintained project for InnerSource experimentation. This approach may be adopted by teams being initially hesitant to adopt inclusive development with a wider community. However, selecting a project without active maintainers or limited resources for maintenance poses significant challenges in building a supportive community. Such initiatives are prone to failure, potentially leading to the misconception that InnerSource is not beneficial. It is crucial to understand that InnerSource does not automatically imply the availability of resources or an established community for maintaining a software project. To address these misconceptions and to overcome hurdles, OSPO/ISPOs can play a vital role by educating the teams through workshops and setting guidelines on InnerSource practices. By clearly defining the roles and responsibilities of maintainers, code owners, contributors, project stewards, community members, and managers, OSPO/ISPOs provide a framework for effective collaboration. Moreover, OSPO/ISPOs, as independent entities with visibility across teams, can impartially resolve conflicts and facilitate smoother adoption of InnerSource within the organization. By leveraging the expertise and guidance provided by OSPO/ISPOs, organizations can break down silos, foster collaboration, and drive innovation. The OSPO/ISPO serves as a catalyst for change, helping teams overcome inertia and embrace the InnerSource model for enhanced software development and increased value creation and long term success.
Bio:
Shanmugapriya Manoharan
Shanmugapriya is an Open Source & InnerSource enthusiast, working as Engineering Advisor at Open Source Program Office (OSPO), IKEA IT AB. She has several years of experience in driving initiatives and projects including Open Source and InnerSource projects, while working in organizations like HPE and Dell Technologies. She specializes in Cloud technologies, Containerization, Virtualization and Enterprise Storage. She holds a Master’s degree in Software System and Bachelor’s degree in Computer Science and Engineering.
