Are you succeeding when InnerSourcing? Defining a metrics strategy

  • 0
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53

https://conferences.oreilly.com/oscon/oscon-tx/public/schedule/detail/61401
InnerSource is a new approach to deal with usual issues in large organizations to increase development velocity and improve developer engagement, but it is still unclear how this is measured—or if this process is even actually succeeding. Daniel Izquierdo explores the concepts and tools you need from an analytics perspective and explains how they can help you make decisions.
Monitoring should be one of the key aspects when applying InnerSource concepts within any organization. It requires expertise in the field, a detailed methodology and in general a strategy around measurements focused on awareness, process improvement, and motivational actions: awareness helps to understand the current software development stage; process improvement helps to detect issues and understand and fix the root error cause; and motivational actions push developers to reach some goals.
Metrics provide an understanding of the current structure and methodology of a software development team and how far an organization is from an ideal InnerSource situation. Indeed, it is possible to benchmark the team with respect to open source projects, such as the Apache Software Foundation, usually taken as example of where the InnerSource path leads to.
Topics include:
Goals using metrics
Areas of analysis
The Goal-Question-Metric approach
Strategy when using metrics
Some examples

More Slides