Free Self-Assessment
Project Health Check
12 questions on agility, teamwork and risk, scored against published agile maturity models. You get a personal assessment and the areas that need work.
AI-generated assessment: a general indication, not legal or professional advice.
What a project health check measures
A project counts as healthy as long as the status report stays green. That is precisely the problem: the report measures what gets reported, not what happens. Projects rarely fail suddenly. They fail slowly, and the signs show up weeks earlier in behaviour everyone sees and nobody writes down.
So this check asks about behaviour rather than opinion. Not “is communication good?”, but what actually happened the last time something went wrong. Twelve questions, three dimensions, and answer options that describe behaviour.
The three dimensions
- Agility & methodology (35%)
- Is the chosen approach actually practised or merely reported? A team with a daily stand-up and a six-month release cycle is not working in an agile way; it has an agile ritual.
- Team & communication (35%)
- Does anyone hear about a problem while it is still small? The measure behind this is not mood but the lag between “someone suspects something” and “it is on the table”.
- Risk & control (30%)
- Are there risks with a name, an owner and a date or a list that gets refreshed for the steering committee? A risk without an owner is a note.
Frequently asked questions
What does the project health check cost?
Nothing. Twelve questions, about five minutes, and you see the result straight away. Your name and email address come to me with your result, so I can answer any follow-up questions.
What is the assessment based on?
The Agile Maturity Index (Sidky et al., 2007) and the Agile Adoption Framework (Qumer & Henderson-Sellers, 2008). The questions draw on PRINCE2 and AgilePM. Both models describe maturity in stages rather than as a yes-or-no test.
Does it work for traditional projects too?
Yes. Two of the three dimensions — team and risk — assume no agile approach at all. The agility dimension does not measure whether Scrum is in use, but whether change reaches the project before it is too late. That question is just as meaningful in a waterfall setting.
Is a self-assessment enough to judge a project?
No, and it is not meant to be. One person answers twelve questions from their own vantage point — that is a hypothesis, not a diagnosis. It becomes useful when several people on the project take the same check and discuss where their answers diverge. That gap is usually the real finding.
What do I do with the result?
Look at the weakest dimension first, not the overall score. A low control score cannot be fixed with more meetings, and a low communication score cannot be fixed with another tool. The evaluation names a concrete area to act on for each dimension.