Merge pull request #25 from jeffabailey/master

Add Use Goals, Questions, and Metrics section

Author: rrrutledge

SUMMARY.md

@@ -14,6 +14,13 @@
   * [Authors and Reviewers](infrastructure/authors.md)
 * [What, When and How to Measure](measuring/introduction.md)
   * [Goals using Metrics](measuring/goals.md)
+    * [Use Goals, Questions, and Metrics](measuring/use\_gqm.md)
+      * [Goals](use\_gqm/goals/README.md)
+        * [Reduce Duplication](measuring/goals/reduce-duplication.md)
+      * [Questions](use\_gqm/questions/README.md)
+        * [Who Uses](measuring/questions/who-uses.md)
+      * [Metrics](use\_gqm/metrics/README.md)
+        * [Usage Count](measuring/metrics/usage-count.md)
   * [Areas of Analysis](measuring/areas.md)
   * [Goal-Question-Metric Approach](measuring/gqm.md)
   * [Strategy](measuring/strategy.md)

measuring/metrics.md

@@ -19,7 +19,7 @@ clear workflow followed by any developer within the organization.
 
 On the other hand, if the workflow is not well defined or if the
 development infrastructure allows to have work arounds, this may lead to
-situations where shortcuts are usual and developers and managers may get
+situations where shortcuts are usual, and developers and managers may get
 frustrated at some point.
 
 Thus, having in mind those differences between two communities, inner

measuring/use_gqm.md

@@ -0,0 +1,21 @@
+# Use Goals, Questions, and Metrics
+
+*An overview of the GQM catalog.*
+
+```mermaid
+graph LR;
+reduce-duplication[Reduce Duplication] --> who-uses[Who Uses];
+who-uses --> usage-count[Usage Count];
+```
+
+## Goals
+
+* [Reduce Duplication](../goals/reduce_duplication.md)  
+
+## Questions
+
+* [Who uses the InnerSource project?](../questions/who-uses.md)
+
+## Metrics
+
+* [Usage Count](../metrics/usage_count.md)

use_gqm/goals/README.md

@@ -0,0 +1,2 @@
+# Goals
+

use_gqm/metrics/README.md

@@ -0,0 +1,2 @@
+# Metrics
+

use_gqm/questions/README.md

@@ -0,0 +1,2 @@
+# Questions
+