OneSystems supplies software to its own clients. One of those systems was mission-critical to the client’s operations and had reached the state where code quality was producing consequences. Agile Labs ran a four-phase rescue: assessment, remediation, support, then enhancement.
The system carried vulnerabilities, performance limits and reliability that could not be relied on.
The commercial position matters here. The system was not an internal tool. It sat inside a client relationship, which made the problem reputational before it was technical, and it could not be taken offline while it was fixed.
Four phases, in order, with assessment first. Adding features to an unstable system is how the instability becomes permanent.
An in-depth review of the existing system, which identified numerous vulnerabilities ranging from mid to high priority. This established what was wrong before anything was changed.
Targeted remediation against the assessment findings: code refactoring, security fixes and performance work. This phase stabilised the system.
Ongoing monitoring after the upgrades, addressing issues as they emerged. This phase is what prevents recurrence, and it is the part most rescues omit.
New functionality for the end client’s evolving needs, and scalability improvements. This came last, after control was re-established.
The system was returned to a secure, stable and supportable condition, and OneSystems was able to continue extending it for its client.
The vulnerabilities were found by looking. They had not been reported by users or flagged by an incident. An inherited system carries the problems nobody has gone looking for, and the assessment is what moves them from unknown to scheduled.
Build better software, with zero surprises