In stages (V-model)
For scopes that can be fixed, regulated systems, integrations with a core system or an ERP, and projects that your committee approves in phases.
Before anything is built, you already know what will be delivered, in what order and the criteria you will use to accept it; if something changes, you review and approve the impact on scope, schedule or cost before it is carried out.
Six stages, one after the other, each with a deliverable that you review. What makes it a V-model: each test is defined in the stage that gives rise to it —acceptance criteria from Origin, the quality matrix and the integration tests from Design— and is run later: unit and integration tests during Construction, and the quality matrix and acceptance in Testing, before release.
Origin
We understand the business need and turn it into a story with its goal, its limits and who decides.
Deliverable: the requirement story, validated by the person you designate to decide.
Analysis
We measure what exists today: processes, systems, data and rules, including those that only one person knows.
Deliverable: the analysis, with the risks and dependencies in view.
Design
We model the business before the technology —the pieces of the system carry the names and boundaries of your business, not those of the database; this is called domain-driven design (DDD)—, and from that come the architecture, the rule matrices and the test cases, each with its expected result.
Deliverable: the design and the test matrix: from this point you know the criteria you will use to accept it.
Construction
We build against that matrix. Each piece arrives with its unit tests and, when it connects to another system, with tests of that connection that can be run again and that your team can run whenever it wants, without depending on us (automated collections, such as Postman's).
Deliverable: the code in your repository, with its tests, and the collections so your team can run them whenever it wants.
Testing
A quality review independent of whoever built it runs the full matrix (QA); then your people validate in your own environment (user acceptance testing, UAT).
Deliverable: the test report with its evidence and the acceptance record.
Release
We put it into operation with an agreed rollback plan and support during the first few days.
Deliverable: the user and operations manual, and the rollback plan in case something does not behave as tested.