Skip to content

Commit 4380db1

Browse files
committed
Link to markdown files that were in this repo, but that were not linked from README.md. Also fixed template format of introducing-metrics-in-innersource.md.
1 parent a8ad8cd commit 4380db1

File tree

2 files changed

+20
-24
lines changed

2 files changed

+20
-24
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,11 +40,12 @@ possible to either deploy the same service in independent environments with sepa
4040
#### Pattern Ideas (not yet proven; brainstormed)
4141

4242
* [Don't Bother Looking](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/60)
43-
* [Junkyard Styled Inner Sourcing](https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/61)
43+
* [Junkyard Styled Inner Sourcing](junkyard-styled-innersourcing.md)
4444
* [Shared Code Repo Different from Build Repo](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Shared-Code-Repo-Different-from-Build-Repo) - *Deal with the overhead of having shared code in a separate repository that isn't the same as the project-specific one that is tied to production builds.*
4545
* [Incentive Alignment](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Donut:-Creating-Developer-Incentive-Alignment-for-InnerSource-Contribution)
4646
* [Change the Developers Mindset](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Pattern:-change-the-developers-mindset)
4747
* [Share Your Code to Get More Done - Likely Contributors Variant](https://github.com/InnerSourceCommons/innersourcecommons.org/wiki/Pattern:-Share-Your-Code-to-Get-More-Done---Likely-Contributors-Variant)
48+
* [Introducing Metrics in InnerSource](introducing-metrics-in-innersource.md) - *Involve all stakeholders in designing and interpreting metrics to measure the current status in terms of health and performance of the InnerSource initiative.*
4849

4950
#### Pattern Donuts (needing a solution)
5051

@@ -76,7 +77,7 @@ The pattern form is useful for describing proven patterns but it can also be use
7677

7778
[See our CONTRIBUTING.md for details on getting involved](CONTRIBUTING.md)
7879

79-
We encourage beginners seeking answers to jump in by creating ''donuts'' (problems without solutions). We encourage experts to pad their experience - these are hoped to become part of a book one day. Anyone can offer reviews and comments for [in-progress patterns](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls).
80+
We encourage beginners seeking answers to jump in by creating ''donuts'' (problems without solutions). We encourage experts to pad their experience - these are hoped to become part of a book one day. Anyone can offer reviews and comments for [in-progress patterns](https://github.com/InnerSourceCommons/InnerSourcePatterns/pulls).
8081

8182
We work together via Github, Webex, Slack, etc. Do not hesitate to join the [#innersourcecommons](https://isc-inviter.herokuapp.com/) or #innersource-patterns slack channels and ask to be included in the [patterns meetings](/meta/meetings.md) (there is an email list).
8283

@@ -102,4 +103,3 @@ The topics below cover information about how we define, operate, and upkeep this
102103
![Creative Commons License](https://i.creativecommons.org/l/by-sa/4.0/88x31.png)
103104

104105
InnerSourcePatterns by [InnerSourceCommons.org](http://innersourcecommons.org) is licensed under a [Creative Commons Attribution-ShareAlike 4.0 International](http://creativecommons.org/licenses/by-sa/4.0/) License.
105-

introducing-metrics-in-innersource.md

Lines changed: 17 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,19 @@
1-
# Title
1+
## Title
22

33
Introducing Metrics in InnerSource
44

5-
# Patlet
5+
## Patlet
66

77
Involve all stakeholders in designing and interpreting metrics to measure the
8-
current status in terms of _health_ and performance of the InnerSource
8+
current status in terms of _health_ and performance of the InnerSource
99
initiative.
1010

11-
# Context
11+
## Context
1212

1313
An organization is planning to apply or this is in the early stages of applying InnerSource. This would like to measure the current status in terms of 'health' and performance of the initiative, and if the expected outcomes such as an increase in the level of cross-divisional and cross-location collaboration are actually taking place.
1414
This pattern applies to early stages of the initiative or are small in their scope, but they may be mature in their initial process and steps.
1515

16-
17-
# Problem
16+
## Problem
1817

1918
This organization may already have qualitative feedback from the
2019
involved teams, but desire more objective information focused
@@ -27,15 +26,14 @@ Changes in the top level initiatives may affect the InnerSource program
2726
as they rely in the good will of some executive from the organization.
2827

2928
You may have a problem justifying the InnerSource effort when there is
30-
a change in business priorities or business leadership. Then you need
29+
a change in business priorities or business leadership. Then you need
3130
something concrete to justify the program. A future problem you're
3231
guarding against.
3332

3433
If there's a change in the C-level, metrics might be helpful to convince
3534
them that InnerSource is useful.
3635

37-
38-
# Forces
36+
## Forces
3937

4038
People do not like to be tracked or measured.
4139

@@ -49,7 +47,7 @@ Metrics are usually misunderstood if people have not received any
4947
training on those.
5048

5149
Organizations collect vanity of any other type of metrics that do not
52-
track business objectives' sucess or failure over time.
50+
track business objectives' success or failure over time.
5351

5452
Metrics tend to become goals, will subsequently be gamed and thus meaningless.
5553

@@ -59,7 +57,7 @@ Some countries in some organizations may face extra complexity when introducing
5957

6058
Tools and how they use them. There might be a learning curve in the discussion about metrics. And perhaps the tools do not support the metrics we're looking for.
6159

62-
# Solution
60+
## Solution
6361

6462
Bring developers, middle managers and C-level to have a discussion
6563
about metrics. And consider other roles out of the usual development process such as
@@ -73,7 +71,7 @@ Consider third party and neutral player to produce such metrics.
7371

7472
Have specific training on the topic of metrics and good practices
7573
to use them. An example is to have a methodology to follow metrics such
76-
as the Goal-Question-Metric approach or the Objetives-KeyResults one.
74+
as the Goal-Question-Metric approach or the Objectives-KeyResults one.
7775
On the other hand, try to update the metrics used to the short-term
7876
and medium-term goals.
7977

@@ -90,7 +88,7 @@ to understand and follow.
9088
Note: any proposed metric are just examples and not the ones that should be using. Depending on the selection of business goals to track, those will match with specific set of metrics.
9189

9290

93-
# Resulting Context
91+
## Resulting Context
9492

9593
The organization builds a monitoring infrastructure where the agreed
9694
metrics will be the ones to be used.
@@ -106,23 +104,21 @@ Those metrics will help developers to understand how the initiative
106104
evolves and help them with their daily work.
107105

108106

109-
# Known Instances
107+
## Known Instances
108+
109+
## State
110110

111+
Unproven
111112

112-
# Authors
113+
## Authors
113114

114115
- Daniel Izquierdo
115116
- Tim Yao
116117
- Clint
117118
- Russ Rutledge
118119
- Tom
119120

120-
# Acknowledgement
121+
## Acknowledgement
121122

122123
- Georg
123124
- Bob
124-
125-
# State
126-
127-
Early Idea
128-

0 commit comments

Comments
 (0)