Skip to content

Commit a9b511e

Browse files
authored
Improve pattern based on reviews: forces and solution
Thanks to @gregswindle, @gruetter and @NewMexicoKid for their pieces of advice * Update problem statement to mention metrics * Add forces such as unrealistic objectives, vanity or gaming * Add other stakeholders to the solution * Add third party neutral metrics manager to the solution * Add specific method and strategy to start with metrics
1 parent f0babcb commit a9b511e

File tree

1 file changed

+22
-5
lines changed

1 file changed

+22
-5
lines changed

introducing-metrics-in-innersource.md

Lines changed: 22 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,9 +4,12 @@ Introducing Metrics in the InnerSource Initiative
44

55
# Context
66

7-
An organization is applying InnerSource. This needs to check the
8-
current status and if some of the expected outcomes are starting
9-
to work.
7+
An organization is applying InnerSource.
8+
This would like to measure the current status in terms of 'health'
9+
and performance of the initiative, and if the expected outcomes such as
10+
an increase in the level of cross-divisional and cross-location collaboration
11+
are actually taking place.
12+
1013

1114

1215
# Problem
@@ -32,18 +35,32 @@ There is not a culture of software development metrics.
3235
Metrics are usually misunderstood if people have not received any
3336
training on those.
3437

38+
Organizations may have unrealistic or premature business
39+
objectives. Even feeling that InnerSource is a
40+
silver bullet for their problems.
41+
42+
Organizations collect vanity metrics that do not track business
43+
objectives' success or failure over time.
44+
45+
Metrics tend to become goals, will subsequently be gamed and thus meaningless.
3546

3647
# Solution
3748

3849
Bring developers, middle managers and C-level to have a discussion
39-
about metrics.
50+
about metrics. And consider other roles out of the usual development process such as
51+
Human Resources, legal departments, product management, and others.
4052

4153
Let developers and middle managers know that these metrics or KPIs
4254
are not focused on tracking their personal performance, but to compare
4355
if the initiative is currently working as expected.
4456

57+
Consider third party and neutral player to produce such metrics.
58+
4559
Have specific training on the topic of metrics and good practices
46-
to use them.
60+
to use them. An example is to have a methodology to follow metrics such
61+
as the Goal-Question-Metric approach or the Objetives-KeyResults one.
62+
On the other hand, try to update the metrics used to the short-term
63+
and medium-term goals.
4764

4865
Bring specific discussions on the metrics to be used avoiding per
4966
developer granularity or at least anonymizing that info.

0 commit comments

Comments
 (0)