ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Code Review TimeCumulative Flow DiagramTeam Health Check
2
PredictabilityEncourages small, manageable code changes leading to more predictable delivery.Addressing issues discovered by CFD and optimizing processes can have a huge impact on the predictability of the team.Does not directly assess predictability, and while it can provide some qualitative data, ultimately predictability can only be truly judged from outside of the team.
3
ExpertiseFeedback from Code Reviews is a strong contributor to learning, and the impact is bigger if the feedback loop is shorter. There's no strong correlation, but throughput increase can be a result of increased expertise too.Does not concretely measure expertise, and being self-reported, it’s less objective. However, it can be useful to indicate areas for improvement.
4
EngagementNo direct impact, but shorter code review time increases developer experience, which can indirectly affect engagement.This does not directly measure team engagement.Directly assesses team members' feelings of motivation and engagement.
5
CollaborationIndirectly promotes pair work and team collaboration during the review process, as these practices can shorten the review time.Does not directly measure team collaboration, though some metrics (like high amount of WIP) can point to lack of it as a root cause.Directly assesses the team's feeling on the quality and quantity of collaboration opportunities.
6
EfficacyShortening the feedback loop encourages faster customer feedback, but this doesn't directly impact task efficacy.This tool is not directly measuring WHAT gets worked on but HOW work is being done. However, by shortening Average Cycle Time, customer feedback is faster and the team can adapt quicker to new information.Does not directly measure task efficacy, but with the right questions around purpose, it can add to feelings of working on the right things or not.
7
QualitySmall code changes are easier to review, and in case of incidents or bugs, it's faster to find and resolve the issue.Does not directly measure quality, but by identifying bottlenecks and suggesting process optimizations, there’s a potential indirect impact on quality.Does not directly measure the quality of work, but can indicate areas for improvement (in regards to code health for example).
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
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