team health check (13 FAQs)

Agile maturity assessment can be well combined with retrospectives by answering health check questions before or at the start of the retro and reflecting on the results directly as a team.

The process is simple:

1. The team answers a few statements on a scale.
2. The results are made visible in the retrospective.
3. The team discusses anomalies and causes.
4. 1 to 2 concrete actions are agreed upon.
5. In the next measurement, it is checked whether anything has improved.

This keeps the measurement close to daily work and prevents it from becoming a purely reporting tool.

Good questions in an Agile Maturity Assessment are concrete, observable, and action-oriented. Examples are:

• We obtain feedback from customers or stakeholders early enough.
• Our team works on clearly prioritized goals.
• We can make decisions independently within our area of responsibility.
• Critical observations are raised openly and constructively.
• Actions from retrospectives are tracked visibly.
• We reduce the causes of errors rather than just fixing symptoms.

Ideally, the responses should be collected on a scale and then reflected on in a retrospective.

In practice, a rhythm of 6 to 12 weeks makes sense. This gives teams enough time to implement measures without the measurement becoming too infrequent.

For an initial baseline, 3 steps are often enough:

1. Short health check.
2. Reflection in the retrospective.
3. Follow-up measurement after 1 to 3 sprint cycles.

Monthly measurements can make sense if the questions are very short. Too frequent, lengthy assessments, on the other hand, quickly lead to survey fatigue.

Agile maturity and Agile Maturity essentially mean the same thing: how far an organization or a team lives agile principles effectively in everyday work.

“Agile maturity” is the German term. “Agile Maturity” is often used in international frameworks, assessments, and tools.

More important than the term is the measurement logic: good Agile Maturity assessments measure not only processes, but also learning ability, customer proximity, collaboration, quality, and leadership.

The agile maturity of teams should not be compared as a ranking. Teams work under different conditions, for example with different products, dependencies, legacy systems, or stakeholders.

A trend comparison within the same team makes sense: Has the value improved since the last measurement? Which measure helped? Which blockage is still visible?

Patterns across teams can still be valuable if they are used to identify systemic obstacles, not to evaluate teams.

A pragmatic 5-stage model for agile maturity looks like this:

1. Reactive: Work is highly ad hoc, learning happens incidentally, and retrospectives have little impact.
2. Repeatable: Agile rituals are in place, but quality and commitment fluctuate.
3. Established: Team processes function reliably and improvements are implemented regularly.
4. Data-driven: Decisions are backed by metrics, feedback, and observation.
5. Learning: Continuous improvement is firmly anchored in the team and leadership culture.

The stages should serve as guidance, not as a rigid evaluation system. What matters is the trend within a team.

Agile maturity is measured using a combination of team feedback, delivery metrics, quality data, and observable changes in behavior.

A practical sequence is:

1. Define the goals of the agile transformation.
2. Select 4 to 6 relevant dimensions, for example customer orientation, delivery, quality, team autonomy, learning culture, and leadership.
3. Establish a baseline through a health check, metrics, and qualitative observation.
4. Reflect on results in retrospectives.
5. Derive 1 to 2 concrete actions per team.
6. Measure again after 6 to 12 weeks and compare the progress within the same team.

Important: A maturity assessment is only useful if it is translated directly into improvement steps. A score alone does not improve agility.

Metrics from four perspectives are useful:

• Delivery: Lead time, delivery frequency, predictability.
• Quality: Defect rate, rework rate, technical stability.
• Team: Psychological safety, clarity, collaboration.
• Customer value: Feedback cycles, perceived added value, satisfaction.
• Improvement: implemented retro actions, removed blockers, tested experiments.

The key is the combination: individual metrics can be misinterpreted. Only the mix of hard and soft indicators provides a robust picture of the agile maturity level. Velocity is not suitable for team comparisons.

Yes, you can conduct anonymous surveys in Echometer. You can create a survey and then share the link to the survey. Anyone with access to the link can participate in the survey anonymously, without having to register beforehand.

Yes, you can automate team surveys via pulse checks in Echometer. To automate surveys in Echometer, first select the questions for the pulse check, then select the start date and then the frequency at which this survey should be sent.

You can either send the survey to all teams in your workspace or exclude individual teams from the pulse checks.

Yes, you can record the psychological safety of your team in Echometer with Health Checks. Echometer has a template for retrospectives as well as various items in the Health Check item pool. You can therefore configure the measurement individually and decide for yourself whether you want to collect the measurement as part of a retrospective or as part of a survey.

Yes, with Echometer you can measure Team Happiness and Team Morale. You can use the Health Checks in Echometer and incorporate them into your team retrospectives or surveys.

Yes, you can collect and measure the eNPS (Employee Net Promoter Score) in Echometer’s Health Checks and surveys for retrospectives.

The eNPS can be evaluated in Echometer both at team level and across teams. For example, you can use the heat map in the Workspace Health Dashboard for cross-team evaluation.