On-site delivery: making go-live rollback plan stick
{pboot:if('Context: Last week we reviewed test case review with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but '!='')}Context: Last week we reviewed test case review with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but
{/pboot:if}Context: Last week we reviewed test case review with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but test case review 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.
Delivery Approach
Last week we reviewed contract milestones with the client's IT lead. They care more about stability than buzzwords. We hit a case of payment succeeded but orders still pending. Troubleshooting started with logs on Flutter, then followed our reproduction steps. Next, we recommend to compare staging vs production configuration diffs. If more features are added, scope the blast radius before scheduling. This write-up is for colleagues progressing project delivery. The client is in food & beverage, roughly two hundred+ staff, based around new urban centers. We hit a case of mini program review rejected. Troubleshooting started with logs on WeChat DevTools, then followed our reproduction steps. Next, we recommend to log API status codes and latency. If more features are added, scope the blast radius before scheduling.
Risks & Mitigations
The same requirement can sound different across departments; writing it down helps align decisions on contract milestones. QA walked the main path three times on real devices and flagged edge cases around contract milestones. Archive screenshots and config change IDs for this contract milestones round so next month's retrospective stays concrete. The same requirement can sound different across departments; writing it down helps align decisions on data migration windows. Editors know the CMS well enough, but data migration windows still needs a one-page rule sheet to cut verbal rework. Add a field dictionary to the docs so new joiners ask fewer repeat questions.
Operations & Collaboration
The same requirement can sound different across departments; writing it down helps align decisions on monitoring alert thresholds. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to monitoring alert thresholds first. Prefer a go-live window outside peak traffic, and prepare the rollback package early. The same requirement can sound different across departments; writing it down helps align decisions on go-live rollback plan. We hit a case of a teammate accidentally deleting a channel. Troubleshooting started with logs on CDN, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early.
Takeaways: This write-up is for colleagues progressing project delivery. The client is in industrial equipment, roughly about thirty people, based around new urban centers. We hit a case of legacy outbound links broken. Troubleshooting started with logs on Git, then followed our reproduction steps. Prefer a go-live window outside peak traffic, and prepare the rollback package early.