ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Name 1Name 2Name 3Name 4Name 5ProblemsSolutionsAction Points
2
Easy to release
3
Suitable process
4
Tech quality (code base health)
5
Value
6
Speed
7
Mission
8
Fun
9
Learning
10
Support
11
Pawns or players (MB Team)
12
13
14
Example of AwesomeExample of Crappy
15
Easy to releaseReleasing is simple, safe, painless & mostly automated.Releasing is risky, painful, lots of manual work, and takes forever.
16
Suitable processOur way of working fits us perfectlyOur way of working sucks
17
Tech quality (code base health)We’re proud of the quality of our code! It is clean, easy to read, and has great test coverage.Our code is a pile of dung, and technical debt is raging out of control
18
ValueWe deliver great stuff! We’re proud of it and our stakeholders are really happy.We deliver crap. We feel ashamed to deliver it. Our stakeholders hate us.
19
SpeedWe get stuff done really quickly. No waiting, no delays.We never seem to get done with anything.We keep getting stuck or interrupted. Stories keep getting stuck on dependencies
20
MissionWe know exactly why we are here, and we are really excited about itWe have no idea why we are here, there is no high level picture or focus. Our so-called mission is completely unclear and uninspiring.
21
FunWe love going to work, and have great fun working togetherBoooooooring
22
LearningWe’re learning lots of interesting stuff all the time!We never have time to learn anything
23
SupportWe always get great support & help when we ask for it!We keep getting stuck because we can’t get the support & help that we ask for.
24
Pawns or players (MB Team)We are in control of our destiny! We decide what to build and how to build it. Each person has an equal voteWe are just pawns in a game of chess, with no influence over what we build or how we build it
25
26
27
Good
Green doesn’t necessarily mean things are perfect. It just means the squad is happy with this, and see no major need for improvement right now.
28
Some problems
Yellow means there are some important problems that need addressing, but it’s not a disaster
29
Bad
Red means this really sucks and needs to be improved.
30
31
>better
32
<worse
33
34
More info: https://engineering.atspotify.com/2014/09/16/squad-health-check-model/
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