Qu’est-ce qu’un Bilan de santé d’équipe Agile et pourquoi sont-ils importants ?

A team health check is a simple tool that helps you measure and track team health and happiness over time; the data they capture can inform actions that drive continuous improvement.

Team health relates to the factors that contribute to team success.

There’s been considerable effort dedicated to defining those factors thereby paving the way to enhancing them.

Google’s research, cites five factors that are pivotal to team success.

Spotify’s work in this space informed their Squad Health Check. Having evolved over time, the 11 dimensions of their check reflect the factors they perceive as key to team health.

The great thing is, you don’t have to launch a research program to measure and nurture your team’s health.

Les bilans de santé d’équipe Agile sont des mécanismes exceptionnellement précieux pour deux raisons principales –

• The information they capture can help inform data-driven actions designed to improve team health.
• The effectiveness of those actions can be tracked over time.

Why is team health important?

A healthy, happy team team can benefit –

• Employers
• Employees
• An employee’s family

We know our health is important.

We know our health relates not only to our physical selves and what we can do, but also our emotional selves and how we feel.

We know if we feel good, we can do more.

Well, the same can be said of team health.

The health of the team is a culmination of the quality of their communication, culture and camaraderie which then impacts upon productivity, velocity, and ease of collaboration when it comes to hitting team goals.

Taking some time to understand and measure the health of your team can therefore lead to insights regarding what might be impacting their systems and what drives continuous improvement.

How can you improve your team’s health?

Decide on your dimensions

It’s important to determine what matters most to you and your team (within your context), as this will inform the dimensions you choose to use in your health check. A great way to define these dimensions is to speak with key stakeholders – this includes your team.

TeamRetro propose une gamme de modèles avec des dimensions préchargées pour te lancer. Du Bonheur des équipes à distance, aux modèles Spotify ou Atlassian, en passant par le bilan de santé des Valeurs Scrum, tu peux utiliser ces modèles tels quels ou les modifier pour les adapter aux besoins de ton équipe.

TeamRetro te permet d’appliquer tes dimensions pour construire tes propres modèles de bilan de santé. You can, in fact, create multiple models and set a default model.

Plus important encore, TeamRetro t’aide à suivre la réponse de ton équipe à ces dimensions sur une période donnée, capturant ainsi l’évolution de la santé de ton équipe.

Create a cadence

You could set a health check schedule that could range from daily through to annually but it’s important to set some sort of regular cadence that informs how you want people to respond and share.

Keep in mind that faster, shorter health checks will let you see trends and validate team health in a more timely and relevant way.

You can run your health checks synchronously or asynchronously.

If you choose to facilitate asynchronous checks, it’s a good rule of thumb to ensure –

• That the health dimensions are understood
• You have set the tone for how you want people to respond to health checks
• What happens with the data is known and understood

Making team health checks a regular occurrence and with the right message, helps build trust and psychological safety, thereby creating a space in which –

• Feedback is embraced as constructive rather that perceived as a criticism
• Issues are identified and quickly addressed
• The positive relationships between team members are reinforced
• Conversations are open, honest and supportive

Measure and Manage

The last step is all about connecting your team and transparency is key.

1. Share the results of that first health check with your team.
2. Acknowledge and celebrate successes.
3. Explore any issues the health check may have identified.
4. Ask your team for their input as to how team health could be improved.
5. If relevant, use the artefacts of your health checks as the theme for your next retrospective.
6. Capture actions or team agreements that the team would like to take going forward.