How to accept a project from a developer: the code, the access, the check
Acceptance is not a feeling that it sort of works. It is a short list you can walk through without the author.
AVERIQ · · 2 min read
A project is easy to accept on the feeling of the moment. In the demonstration everything can be pressed, and the author is beside you, prompting. A month later a text needs changing, or a role needs adding. There is no repository. The server password is in a private chat. And “it only builds on my machine.” A sound handover does not allow that.
Walk the scenario yourself
Open a clean browser, or another role, and walk the action you agreed would count as the handover. Check the empty list, an error in the form, and the phone as well. If the author takes the mouse at every step, the scenario is not ready.
Take the code, and the ability to build it again
- The repository belongs to the company, not to the contractor's personal account.
- The repository contains no passwords, no keys, and no dumps of the live database.
- There is a guide: how to install it, what to put in the environment, and how to release it.
- It is clear which version is on the server now.
Access is not stacked into one message
The domain, the hosting, email, analytics, the payments account, and the database are different keys. They stay with you. The contractor is given access for the time of the work, and that access is revoked when the work is finished. A shared password kept “just in case” means that later nobody remembers who else still uses it.
Write down what is not there
The list of what was left out matters as much as the list of what was done. Otherwise a forgotten idea turns into a complaint a week later. If a queue of small changes is needed after acceptance, that is already support, not an endless handover of the same project.
The minimum worth keeping yourself: the repository, a guide to launching, access to the infrastructure, the acceptance scenario, and a list of what was postponed on purpose.