You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Link to markdown files that were in this repo, but that were not linked from README.md. Also fixed template format of introducing-metrics-in-innersource.md.
*[Shared Code Repo Different from Build Repo](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Shared-Code-Repo-Different-from-Build-Repo) - *Deal with the overhead of having shared code in a separate repository that isn't the same as the project-specific one that is tied to production builds.*
*[Change the Developers Mindset](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Pattern:-change-the-developers-mindset)
47
47
*[Share Your Code to Get More Done - Likely Contributors Variant](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Pattern:-Share-Your-Code-to-Get-More-Done---Likely-Contributors-Variant)
48
+
*[Introducing Metrics in InnerSource](introducing-metrics-in-innersource.md) - *Involve all stakeholders in designing and interpreting metrics to measure the current status in terms of health and performance of the InnerSource initiative.*
48
49
49
50
#### Pattern Donuts (needing a solution)
50
51
@@ -76,7 +77,7 @@ The pattern form is useful for describing proven patterns but it can also be use
76
77
77
78
[See our CONTRIBUTING.md for details on getting involved](CONTRIBUTING.md)
78
79
79
-
We encourage beginners seeking answers to jump in by creating ''donuts'' (problems without solutions). We encourage experts to pad their experience - these are hoped to become part of a book one day. Anyone can offer reviews and comments for [in-progress patterns](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls).
80
+
We encourage beginners seeking answers to jump in by creating ''donuts'' (problems without solutions). We encourage experts to pad their experience - these are hoped to become part of a book one day. Anyone can offer reviews and comments for [in-progress patterns](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls).
80
81
81
82
We work together via Github, Webex, Slack, etc. Do not hesitate to join the [#innersourcecommons](https://isc-inviter.herokuapp.com/) or #innersource-patterns slack channels and ask to be included in the [patterns meetings](/meta/meetings.md) (there is an email list).
82
83
@@ -102,4 +103,3 @@ The topics below cover information about how we define, operate, and upkeep this
InnerSourcePatterns by [InnerSourceCommons.org](http://innersourcecommons.org) is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International](http://creativecommons.org/licenses/by-sa/4.0/) License.
Copy file name to clipboardExpand all lines: introducing-metrics-in-innersource.md
+17-21Lines changed: 17 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,19 @@
1
-
# Title
1
+
##Title
2
2
3
3
Introducing Metrics in InnerSource
4
4
5
-
# Patlet
5
+
##Patlet
6
6
7
7
Involve all stakeholders in designing and interpreting metrics to measure the
8
-
current status in terms of _health_ and performance of the InnerSource
8
+
current status in terms of _health_ and performance of the InnerSource
9
9
initiative.
10
10
11
-
# Context
11
+
##Context
12
12
13
13
An organization is planning to apply or this is in the early stages of applying InnerSource. This would like to measure the current status in terms of 'health' and performance of the initiative, and if the expected outcomes such as an increase in the level of cross-divisional and cross-location collaboration are actually taking place.
14
14
This pattern applies to early stages of the initiative or are small in their scope, but they may be mature in their initial process and steps.
15
15
16
-
17
-
# Problem
16
+
## Problem
18
17
19
18
This organization may already have qualitative feedback from the
20
19
involved teams, but desire more objective information focused
@@ -27,15 +26,14 @@ Changes in the top level initiatives may affect the InnerSource program
27
26
as they rely in the good will of some executive from the organization.
28
27
29
28
You may have a problem justifying the InnerSource effort when there is
30
-
a change in business priorities or business leadership. Then you need
29
+
a change in business priorities or business leadership. Then you need
31
30
something concrete to justify the program. A future problem you're
32
31
guarding against.
33
32
34
33
If there's a change in the C-level, metrics might be helpful to convince
35
34
them that InnerSource is useful.
36
35
37
-
38
-
# Forces
36
+
## Forces
39
37
40
38
People do not like to be tracked or measured.
41
39
@@ -49,7 +47,7 @@ Metrics are usually misunderstood if people have not received any
49
47
training on those.
50
48
51
49
Organizations collect vanity of any other type of metrics that do not
52
-
track business objectives' sucess or failure over time.
50
+
track business objectives' success or failure over time.
53
51
54
52
Metrics tend to become goals, will subsequently be gamed and thus meaningless.
55
53
@@ -59,7 +57,7 @@ Some countries in some organizations may face extra complexity when introducing
59
57
60
58
Tools and how they use them. There might be a learning curve in the discussion about metrics. And perhaps the tools do not support the metrics we're looking for.
61
59
62
-
# Solution
60
+
##Solution
63
61
64
62
Bring developers, middle managers and C-level to have a discussion
65
63
about metrics. And consider other roles out of the usual development process such as
@@ -73,7 +71,7 @@ Consider third party and neutral player to produce such metrics.
73
71
74
72
Have specific training on the topic of metrics and good practices
75
73
to use them. An example is to have a methodology to follow metrics such
76
-
as the Goal-Question-Metric approach or the Objetives-KeyResults one.
74
+
as the Goal-Question-Metric approach or the Objectives-KeyResults one.
77
75
On the other hand, try to update the metrics used to the short-term
78
76
and medium-term goals.
79
77
@@ -90,7 +88,7 @@ to understand and follow.
90
88
Note: any proposed metric are just examples and not the ones that should be using. Depending on the selection of business goals to track, those will match with specific set of metrics.
91
89
92
90
93
-
# Resulting Context
91
+
##Resulting Context
94
92
95
93
The organization builds a monitoring infrastructure where the agreed
96
94
metrics will be the ones to be used.
@@ -106,23 +104,21 @@ Those metrics will help developers to understand how the initiative
0 commit comments