How a software takeover begins
Review the project you have before committing to a completion plan or a rebuild.
1. Identify the missing handoff
Tell us what the software was intended to do, where work stopped and which files or accounts you have. We also discuss any deadline and the first task your business needs working.
2. Review the code and accounts
We check the available source, hosting and connected services. Missing account access is recovered through the owner or provider. Any uncertainty about the right to use the software needs to be resolved before the affected work begins.
3. Run and check the available version
Where possible, the project is built on a separate test system. We compare it with the live version and try important tasks. Live payments and customer messages are kept out of routine testing.
4. Compare the options
The findings help show whether to repair, finish in stages or rebuild. You see what is known, what is still uncertain and what each proposed stage would deliver.
Read about repair and rebuild decisions5. Agree on the next stage
Before work proceeds, agree on the changes, checks, data to preserve and release steps. The handoff should explain how the updated system runs and how future changes are made.