Stabilising a showroom application that had lost user confidence
A global automotive retailer's online sales division was running a customer-facing showroom application that had become unstable, denting user confidence and blocking further enhancement. We opened with a short, focused system review — auditing existing documentation, reverse-engineering the codebase to identify core weaknesses, reviewing open demands and known issues, and assessing the current operating model — to produce a prioritised, evaluated list of stability improvements. That fed directly into an ongoing stabilisation, maintenance, and evolution phase: a scrum-based team designing, building, and testing fixes and enhancements against those priorities, running second- and third-line support and incident handling, and setting up a formal SLA and system roadmap agreed with the application owner. The team scales up or down on request as demand changes, so support effort tracks actual need rather than a fixed headcount.