Enterprise Testing Framework & Quality Assurance Strategy
Case Study
About Our Client
Overview
Our client is a state-owned water and sewerage utility delivering critical services across its region. Over the preceding three years its Digital and Technology department had been working through a structured transformation program, building project delivery, architecture, and business analysis capabilities from a low baseline and moving to a squad-based agile delivery model. Testing and quality assurance was the final capability gap. Testing had been ad hoc — executed off the side of developers’ and configuration engineers’ desks, with no formal methodology, no test management tooling, and no structured user acceptance testing process. With a finance system replacement underway, an active cloud migration program, and a growing pipeline of customer-facing and vendor-led projects ahead, the client needed to establish a structured QA capability it would own outright.
The Challenge
A critical capability gap in a maturing delivery organisation
The client had built strong delivery, architecture, and analysis capabilities, but quality assurance had not kept pace. Testing was informal and inconsistent, and defects had already reached production — including integration failures during an earlier platform implementation. With several high-stakes programs in flight and heavy reliance on external vendors, the risk of continuing without a structured QA capability was real and growing.
Key challenges included:
- Ad hoc, inconsistent testing with no formal methodology, no test management tooling, and no structured UAT process, creating variable delivery quality across teams.
- Defects reaching production on critical public-facing systems — including billing, meter checking, and payment tools — where failures have direct community impact.
- A high-stakes finance system replacement, an active cloud and SaaS migration, and a pipeline of vendor-led projects all depending on a quality baseline that did not yet exist.
- Growing reliance on multiple external vendors delivering simultaneously, introducing integration complexity and a need for clear vendor accountability.
- A framework that had to be adoptable by an incoming QA lead who was not yet hired — meaning every decision needed to be documented with its rationale, not just its outcome.
- A firm requirement to be left entirely self-sufficient, with no ongoing dependency and no locked-in intellectual property.
Services:
- Enterprise Testing Methodology & Governance Design
- Quality Assurance Strategy Document
- Reusable Test Artefacts & Templates (Program and System Level)
- Testing Levels with Entry & Exit Criteria (SIT, UAT, Regression, Non-Functional)
- Defect & Risk Management Process
- Requirements Traceability & Test Reporting/Metrics Practices
- Tooling Assessment & Future-State Roadmap
- Knowledge Transfer & Full Capability Handover
Sector
Utilities / Water (Critical Public Infrastructure)
The Approach
Designing a capability the organisation owns outright
Avocado applied its outcome-focused delivery model, working collaboratively with the client’s team to design a testing capability the organisation would own completely — one that worked for the teams using it today and could scale as the program grew. Every design decision was risk-based, traceable to a real requirement, and documented with its rationale so the incoming QA lead would understand not just what was built, but why. The engagement was structured across discovery, methodology and framework design, artefacts and tooling, and knowledge transfer:
Discovery & current-state assessment: A structured review of existing testing practices, tools, and maturity, including stakeholder interviews and a gap analysis mapped against the client’s own digital project delivery framework, to ground the design in real risks and requirements.
Methodology & governance design: Definition of an enterprise testing methodology covering principles, roles, responsibilities, and governance, aligned to the client’s squad-based delivery model — including how testing engages early in delivery cycles and how shift-left principles apply across both squad and vendor-led programs.
Testing levels & entry/exit criteria: Clearly defined testing levels with explicit entry and exit criteria for system integration, user acceptance, regression, and non-functional testing, giving every team a consistent, repeatable baseline to follow.
Defect, risk, traceability & reporting: A defect management process covering classification, severity, triage, and escalation; a risk management framework aligned to the delivery model; a requirements traceability approach linking test cases to business requirements and surfacing coverage gaps; and defined reporting and metrics practices covering how testing is evidenced and how metrics support continuous improvement over time.
Reusable artefacts & templates: A library of program- and system-level test plan templates, test case and defect log templates, environment readiness checklists, and test data management guidance — designed to work across squad, vendor-led, and hybrid delivery, and ready to use from day one without a testing expert to interpret them.
Standards & tooling: The framework was built to ISTQB testing standards — a recognised industry benchmark any qualified QA professional can build on — supported by an assessment of the existing tooling environment and a technology-agnostic, JIRA-compatible future-state recommendation and roadmap, honest about what the organisation actually needed at its current maturity rather than adding unnecessary complexity.
Knowledge transfer & handover: Knowledge transfer embedded throughout rather than bolted on at the end — sharing context and involving the client’s team at every milestone — culminating in structured handover sessions, plain-language process guides written for non-specialists, a full artefact library, and a recommendations document written specifically for the incoming QA lead.
The Result
A foundation the organisation can build on independently
The engagement was designed to move the client from ad hoc, developer-led testing to a structured, enterprise-wide quality assurance capability owned entirely in-house — addressing its final transformation capability gap.
- The framework was built to give every team a standardised, repeatable testing baseline that could be applied consistently whether work was squad-delivered, vendor-led, or hybrid.
- Clear entry and exit criteria, defect triage, and governance checkpoints were designed to strengthen vendor accountability across a growing pipeline of external delivery partners.
- Explicit testing levels, coverage expectations, and sign-off processes were built in to improve go-live confidence and reduce the risk of defects reaching critical public-facing systems.
- With every decision documented alongside its rationale, the framework was designed to be inherited and extended by an incoming QA lead from day one, rather than creating a dependency on Avocado.
- Structured knowledge transfer and full ownership of all artefacts were built in from the outset, leaving the organisation entirely self-sufficient with no locked-in intellectual property.
Overall, the engagement was designed to give the client a pragmatic, reusable quality assurance foundation — one that fits its current maturity, scales with its transformation program, and remains fully in its own hands.
