Welcome to the Team Health Check App!

Team (Squad) health check web application is a tool for quick assessment and visualization of how Agile teams perform in three aspects: tech health, team health, and product health. It uses a set of behaviour anchors on relevant themes for a high performing team to discuss and capture sentiment. For each question or theme, the team/squad discusses if they are closer to “awesome” or closer to “bad”, which colour to choose for that indicator, and what the trend is (stable, improving, or getting worse). For example, the theme "can we release easily?" might elicit responses of "our releases are good/meh/bad" i.e. green, amber and red, the colours of a traffic light.

GREEN: Things are going very well. Although this does not mean that everything is perfect the team or squad is satisfied and does not see much space for improvement.
AMBER: There are some problems that need to be solved. However, it is not a disaster.
RED: There is a lot going wrong. Improvements are urgently needed.

The main purpose of this model is to help teams build up self-awareness about what's working and what's not, and to identify improvement opportunities. It also provides leaders with a way to support, not judge, teams. The app gathers feedback from everyone in real time and calculates the results. The results are displayed in a multi-team-level visualization, so that patterns and trends can be observed and addressed. The app can also keep a track of the squads progress over time without the need for manual collation.

Following are the detailed descriptions of the behavior anchors:

  1. Delivering value
    • Good: We deliver great stuff! We're proud of it and our stakeholders are really happy.
    • Bad: We deliver bad quality. We are not proud of it and our stakeholders unhappy.

  2. Codebase Health
    • Good: We're proud of the quality of our code! It is clean, easy to read and has great test coverage.
    • Bad: Our code is messy and difficult to maintain.

  3. Task Planning And Priority
    • Good: I'm clear about the planned tasks and its priority in my backlog.
    • Bad: I'm not clear about my assigned tasks and its dependencies and I'm unsure if I can deliver on commitments.

  4. Information sharing
    • Good: We always have the right information about changes/decisions that affect out work.
    • Bad: We never receive updates consistently and this affects our day to day work

  5. Team Work
    • Good: We are a great team that works great together. We respect each other and share appreciation for the good work.
    • Bad: We are a bunch of individuals who neither know nor care what the others on the team are doing.

  6. Events
    • Good: Our meetings including standups, planning, reviews and retrospectives are regular and effective.
    • Bad: Our meetings are ineffective and do not follow a regular cadence.

  7. Learning and Fun
    • Good: We are constantly learning new things and from our mistakes, upskilling ourselves along the way. We love our work and we have a lot of fun together.
    • Bad: The work is boring and we never have time to learn anything. Worse yet, we never learn from our mistakes.

  8. Pawns or Players
    • Good: We are in control of our own destiny! We hava autonomy with purpose and mastery of our competence areas and decide what to build and how to build it.
    • Bad: We are just pawns in a game of chess with no influence over what we build or how we build it.

  9. Product Ownership
    • Good: We are happy with the current state of our backlog and its relevance to the business.
    • Bad: Our backlog is messy and does not seem to deliver value for its stakeholders.

  10. Speed And Incremental Deliveries
    • Good: We get stuff done really quickly! No waiting and no delays.
    • Bad: We never seem to get anything done. We keep getting stuck or interrupted. Stories keep getting stuck on dependencies.

  11. Easy to release
    • Good: Releasing is simple, safe, painless and mostly automated.
    • Bad: Releasing is risky, painful, lots of manual work and takes forever.

  12. Suitable processes
    • Good: Our way of working fits us perfectly.
    • Bad: Our way of working sucks!

  13. Tooling
    • Good: We are agile use productivity and engineering tools effectively to deliver greater value
    • Bad: We are unable to use contemporary tools and are stuck with old legacy tools.

  14. Support
    • Good: We always get great support and help when we ask for it!
    • Bad: We keep getting stuck because we can't get the support and help that we ask for.

  15. Manager Leads Team by Example
    • Good: Our manager always leads by example and can be trusted to follow through on promised actions
    • Bad: Our manager does not communicate effectively and cannot help team to deliver value.