Indicators
Indicators
Healthcheck workshops allow a team to record both quantitative and qualitative data about how the team feels across several indicators.
The indicators serve as prompts for discussion and also can be scored against a Red/Amber/Green scale.
The indicators of squad health are:
- Delivering value
- Easy to release
- Fun
- Health of codebase
- Learning
- Mission
- Pawns or players
- Speed
- Suitable process
- Support
- Teamwork
Examples of performance against indicators
| Indicator | Example of performing well against indicator | Example of performing poorly against indicator |
|---|---|---|
| Delivering value | We deliver value - our stakeholders are happy | We deliver little value - our stakeholders are unhappy |
| Easy to release | Releasing is simple, safe, and automated | Releasing is difficult, risky, and involves a lot of manual work |
| Fun | We have a lot of fun | There is no fun |
| Health of codebase | The code is clean, maintained, and has good test coverage | There is a lot of technical debt, the application is lacking in test coverage |
| Learning | We are always learning new things | We never learn anything new |
| Mission | We know why we are here and what we are working towards | We have no idea why we are here. There is no clear mission |
| Pawns or players | We decide what to build and how to build it | We have no influence over what to build or how to build it |
| Speed | We get stuff done quickly | We are often blocked by dependencies |
| Suitable process | Our way of working fits the team well | Our way of working conflicts with how the team wants to operate |
| Support | We get great support when we need it | We never get the support we need and request |
| Teamwork | We have good close collaboration in the team | We operate as individuals with little collaboration |