Skip to content

Commit cff66d7

Browse files
authored
Small readability updates
Small readability updates.
1 parent d067b11 commit cff66d7

File tree

1 file changed

+9
-11
lines changed

1 file changed

+9
-11
lines changed

start-as-experiment.md

Lines changed: 9 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ investment.
1616

1717
## Context
1818

19-
The company is considering to leverage InnerSource to increase the efficiency
19+
The company is considering InnerSource to increase the efficiency
2020
of collaboration on software projects. However, most managers are not familiar
2121
with the Open Source working model and are instead accustomed to hierarchical,
2222
top-down control style management. The idea of InnerSource is very popular with
@@ -32,7 +32,7 @@ or are actively developing Open Source software.
3232
and if many projects are likely to rely on it, a decision to shut it down
3333
will be very unpopular and therefore hard to make. The perceived resulting
3434
loss of control might deter some managers to even start with InnerSource.
35-
- Implementing InnerSource style working models are often a radically departure
35+
- Implementing InnerSource style working models are often a radical departure
3636
from previously practiced working models. It is therefore likely, that
3737
existing, mandatory processes are no longer applicable and that appropriate
3838
governing processes are missing. The result might be that one has to operate
@@ -43,12 +43,10 @@ or are actively developing Open Source software.
4343
## Solution
4444

4545
Declare the InnerSource initiative as a time limited experiment. Define and
46-
communicate the criteria for projects to join the InnerSource experiment. The
47-
criteria should be chosen such that they maximize the chances of building a
48-
healthy InnerSource community around the selected InnerSource projects. They
49-
should also help to ensure that the setting of the projects is such that they
50-
can later be used to gain externally valid insights into the effects of
51-
applying InnerSource. Examples for such criteria are
46+
communicate the criteria for projects to join the InnerSource experiment. Choose
47+
criteria that will maximize the chances of building a healthy InnerSource community
48+
around the selected InnerSource projects. The criteria, on examination within a project's context,
49+
should transparently highlight the benefits of applying InnerSource. Examples for such criteria are
5250

5351
- Sufficient geographical distribution of developers
5452
- Sufficient departmental mix of developers,
@@ -70,7 +68,7 @@ their value contributions.
7068

7169
Managers are able to kick start InnerSource for the following reasons:
7270

73-
- The experimental setup eases the need of managers to scrutinize the
71+
- The experimental setup eases the need for managers to scrutinize the
7472
InnerSource program numbers in the same way that they would for typical
7573
projects.
7674
- The possibility of failure of the experiment is understood and accepted. The
@@ -80,8 +78,8 @@ Managers are able to kick start InnerSource for the following reasons:
8078
- In case of success, the data gathered during the experiment will allow
8179
managers to make a longer lasting commitment to InnerSource.
8280

83-
Participants in the InnerSource experiment are now conscious of the fact that
84-
they have to prove to management that InnerSource yields the promised benefits.
81+
Participants in the InnerSource experiment are now conscious that they have to
82+
prove to management that InnerSource yields the promised benefits.
8583
It will therefore help to focus work on those activities which provide the most
8684
demonstrable value thus increasing the chances of success.
8785

0 commit comments

Comments
 (0)