Failing IT projects rarely recover by working harder on the same plan. Learn a structured recovery sequence — confirm viability, reset expectations, redefine done, fix the backlog and control work in progress — and why the order matters more than any single fix.
Watch the free preview
How to tell a project is failing, not just struggling — free to watch, no account needed.
What you'll learn
- Recognise the early signals that an IT project is failing rather than merely struggling
- Explain why tactical fixes fail when applied before viability and expectations are addressed
- Apply a structured recovery sequence in the correct order to stabilise a troubled project
- Redefine done, triage the backlog and control work in progress to restore predictable flow
- Produce a credible Project Recovery Plan a steering committee can approve
Syllabus
Why Failing Projects Resist the Obvious Fixes
How to tell a project is failing, not just strugglingFree preview
Why tactical fixes fail before viability is addressed
The Recovery Sequence in Depth
Confirm viability and reset expectations first
Redefine done, fix the backlog, control WIP
Leading a Real Recovery
Leading the stabilisation and the people through it
Case study — the project that missed three dates
Making the Recovery Stick
Building your Project Recovery Plan
Recovery traps and anti-patterns to avoid