Merge pull request #23 from InnerSourceCommons/rrrutledge-patch-1

Sample goal/question/metric

Author: rrrutledge

measuring/goals/reduce-duplication.md

@@ -0,0 +1,11 @@
+# **Goal:** Reduce duplication
+
+Why should be build things more than once?
+We're already busy and behind where we'd like to be.
+We want to build just once software that solves commmon problems and then share it widely throughout the company.
+
+## Related Questions
+
+| **Question** | **How it relates to the goal** | **Gotchas** |
+| --- | --- | --- |
+| [Who uses the InnerSource project?](../questions/who-uses.md) | Every instance of reduced duplication will show up as an increase in usage. | The converse is not necessarily true that every instance of increased usage is an instance of reduced duplication.  It's always possible that some shared usage would have happened even without InnerSource. |

measuring/metrics/usage-count.md

@@ -0,0 +1,20 @@
+# **Metric:** Usage count
+
+**Synopsis**: Count how many times the InnerSource project is used.
+Gain additional insight by gathering metadata on these usages such as business unit or timeframe.
+With this additional metadata we can see how lopsided or even the usage is spread across the company and across time.
+
+**Unit of Measurement**: Ordinal number.
+
+**Interpretation**: Higher absolute usage count is generally better.
+Higher diversity of usage across business unit or timeframe is generally better.
+
+**Measuring**
+
+If the project is an API and requires caller authentication, then read the API logs to determine the list of callers.
+
+If the project is a module (or package), then scan your source control system for files that list out dependencies for a package manager to install.
+Here is a list of [many package managers](https://github.com/oss-review-toolkit/ort#analyzer).
+Look in those dependencies for usage of your InnerSource project.
+
+If the project is a UI and requires login, then read the project logs to determine the list of users.

measuring/questions/who-uses.md

@@ -0,0 +1,13 @@
+# Who uses the InnerSource project?
+
+Depending on the InnerSource project, usage of the project could look something like:
+
+* Inclusion of a module in a build.
+* Calling and API.
+* Visiting a UI.
+
+## Related Metrics
+
+| **Metric** | **How it answers the question** | **Gotchas** |
+| --- | --- | --- |
+| [Usage count](../metrics/usage-count.md) | We can see how many times an InnerSource project is reused.  If there is extra information attached to that usage (like which business unit is the user) then we can see how widely across the company an InnerSource project is used. | |