ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACAD
1
How to contribute:
2
STEP 0: Talk to the working group and read the kanban
3
STEP 1: Contribute a metric to one of the CCM domains (DSP, CEKM, etc.)
4
STEP 2: Update the change logThis is tracked in a column. For each row: if you change anything substantial put a date and name and type a bit in here about what you did.
5
6
Color key: Some rows change colors automatically to indicate decisions that have been made about them. Adjust the logic in "conditional format rules" and the key is:
7
8
Green: done stuffDeclared done and good for v2. This shouldn't need to be edited further.
9
Super Green: super done stuffDeclared done and good in MVPv1. This column is protected from edits but we can't easily protect the row. Anything in column X triggers this.
10
Dark yellow: super in progressAnything in the review column(s) triggers this. The idea is that as review comments are closed they're removed to the change log although red/green rules have precedence. These are suggested expressions that have engagement and discussion so should probably be worked on.
In some cases they won't move forward (see AIS-07-M1) but are maintained for history.
11
Light Yellow: in progressAnything in the expression column triggers this
12
Red: voted off the islandDeclared NOT a candidate for a metric. Marking a metric as 'manual' or putting anything in the 'Declared NOT a candidate' column triggers this.
13
14
Metrics:
15
The metric fields are described in https://docs.google.com/document/d/1_Pp8QWga9gbkvMzFhB4-p4hAwyCxpbUjdho14HdEdfM/edit?usp=sharing
16
Further instructions:
17
Primary CCM Control IDThis describes the CCM control ID to which the metric is the most relevant. Some metric may seem equaly relevant to more than one CCM control. In that case, just pick one arbitrarily.
18
Applicable CCM Control IDsThis describes all the CCM controls to which the metric appplies, including the Primary CCM control ID.
19
Metric IDScheme used for vMVP release of the catalog is the primary control ID with a -M# suffix. For example "AIS-06-M1".
Prior approach: This should be a six character unique identifier for the metric to simplify cross referencing. It can be built, for example, by chosing the first two letters of the 3 most significant words in the title of the metric

Contributors are free to chose another approach as long as the metric ID is reasonably guaranteed to be unique. There is a kanban item on the status page to finalize for final release.
20
21
When adding a metric to an existing CCM control that already has another metric (see for example the DSP-01 control):
22
1) Simply insert a new line in the spreadsheet below the last metric submited for that specific control.
23
2) Copy the CCM control ID, without repeating the CCM control title and control description
24
3) Add the metric details.
25
26
The metric category column SHALL be filled with one of 3 choices: Manual, Near-Automated, Automated.
27
- Manual: Requires human input or evaluation, based on non-trivial effort. (E.g. Read/review/analyse documents, collect input by email, …)
28
- Near-automated: Relies on an automated tools, with humans providing input or validation with minimal dedicated effort. (Note: we could define as “less than 5 minutes of human work”)
29
- Automated: Can be implemented fully automatically (Note: This does not include initial/one-off setup.)
30
31
32
33
Status is located on "Status & kanban" tab
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100