The last sprint problem
On most projects the handover is a meeting in the final week: a shared screen, a tour of the repository and a long document nobody opens again. Six months later the client's team is afraid to touch the code.
We now plan the handover in the first week, because it changes how we build everything after it.
What changes
- The repository lives in your account from day one. Our engineers are guests in it, never the other way round.
- Decisions are written down as they happen, in short notes beside the code, not reconstructed at the end.
- Your engineers review our pull requests from the first month, even if they only read them.
- The last two weeks are spent side by side, with your team making the changes and ours watching.
Good code that only its authors understand is still a liability.
What it costs
Very little. The notes take minutes, the reviews take an hour a week. What it saves is the quiet rewrite a new team starts when it does not trust what it inherited.
