Topic 05 / 062 articles
What to take over at handover, how much maintenance a launch really needs, and when rewriting beats patching.
Latest
A handover is not a file archive. It is an access inventory, a working environment, and proof that the new team can ship a change on its own. This guide gives the checklist and the one acceptance criterion that "everything has been handed over" does not cover.
The decision to rebuild is made more often than it is justified. Four checks you can run yourself, and the question that separates a technical problem from an organisational one.
The services this topic is relevant to.
Website and system maintenance: what is included and excluded, response versus resolution time, backups, access ownership and handover.
Technical assessment: repair or rebuild, whether to take over a system, why it struggles. The deliverable is a decision with alternatives, not a project.
