Public sector
Information system interoperability programme
Secure the requirements, the functional governance and the quality of deliverables on an interoperability programme.
- Interoperability
- Governance
- Requirements
Governance, Compliance & Quality Assurance
Quality assurance
Install a quality assurance set-up that acts on causes: requirements review, control of deliverables and management of defects.
EN UNE PHRASE
Preventing a defect costs less than fixing it at acceptance.
THE PROBLEM
The situations that bring us in
- 01
Ambiguous specifications are only caught at testing time.
- 02
Defects are tracked in several tools with no common qualification.
- 03
The residual defect rate is unknown at the moment of switchover.
- 04
Quality is carried by the same people who do the building.
- 01THE PROBLEM
A quality set-up limited to end-of-cycle testing, with no effect on the quality produced upstream.
- 02WHAT AXENEO DOES
We build the quality plan, organise the requirement and deliverable reviews, define how defects are qualified and the indicators used to steer.
- 03THE RESULT
Defects caught earlier, consistent defect management, and a go-live decision grounded in indicators.
What we do
The set-up
- Quality strategy and project quality plan
- Organisation of the QA function and independence of control
- Review of requirements and specifications
- Acceptance criteria and control of deliverables
Steering
- Qualification, prioritisation and tracking of defects
- Quality indicators and dashboards
- Campaign reviews and passage decisions
- Capturing learning and continuous improvement
The Governance, Compliance & Quality Assurance method
This domain sits within the pillar’s overall method.
- 01
Scoping
Quality enters the project with the scoping: requirements formalised, testable, prioritised and linked to an identified need.
- 02
Requirements
Every requirement gets an owner, an acceptance criterion and a link to the test that will verify it. Traceability is built as you go, not reconstructed afterwards.
- 03
Quality plan
Roles, expected deliverables, reviews, quality gates and go-live conditions. The setup is sized to what the programme is worth.
- 04
Testing
Test strategy by level, coverage reported against requirements, representative data sets and controlled environments.
- 05
Validation
Functional validation, integration, regression. Gaps are qualified and settled in governance, not absorbed quietly.
- 06
Compliance
Where a standard applies, the body of evidence and the remediation plans are built continuously, through to the audit.
USE CASES
Where we step in
Independent QA on a programme
Separate control from delivery so that gaps reach governance.
Recovering a degraded project
Establish the real state of quality, qualify the defect debt and build a plan to bring it back up.
Related case studies
Contact
Quality assurance: let’s talk about your context
Whether the subject is a programme to secure, an acceptance process to structure or a certification to prepare, the first question is the same: what exactly are we committing to, and how do we demonstrate it?