Website project retrospective: brand site launch (a hundred-person team)

Context: Last week we reviewed company website development 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 company website development first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Testing & Acceptance

This write-up is for colleagues progressing website and CMS work. The client is in media & creative, roughly two hundred+ staff, based around Europe. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to landing page SEO basics first. Next, we recommend to document the reproduction path in a shared sheet. If more features are added, scope the blast radius before scheduling. The same requirement can sound different across departments; writing it down helps align decisions on company website development. We hit a case of sales never receiving emails after form submit. Troubleshooting started with logs on Flutter, 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. This write-up is for colleagues progressing website and CMS work. The client is in education & training, roughly about thirty people, based around East Asia. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to landing page SEO basics first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Delivery Approach

Last week we reviewed basic accessibility 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 basic accessibility. Prefer a go-live window outside peak traffic, and prepare the rollback package early. Last week we reviewed company website development with the client's IT lead. They care more about stability than buzzwords. Editors know the CMS well enough, but company website development 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.

Operations & Collaboration

The same requirement can sound different across departments; writing it down helps align decisions on image weight control. We hit a case of captchas frequently failing to load. Troubleshooting started with logs on Git, then followed our reproduction steps. Archive screenshots and config change IDs for this image weight control round so next month's retrospective stays concrete. This write-up is for colleagues progressing website and CMS work. The client is in textile & apparel, roughly about thirty people, based around North America. QA walked the main path three times on real devices and flagged edge cases around basic accessibility. Next, we recommend to require a change request for any scope change. If more features are added, scope the blast radius before scheduling. This write-up is for colleagues progressing website and CMS work. The client is in manufacturing, roughly around fifty employees, based around coastal tech hubs. Business asked for a clickable prototype within two weeks, while engineering wanted to lock fields related to image weight control first. Prefer a go-live window outside peak traffic, and prepare the rollback package early.

Takeaways: The same requirement can sound different across departments; writing it down helps align decisions on multilingual website build. Editors know the CMS well enough, but multilingual website build still needs a one-page rule sheet to cut verbal rework. Archive screenshots and config change IDs for this multilingual website build round so next month's retrospective stays concrete.