On-site delivery: making backup and recovery drills stick

Context: Last week we reviewed backup and recovery drills with the client's IT lead. They care more about stability than buzzwords. We hit a case of legacy outbound links broken. Troubleshooting started with logs on a hosting panel, then followed our reproduction steps. Archive screenshots and config change IDs for this backup and recovery drills round so next month's retrospective stays concrete.

Background & Goals

This write-up is for colleagues progressing project delivery. The client is in beauty & wellness, roughly a dozen staff, based around high-tech zones. We hit a case of a teammate accidentally deleting a channel. Troubleshooting started with logs on Postman, then followed our reproduction steps. Add a field dictionary to the docs so new joiners ask fewer repeat questions. The same requirement can sound different across departments; writing it down helps align decisions on weekly status cadence. We hit a case of legacy outbound links broken. Troubleshooting started with logs on Flutter, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Risks & Mitigations

The same requirement can sound different across departments; writing it down helps align decisions on prototype sign-off checkpoints. QA walked the main path three times on real devices and flagged edge cases around prototype sign-off checkpoints. Next, we recommend to store backups in a separate folder with dated labels. If more features are added, scope the blast radius before scheduling. This write-up is for colleagues progressing project delivery. The client is in property & industrial parks, roughly two hundred+ staff, based around county-level cities. We hit a case of a teammate accidentally deleting a channel. Troubleshooting started with logs on Nginx, then followed our reproduction steps. Archive screenshots and config change IDs for this acceptance checklist round so next month's retrospective stays concrete. Last week we reviewed contract milestones with the client's IT lead. They care more about stability than buzzwords. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to contract milestones first. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Operations & Collaboration

Last week we reviewed training and handover with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around training and handover. Next, we recommend to temporarily disable noncritical plugins and retest. If more features are added, scope the blast radius before scheduling. Last week we reviewed data migration windows with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but data migration windows still needs a one-page rule sheet to cut verbal rework. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed prototype sign-off checkpoints with the client's IT lead. They care more about stability than buzzwords. QA walked the main path three times on real devices and flagged edge cases around prototype sign-off checkpoints. Add a field dictionary to the docs so new joiners ask fewer repeat questions.

Takeaways: Last week we reviewed test case review with the client's IT lead. They care more about stability than buzzwords. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on a hosting panel, then followed our reproduction steps. Archive screenshots and config change IDs for this test case review round so next month's retrospective stays concrete.