Skip to content

Commit 01a81d2

Browse files
committed
Merge remote-tracking branch 'origin' into fix-gqm-links
2 parents d177ed9 + 5837fe8 commit 01a81d2

File tree

1 file changed

+47
-0
lines changed

1 file changed

+47
-0
lines changed

measuring/goals_using_metrics.md

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
Goals using Metrics
2+
===================
3+
4+
This section aims at providing a strategy for your InnerSource metrics
5+
that help to understand the path from your initial process till a full
6+
InnerSource organization.
7+
8+
It is important to remark that metrics useful for some organizations are
9+
not that useful in other contexts. This is similar to the open source
10+
projects where a project is not that similar to other in terms of
11+
governance, licenses, infrastructure or detailed process, but they are
12+
producing open source software and working as a community. This handbook
13+
has a similar goal, to detail how an ideal InnerSource project would
14+
be, but there are not two organizations using the same InnerSource
15+
approach.
16+
17+
Thus, metrics useful for some contexts, for example technological
18+
organizations, might not apply to other context such as banks due to
19+
external factors such as legal regulations that are even different from
20+
country to country.
21+
22+
In addition to all of this, when measuring InnerSource, there are three
23+
main purposes to use metrics: check on going work, lead process
24+
improvement[^5] and motivational aspects.
25+
26+
- **Check** on going work: this helps to understand where the
27+
development is right now. To be aware of the status helps to
28+
understand how fast things are changing when a new process is in the
29+
pipeline. This also helps to go from A to B and even trying several
30+
approaches to the same problem and have tests for this.
31+
32+
- **Lead** process improvement: InnerSource means a change in how
33+
process works in the following. From a hierarchical way to a flatter
34+
way of working, InnerSource needs indicators to help to determine
35+
if that process improvement is properly working. And if this is not
36+
working, then using another approach or apply other policies.
37+
38+
- **Motivational** aspects: InnerSource also means cultural change,
39+
and this is not usually taken into account in other methodologies.
40+
Indeed, this cultural change is identified in InnerSource as key.
41+
This should be the type of actions that will help to migrate from a
42+
traditional way of working to a more transparent and community-
43+
oriented way to work. And metrics can help to lead this process.
44+
First, to let developers know where they are and how their process
45+
is working, but also to have some fun within the work and
46+
competitions through challenges, hackathons and other measurable
47+
activities that lead to a more community-oriented organizations.

0 commit comments

Comments
 (0)