Introducing Metrics in InnerSource: Merge PR497 and PR501 upstream (instead of new patterns) (#526)

* All forces mentioned were against the pattern. I'm adding some in favor for balance and better justification.
* Add known instance - based on #497 
* Structure the solution. Mention outliers (thank you, Addie).
* Links to metrics references that are mentioned in the text.

Co-authored-by: Trueblueaddie <[email protected]>
Co-authored-by: Sebastian Spier <[email protected]>

Author: 3 people

patterns/1-initial/introducing-metrics-in-innersource.md

@@ -22,6 +22,8 @@ This pattern applies very widely from InnerSource initiatives in their infancy s
 
 ## Forces
 
+Against:
+
 * People do not like to be tracked or measured.
 * There is no canonical monitoring infrastructure for the software development process. Furthermore, such infrastructure is hard to build or to get funding for.
 * There is not a culture of software development metrics.
@@ -32,17 +34,30 @@ This pattern applies very widely from InnerSource initiatives in their infancy s
 * Some organizations in some countries may face extra complexity when introducing metrics as the countries may not allow tracking individuals.
 * There might be a learning curve in the discussion about metrics. And perhaps the tools do not support the InnerSource metrics we are looking for.
 
+In favor:
+
+* Management needs to understand how InnerSource is impacting development. Metrics allow for accurate visualizations.
+* There are several industry standards for monitoring the software development process (e.g. [DORA](https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance), [CHAOSS](https://chaoss.community/)).
+* There are many tools providing metrics for monitoring the software development process and the software product.
+
 ## Solution
 
+### Manage people's needs
+
 Bring developers, middle managers and C-level to have a discussion about metrics. And consider other roles out of the usual development process such as Human Resources, legal departments, product management, and others.
 
 Let developers and middle managers know that these metrics or KPIs are not focused on tracking their personal performance, but to compare if the initiative is currently working as expected.
 
 Consider a third party that is seen as a neutral player to produce such metrics.
 
+### Approach professionally
+
 Have specific training on the topic of metrics and good practices to use them. An example is to have a methodology to follow metrics such as the Goal-Question-Metric approach or the Objectives-KeyResults one. On the other hand, try to reflect the short-term and medium-term goals in the metrics to be used.
 
-Metrics when published or discussed should be done so in the aggregate without referring to specific people.
+When publishing or discussing metrics they should be
+
+* aggregated - without referring to specific people
+* watching out for outliers
 
 Produce a characterization of metrics as this might be helpful for others to understand and follow.
 
@@ -77,7 +92,7 @@ Continued monitoring of these metrics will help middle management and developers
 
 ## Known Instances
 
-TBD
+Santander Bank
 
 ## Status
 
@@ -91,10 +106,12 @@ Initial
 - Russ Rutledge
 - Tom
 - Jack Yang
+- Igor Zubiaurre
 
 ## Acknowledgement
 
 - Georg
 - Bob
 - [Aaron Stewart](https://github.com/a-a-ron/innersource-template-pluralsight/tree/master/metrics)
 - Wilson Mar
+- Addie Girouard