Skip to content

Commit 82724e8

Browse files
Nick Yeatesgruetter
authored andcommitted
pattern/contracted-contributor (#57)
Added reviewed pattern _Contracted Contributor_
1 parent a8c9b13 commit 82724e8

File tree

2 files changed

+145
-0
lines changed

2 files changed

+145
-0
lines changed

assets/img/contracted-contributor.png

401 KB
Loading

contracted-contributor.md

Lines changed: 145 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,145 @@
1+
## Title
2+
3+
_Contracted Contributor_
4+
5+
## Context
6+
7+
A large corporation has started an InnerSource initiative. Major goals for the
8+
initiative are to increase the efficiency of distributed software develoment
9+
and to foster innovation by allowing every associate to voluntarily
10+
contribute to InnerSource projects, regardless of topic and business unit.
11+
12+
Top level management is on board and supporting the InnerSource initiative. For
13+
them, the InnerSource initiative is just one of many initiatives to foster
14+
innovation and efficiency, though. They are funding InnerSource with money and
15+
capacity for community leaders and are largely giving autonomy as for how the
16+
budget is spent. They are also limiting the breadth and duration of the
17+
initiative and partake in periodic reviews until there is proof that it yields
18+
the expected results (see [Review Committee](review-commitee.md)). Top level
19+
management has announced their support for InnerSource on various company
20+
internal meetings.
21+
22+
However, top level management has not yet empowered or incentivised mid-level
23+
managers to allow or even motivate their employees to participate in
24+
cross-divisional InnerSource activities. In addition to that, the capacity of
25+
every associate is usually allocated to non InnerSource projects for 100 % of
26+
their working time. Cross organizational collaboration is not yet the norm and
27+
line managers usually do not have targets outside of their own organisation.
28+
Contributions to InnerSource projects are expected to be made during working
29+
hours, not during free time.
30+
31+
## Problem
32+
33+
Without support by middle management, the total number of contributors and, as
34+
a result, the amount of contributions made and value generated by the
35+
InnerSource initiative will likely fall below expectation of top level
36+
management. This will likely be ampflified if there is no adequate funding for
37+
and empowerment of [Dedicated Community Leaders](dedicated-community-leader.md).
38+
This runs the risk of top level management abandoning the InnerSource idea.
39+
40+
## Forces
41+
42+
- Managers are held responsible for the results of their business units.
43+
Letting their staff participate in InnerSource activities which might spend
44+
time making contributions outside of their business unit effectively reduces
45+
the capacity of his or her unit. This will likely make it harder for the
46+
managers to reach or exceed their goals.
47+
- Line managers and HR will, by default, judge the performance of their
48+
subordinates against their business units goals, which might not be aligned
49+
with the goals of the InnerSource community.
50+
- The less executive air cover a line manager perceives he has, the less likely
51+
is he or she to have his or her staff participate in InnerSource activities
52+
which contribute to another business unit.
53+
- The less transparency and control a line manager has of work done by one of
54+
her subordinates, the less likely is she to allow her to contribute.
55+
- The less formally work in InnerSource is managed and organised, the less
56+
likely a line manager who is accustomed to formal processes is to sign off on
57+
one of her employees contributing to InnerSource.
58+
- The more time an associate spends on contributions to an InnerSource project
59+
which does not benefit his day-to-day work, the more will the workload for
60+
his teammates in his business unit increase.
61+
- Individual contributors will likely consider participating in InnerSource
62+
as an opportunity to enhance their professional netowrk within the company
63+
and to gain knowledege and experience in the technical area of her
64+
contributions.
65+
66+
## Solution
67+
68+
Set up a formal contracting between the contributor, her line manager and a
69+
centrally funded and steered InnerSource governance office (ISGO). Have the
70+
ISGO reimburse business units who contracted contributors for the contracted
71+
time.
72+
73+
- The contracting specifies a maximum percentage of the associates work time in
74+
InnerSource.
75+
- The contracting clearly states that work in the contributor's business unit
76+
takes precendence over work in InnerSource.
77+
- The contracting states that it is not required to work in InnerSource for the
78+
maximum percentage specified in the contract.
79+
- The contracting is signed by the contributor, the contributor's line manager,
80+
the governance office and the [Dedicated Community
81+
Leader](dedicated-community-leader.md) of the community the contributor will
82+
be contributing to.
83+
- The governance office offers to mediate between the contributor and her line
84+
manager in case of conflict regarding the time for contributions.
85+
- The [Dedicated Community Leader](dedicated-community-leader.md) participates
86+
in or provides input for performance reviews of contributors contracted for
87+
more than 20 %.
88+
89+
<img alt="Contracted Contributor" src="/assets/img/contracted-contributor.png" width="70%">
90+
91+
## Resulting Context
92+
93+
A formal contracting and centrally funded reimbursements convincingly
94+
communicating the organizations support for the InnerSource initiative, thus
95+
empowering middle management to sign off on it:
96+
97+
- Allocation of corporate funds to business units for reimbursement of
98+
development capacity signals to line managers that InnerSource is deemed
99+
valuable by the organization, that it has executive air cover and that they
100+
are expected to support it, too.
101+
- A formal contracting signals that work in InnerSource is managed
102+
professionally and inspires trust.
103+
- A formal contracting increases transparency and provides a better overview
104+
about the associate's available capacity for his business unit and
105+
InnerSource projects, thus reducing the risk of "over-booked/planned
106+
capacity".
107+
108+
A formal contracting is also beneficial for contributors and communities:
109+
110+
- With a stable group of contributors, it is more likely that some of them will
111+
eventually achieve trusted committer status.
112+
- A formal contracting provides a basis for resolving conflict related to
113+
participation in InnerSource activities. Note that mediate will likely be
114+
successful only for a few companies with a culture condusive to that.
115+
116+
## Known Instances
117+
118+
- _BIOS at Robert Bosch GmbH_.
119+
120+
## Status
121+
122+
_Proven Pattern_
123+
124+
## Author
125+
126+
- Georg Grütter (Robert Bosch GmbH)
127+
128+
## Acknowledgements
129+
130+
- Diogo Fregonese (Robert Bosch GmbH)
131+
- Robert Hansel (Robert Bosch GmbH)
132+
- Jim Jagielski
133+
- Tim Yao
134+
- Cedric Williams
135+
- Klaas-Jan Stol
136+
- Padma Sudarsan
137+
- Nick Stahl
138+
- Ofer Hermoni
139+
- Robert C. Hanmer
140+
141+
## Changelog
142+
143+
- **2016-10-25** - first review
144+
- **2017-05-09** - rework
145+
- **2017-09-08** - second review, final rework and merged

0 commit comments

Comments
 (0)