The federation-recognised classification of an organisation's FinOps practice across the inform, optimise, and operate phases, with progression criteria defined per discipline rather than as a single composite. FinOps maturity is the dominant input to the FinOps component of the IFO4 Score and the principal external signal of an organisation's posture. The federation requires maturity to be self-attested quarterly with evidence pointers, and externally validated annually as part of the accreditation cycle under UFMS-001:2.4. Inflated maturity claims are challengeable.
Modelled on capability maturity model concepts originally from CMMI; the FinOps Foundation popularised the inform, optimise, operate phases in 2018.
Federation members self-attest FinOps maturity quarterly. External validation occurs annually via the federation review process. Maturity progression is conditioned on evidence under MEV-Annex:3.2 and on the IFO4 Score components per UFMS-001:2.4.
@misc{ifo4_glossary_finops_maturity,
title = {{FinOps Maturity}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{finops-maturity}}},
year = {2026},
url = {https://ifo4.org/glossary/finops-maturity},
note = {Category: FinOps; key: FinOpsMaturity}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.