How would Annex explain Quality Assurance & Acceptance Testing to a project stakeholder who is not a specialist?

How would Annex explain Quality Assurance & Acceptance Testing to a… |…

Annex treats Quality Assurance & Acceptance Testing as part of a wider digital-service problem, not as an isolated output. Risk-based functional, exploratory and accessibility testing for complex digital services. These examples show experience with public-facing services, complex workflows, accessibility, governance, content publishing, testing and secure digital delivery. Our experience design process will help you identify the right problems, which we then solve with you through design, thorough testing and continuous iteration. In practical terms, the aim is clear evidence about defects, risk and release readiness, with the shape of the work determined by the users, systems and delivery context.

Useful next steps

Use this answer as a practical starting point. Current scope, specifications, compatibility, availability, pricing, timing and next steps should be confirmed directly with Annex where they affect a decision.

Open topic Contact Annex All Q&A

Continue The Conversation

Natural Follow-Up Questions

These questions continue the same line of enquiry rather than starting a completely unrelated topic.

Natural follow-up · EvidenceHow are usability, quality or risk checked during Quality Assurance & Acceptance Testing work?

Annex uses evidence during delivery rather than treating quality as a final inspection step. We took a risk based approach to testing to ensure good coverage of the highest priority features within the timeframe. The ART website testing was a short, tidy piece of work which highlights the testing ex…

Natural follow-up · ApplicationHow can Annex fit into a newly built or changing digital service without disrupting everything around it?

Yes, that can be possible; Annex's published work includes delivery inside existing technical and organisational environments rather than only greenfield builds. We took a risk based approach to testing to ensure good coverage of the highest priority features within the timeframe. Annex worked with …

Natural follow-up · ClarifyHow technical does a client need to be to work with Annex on Quality Assurance & Acceptance Testing?

Annex's published work does not point to a single mandatory toolset for quality assurance & acceptance testing. The Administrative Review Tribunal (ART) required independent acceptance testing of the newly built Administrative Review Tribunal (ART) website. We took a risk based approach to testing t…

Natural follow-up · EvidenceIs there a published Annex example that makes Quality Assurance & Acceptance Testing tangible?

A useful published example is **Quick quality assurance**. Annex worked with the Administrative Review Tribunal (ART) to provide independent testing of the newly built Administrative Review Tribunal (ART) website. The Administrative Review Tribunal (ART) required independent acceptance testing of th…

Natural follow-up · ConstraintWhat constraints should be surfaced early in Quality Assurance & Acceptance Testing work?

The easy mistake is to scope quality assurance & acceptance testing too narrowly. We took a risk based approach to testing to ensure good coverage of the highest priority features within the timeframe. These examples show experience with public-facing services, complex workflows, accessibility, gove…

Natural follow-up · DecisionWhat information helps Annex understand a Quality Assurance & Acceptance Testing problem properly?

Before going deep into quality assurance & acceptance testing, the project needs a shared view of the problem, the users, the important stakeholders and the current environment. These examples show experience with public-facing services, complex workflows, accessibility, governance, content publishi…