ISO 29119 Maturity · Software Testing and Quality Management
Your testing practices mapped against ISO 29119, turned into a costed action plan.
10 themes, a 5-level scale. And the action that moves each level to the next.
The framework’s 10 themes, already written from L1 to L5. One company, one business unit, or 300 at once.
ISO 29119 Maturity · Software Testing and Quality Management
10 themes, 5-level scale.
Nordhavn Industries
53 / 100
They measure their maturity with Datamensio
An example
This could be your situation.
Take one company as an example: three sites, three spreadsheets, no shared answer.
Nobody can consolidate.
Nordhavn Industries, 2,400 people in Hamburg, Lyon and Porto. A client asks where the group stands. Each site answers in its own spreadsheet, with its own scales.
Three weeks, a single base.
One ISO/IEC/IEEE 29119 (parts 1 to 5) assessment launched across all three sites at once, from the managers’ interview notes. The framework was already written, its 10 themes and levels L1 to L5 too.
Two costs avoided before being committed.
A score of 53 out of 100, with the gap concentrated on three themes. The AI companion spotted that two actions duplicated those of another audit. The committee report took one sentence to request.
What it saved them
- 3sites measured on the same base, instead of three questionnaires to reconcile
- 2duplicate actions caught before the spend
- 1committee report, with no manual rework
These figures are an example. They could be yours.
The standard imposes processes. Datamensio says where you stand.
01
The framework is already written
Themes, questions and levels L1 to L5, all written. You do not start from an empty spreadsheet.
02
The score lands the same day
Online, by self-assessment link or in interview. Theme by theme, comparable over time.
03
The gap becomes a costed plan
Every step up carries its action. The AI prioritises on expected effect, not on the order of the standard.
04
Progress can be demonstrated
Campaign after campaign, against your target and against your own past. That is what your board asks for.
The maturity scale
One level, the next, and the action that links the two.
This mechanism (a level, a level above, and the action linking the two) is what turns an observation into a trajectory.
Are entry and exit criteria for test phases defined and applied?
- N1
No formalised criteria. Moving from one phase to another depends on team availability and the announced delivery date.
- N2
Criteria appear in some test plans. Their application varies by project and they give way under deadline pressure.
- N3
Criteria are defined in a common template, applied on most projects and checked before moving to the next phase. Exceptions remain occasional.
- N4
Criteria are systematically applied, exceptions are tracked and approved at the appropriate hierarchical level, with justification recorded.
- N5
Criteria are adjusted according to product risk level and revised based on analysis of production incidents, with documented tracking of revisions.
Action to move from L2 to L3
Build entry and exit criteria into the test plan template used by all teams, and make them an explicit checkpoint in the sprint review or go-live committee.
« With Datamensio, we meet our objectives far more efficiently. The ERDF inspection services and our supervising ministry particularly appreciated an approach that gives them reliable data. »
Director, CCI 94CCI Île-de-France
« We believe this is the most suitable solution to scale our transformation project and measure impact according to our needs. »
Maja SucekChief Operating Officer, Interreg Danube
Rarely on its own
Frameworks combine. Put several together to cover your business, or have the AI write yours.
Take your first measurementon ISO 29119.
What this framework covers
ISO/IEC/IEEE 29119 is the series of international standards devoted to software testing. It comprises five parts: concepts and vocabulary, test processes organised into three layers (organisational, test management, dynamic test), the documentation associated with each of these processes, test case design techniques, and keyword-driven testing. It is independent of the development lifecycle chosen: it applies equally to a sequential project or a continuous-flow team. It describes what needs to be done, not the tooling to deploy.
In practice, the difficulty is not knowing the standard, it is knowing where the organisation actually stands. Does the test policy exist anywhere other than in a document drafted for a previous audit? Are entry and exit criteria enforceable at go-live, or negotiated at every release under deadline pressure? Is test coverage measured, or inferred from the number of incidents reported afterwards? Across an application portfolio of several dozen products, the answers vary from one team to another, and no one has a consolidated view.
One confusion comes up often: that ISO 29119 has been made obsolete by agile. The standard was the subject of public debate in the testing community, around the risk of excessive formalism. Successive revisions clarified the point: processes are to be adapted to context and risk level, and documentation can be carried by tooling rather than by standalone deliverables. Another confusion concerns scope: ISO 29119 deals with testing, not quality management in the sense of ISO 9001, nor service management in the sense of ISO 20000. The three overlap, they do not replace one another.
A compliance audit concludes with a yes or a no: the process is in place, or it is not. The maturity assessment asks a different question. What level of control does each practice sit at, and what concrete action moves it to the next level. On a subject like testing, where almost every organisation does something, this gradation is the only one that produces a workable trajectory. The gap between the observed score and the target generates the action plan, which the AI groups into a prioritised roadmap.
The framework is ready to use in Datamensio. It adapts to your context: the AI adjusts the themes, questions and levels according to the CMMI method, or builds a variant from your test policy, your test plans and your internal standards.
Reference standard: ISO/IEC/IEEE 29119 (parts 1 to 5)
The themes assessed
Organisational test policy and strategy
Existence of a formalised test policy, translation into organisational strategy, alignment with business objectives, periodic review, uptake by teams.
Test management and planning
Test plan, scope and objectives, effort estimation, allocation of resources and skills, milestones, entry and exit criteria.
Risk-based approach
Identification of product and project risks, weighting of test effort by risk, traceability between risks and test cases, reassessment during the project.
Test design and techniques
Techniques used (equivalence partitioning, boundary value analysis, decision tables, state transitions, experience-based testing), justification of choices, coverage measurement.
Execution and environments
Preparation and availability of environments, test data management, replay conditions, configuration management, isolation of test environments.
Defect management
Defect lifecycle, severity and prioritisation, resolution timeframes, root cause analysis, feedback loop to design.
Documentation and traceability
Test documentation produced per part 3, level of formalism adapted to risk, traceability between requirements, test cases and results, evidence retention.
Automation and tooling
Automated scope and selection criteria, integration into the build and deployment pipeline, maintenance of the automated asset base, regression testing.
Metrics and steering
Coverage, progress and quality metrics, reporting to stakeholders, go-live decision, reliability of measurement data.
Skills and continuous improvement
Mapping of testing skills, training and certification of teams, lessons learned after a major incident, evolution of practices over time.
A short version of the framework is available for the online self-assessment.
Frequently asked questions
Is ISO 29119 certifiable?
The ISO/IEC/IEEE 29119 series is a set of process standards, with no associated enterprise certification scheme comparable to ISO 9001. Existing certifications in the testing field apply to individuals. Datamensio measures the maturity of your practices and prepares your audits, it does not issue any certificate.
What is the difference between this assessment and a compliance audit?
The audit checks whether a process is in place and concludes with a gap or a compliance finding. The assessment places each practice on a maturity scale and indicates the action that moves it to the next level. The assessment prepares the audit, the audit validates it.
Is the standard compatible with agile teams?
Yes. The processes described are to be adapted to context and risk level, and documentation formalism can be carried by tooling rather than separate deliverables. The framework assesses mastery of the practice, not the volume of documents produced.
How long does the assessment take?
The short version takes around thirty minutes to complete. In collaborative mode, with a test manager, an environments manager and an automation lead, data collection typically spans one to two weeks.
Can the framework be adapted to our organisation?
Yes. You can modify the questions, levels and themes, or start from a blank base. The AI can also build a variant from your test policy and internal standards. Ownership of the framework remains yours.
Can several teams or business units be compared?
Yes. The same framework is rolled out to several entities, and scores can be compared by theme and over time. A cross-entity roadmap consolidates action plans from the different assessments, without duplicating shared actions.
How is the action plan costed?
Each gap between the observed score and the target generates an action. The service catalogue matches a solution to each action, with its cost, timeframe and expected impact on the score. You arbitrate on orders of magnitude, not on intentions.
Where is the data hosted?
In France, with OVH, with backup at Scaleway. No transfer outside the European Union. The AI models used can be selected, including from European providers.