Are Maturity Models needed in Inner Source?

7dddc875546948b5b5094167c90dc10d?s=47 Bitergia
May 16, 2018
91

Are Maturity Models needed in Inner Source?

Presentation at the InnerSource Commons by Jorge Herrera, Entelgy, and Daniel Izquierdo, Bitergia.

During the last months a set of companies in Spain have been working on a maturity model to give a general framework for C-level and other areas of work in InnerSource. This talk will present some internal discussion around the topic of the maturity model and a potential implementation based on the main InnerSource principles such as Collaboration or Transparency. In addition to this, it is expected to open some discussion around the topic of this type of models that are usually initiated as a set of good practices, but at the end they are seen as pure bureaocracy within organizations.

7dddc875546948b5b5094167c90dc10d?s=128

Bitergia

May 16, 2018
Tweet

Transcript

  1. Are Maturity Models needed in InnerSource? Daniel Izquierdo - Bitergia

    Jorge Herrera - Entelgy InnerSource Commons Spring Summit 2018
  2. /us Zylk, Entelgy and Bitergia Why these three companies? •

    ASOLIF umbrella • Complementary capabilities
  3. Introduction What are maturity models used for? • Industrialization: automated

    way of doing things, sequential, software engineering, factory, etc. • Homogeneous way of the development processes: all of the lines/teams work in the same way. • Self-measurement and continuous improvement (eg: from CMMI 2 to CMMI 3).
  4. Context https://en.wikipedia.org/wiki/Open-source_software_assessment_methodologies

  5. Goals Evaluate how mature the development practices, processes, culture and

    organization model are, in order to move to an “open source way” environment. Create a high level guide showing steps to be followed by a company to adopt InnerSource.
  6. Maturity Model Key Process Areas Key process areas based on

    “these” InnerSource Principles • Transparency (and communication) • Collaboration • Community ◦ Culture is a cross area to the rest Maturity levels (from 0 to 3) • Accidental: individual initiatives • Exploration: let’s try this • Adoption: corporate support and cultural change • Efficient: widely adopted (continuous improvement)
  7. Maturity Model Key Process Areas Other key process areas might

    be used! • P: Product Development • T: Tools Development • I: Innovation (Proof of concepts, demos) • S: Shared components development • C: Culture • Space/Time [Sync F2F, Sync Digital, Async] • Artifact [Talk, Docs, Code] • Content [Side, Ancillary, Main]
  8. Maturity Model Assessment Definition of 2 surveys based on the

    Maturity Model. 16 processes and 36 questions.
  9. An example: from level 0 to level 3 Key Process

    Areas / Maturity Levels ACCIDENTAL (L0) EXPLORATION (L1) ADOPTION (L2) EFFICIENT (L3) COMMUNITY development process & tools Each team follows its own development process and tools. They are not defined to share knowledge and artifacts outside development team. Siloed development teams. Development teams use shared code repositories, internally Some teams develop their own CI process, using non corporate or standard CI tools. There is no code review process defined, although some projects teams do it internally. The organization sponsors and promotes a shared repository for collective knowledge Some teams develop their own CI process, using corporate CI tools. There are CI environments. Code review process defined, and used by some projects. Code review is sometimes done by external team members. Most teams develop their own CI process, using corporate CI tools. There are CI environments. Code review process defined, and used by some projects. Code review is usually done by external team members. PRACTICES
  10. Next steps Review key process areas. Identify more processes. Define

    the correct questions for each process. More questions. Test the model against other organizations. Publish the model.
  11. Open Discussion about Maturity Models Could a maturity model help

    to establish the InnerSource roadmap? • Convince and help the C-level to understand this (full picture) • An organization framework, this helps to walk the path to reach certain benefits by anyone Maturity levels and key process areas are open. • Potentially improved to fit any company requirement/structure. Any suggestions?
  12. Open Discussion about Maturity Models Do you know where you

    are in your InnerSource adoption journey? For how long do you think this will take? How are you objectivizing this process? What would you say that your key process areas are? What are your maturity levels? Are you using a maturity model? why?
  13. Are Maturity Models needed in InnerSource? Daniel Izquierdo - Bitergia

    Jorge Herrera - Entelgy InnerSource Commons Spring Summit 2018