As mentioned in the earlier question, sprint retrospective is an opportunity to inspect and adapt the process. Thus, checking the team’s health at this meeting can be a good opportunity. The team should together this time look at the areas of improvement and talk about the overall health.

The Scrum Master can facilitate the health check through various tools, simple can be using a scale from 1-5 where 1 STANDS for awful and 5 for extraordinary. They can even use the TeamHealth Retrospective which is a powerful deep-dive strategic retrospective tool that FOCUSES on the top areas that affect team performance and health.

To check the team health, the team can COME up with the parameters to check on the health – Culture, Technical Practices, Quality, Backlog Visibility, and Team Collaboration. The team can have its own customized parameters and against those parameters, there will be some points to validate that parameter. The team, after discussion, gives a point on the scale of 1-10 to that parameter. The same goes for all the parameters. Once this activity is done, the tool will automatically generate a SPIDER chart showing the areas that need improvement. The Scrum Master can coach and suggest the team on how to REACH the 5 in the spider!