Skip to content

Commit f0babcb

Browse files
committed
Add pattern for discussion: first steps with metrics
This pattern aims at discussing the process to start measuring the inner source initiative from a quantitative point of view.
1 parent d7e0a53 commit f0babcb

File tree

1 file changed

+81
-0
lines changed

1 file changed

+81
-0
lines changed

introducing-metrics-in-innersource.md

Lines changed: 81 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,81 @@
1+
# Title
2+
3+
Introducing Metrics in the InnerSource Initiative
4+
5+
# Context
6+
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.
10+
11+
12+
# Problem
13+
14+
This organization may already have qualitative feedback from the
15+
involved teams, but desire more objective information focused
16+
on development activities.
17+
18+
The organization does not really know where to start measuring
19+
things or what are the key parameters to measure.
20+
21+
22+
# Forces
23+
24+
People do not like to be tracked or measured.
25+
26+
There is not a proper monitoring infrastructure for the software
27+
development process and this is hard to build or to get funding
28+
for this.
29+
30+
There is not a culture of software development metrics.
31+
32+
Metrics are usually misunderstood if people have not received any
33+
training on those.
34+
35+
36+
# Solution
37+
38+
Bring developers, middle managers and C-level to have a discussion
39+
about metrics.
40+
41+
Let developers and middle managers know that these metrics or KPIs
42+
are not focused on tracking their personal performance, but to compare
43+
if the initiative is currently working as expected.
44+
45+
Have specific training on the topic of metrics and good practices
46+
to use them.
47+
48+
Bring specific discussions on the metrics to be used avoiding per
49+
developer granularity or at least anonymizing that info.
50+
51+
52+
# Resulting Context
53+
54+
The organization builds a monitoring infrastructure where the agreed
55+
metrics will be the ones to be used.
56+
57+
Those metrics will help C-level to understand the current situation
58+
of the project and this will help to compare the status before
59+
applying inner source and after applying the inner source initiative.
60+
61+
Those metrics will help middle management to understand how the
62+
initiative evolves and help them with their daily work.
63+
64+
Those metrics will help developers to understand how the initiative
65+
evolves and help them with their daily work.
66+
67+
68+
# Known Instances
69+
70+
71+
# Authors
72+
73+
- Daniel Izquierdo
74+
75+
# Acknowledgement
76+
77+
78+
79+
# State
80+
81+
Early Idea

0 commit comments

Comments
 (0)