What is a software project rescue?
A software project rescue is for a project that has stopped converging: the deadline has moved twice, the last 20% has taken longer than the first 80%, and the vendor's answers no longer add up. An outside developer finds out where the project really stands, takes it over from the vendor if that is the right call, and gets it to a finish line you can hold someone to.
Based in Vancouver, BC, on-site around the Pacific Northwest, and working remotely with clients across Canada and the US.
How a rescue works
1. An honest status check
"80% done" usually means 80% of the screens exist. I look at the code, the infrastructure and the open issues, talk to the people, and tell you what is actually finished, what is not, and what was never started.
2. Taking over from the vendor
If the vendor stays, you get a clear list of what they owe you. If they go, the handover is planned: the source code, the hosting and domain accounts, the credentials, the build and deployment steps, and the documentation all move to you before the relationship ends.
3. A recovery plan
A written plan that ranks what to fix first, what to cut, and what to finish, with the process changes that stop the same slide from happening again.
4. A fixed-price next phase
The next phase of work is quoted at a fixed price after the audit, against a scope we both understand, so the number stops moving.
Start with the Software Project Audit
Every rescue starts with the Software Project Audit: a fixed-price investigation of the people, the process and the code. Its report is the status check, and its recommendations are the recovery plan. If an audit isn't the right next step, the free pre-audit will say so.
Let's Talk
To talk about a project in trouble, get in touch and tell me where it stands.
Not sure whether it needs rescuing or just a firmer hand? Tell me what's stuck and I'll tell you honestly.
Have a question that hasn't been answered here? Check the FAQ.