Is this project actually in trouble?
Ten questions about how your project really runs. You get a score, the areas to fix first, and what to do about them.
- 10 questions
- 5 areas
- about 4 minutes
- stays in your browser
What's included
Ten questions across five areas, about four minutes to work through:
1. Delivery & Release
- How often you release to production
- How stressful a deployment is
2. Code Quality & Testing
- Automated test coverage
- How much development time goes on bugs rather than features
3. Team & Capability
- Team morale
- Your bus factor, meaning how many people could leave before critical knowledge goes with them
4. Architecture & Design
- How well the architecture is documented
- Whether the system would take ten times the current load
5. Process & Communication
- Whether requirements are clear before development starts
- Whether stakeholders agree on priorities
You get: a score out of 100, a one line reading of what that score means, a percentage for each of the five areas with the weak ones named, the warning signs your answers raised, what is working, and a short list of what to do in order.
Nothing is stored and nothing leaves your browser unless you choose to send it to me.
Who it's for
This assessment is designed for technology leaders and stakeholders who suspect their software project isn't performing as well as it should, but aren't sure where the problems lie.
Project Managers - You're managing delivery but sense something is wrong. Deadlines keep slipping, estimates are consistently off, and you need an objective framework to identify where the real problems are hiding.
CTOs and Technical Directors - You're overseeing multiple projects and need a consistent way to evaluate health across your portfolio. This assessment gives you a structured diagnostic you can apply to any project in minutes.
Founders and CEOs - Your tech project is consuming more budget and time than planned, but your team assures you everything is "nearly done". Get an honest reality check on where things actually stand.
Product Owners - Delivery is unpredictable and you can't plan releases with confidence. Understand the root causes behind the chaos so you can have informed conversations with your development team.
Agency Owners - Client projects are running over budget and your team is firefighting constantly. Identify systemic issues affecting delivery before they damage client relationships.
If you've ever thought "I wish I knew whether this project was actually on track", this assessment will give you an answer in about four minutes.
The assessment
0 of 10 answered
0 of 10 answered
Questions about this assessment
How long does the Project Health Assessment take to complete?
- About four minutes. There are ten questions, each one a single choice, and no free text anywhere. Answer them on how the project actually runs rather than how it is meant to run: the result is only worth having if the answers are honest.
What score indicates a project needs external help?
- The assessment scores out of 100 and reads that score in four bands. 80 and above is Healthy. 60 to 79 is Some strain, meaning the project works but something is costing you. 40 to 59 is In trouble, where several things are wrong at once and compound each other. Below 40 is Failing, and that is not a tuning problem. Any individual area scoring below 70 is called out separately as needing attention, because an overall score can hide one badly broken area behind four good ones. The tool also computes an A to F grade from the same number (A is 90 and above, B is 75, C is 60, D is 40, F is below 40) and sends it with the emailed result, though the page itself shows you the score and the bands rather than the letter.
What causes software projects to fail?
- Common causes include unclear requirements, technical debt accumulation, poor team communication, inadequate testing, and stakeholder misalignment. The assessment helps identify which specific areas are contributing to your project's challenges so you can focus improvement efforts effectively.
Can a struggling project be turned around?
- Yes, most struggling projects can be rescued with the right intervention. The key is honest assessment of the current state, prioritising the most critical issues, and bringing in experienced leadership to guide the turnaround. Early intervention improves success rates significantly.
How often should I reassess project health?
- We recommend reassessing every 6-8 weeks to track improvement progress. Regular assessment helps identify emerging problems early before they become critical and validates that improvement efforts are having the desired effect.