This is what we use as quality maturity levels.
| Item | Description |
|---|---|
| T001 | Test coverage is measured at the commit stage |
| B001 | All CI/CD scripts are kept in version control |
| T016 | No release with red tests |
| Item | Description |
|---|---|
| T002 | Commit stage test coverage > 10% |
| T007 | Classify tests as commit, acceptance, and performance |
| T011 | There are acceptance tests for at least one feature upon main use cases |
| B002 | A specific code style is enforced for main programming languages |
| B004 | Compiler warnings are prevented |
| E001 | All direct external dependencies for the software product are specified using fixed versions in version control and also managed with tools/scripts in version control |
| E012 | Secrets are not stored in version control |
| D001 | Deployment frequency is once per month |
| D005 | Lead time for changes is less than six months |
| D009 | Time to restore service is less than one month |
| D013 | Change failure rate is less than 60% |
| Item | Description |
|---|---|
| T003 | Commit stage test coverage > 20% |
| B005 | Available analysis tools on new code are actively used, as submit gate (50% sonar-way, zero issue, incremental) |
| T013 | "Requirement - Acceptance Test" mapping coverage > 5% |
| E002 | Automated application deployment from scratch |
| E003 | Automated application upgrade |
| E013 | All configuration in version control and all production configs from version control |
| E006 | Data is migrated using versioned script only |
| D002 | Deployment frequency is once per week |
| D006 | Lead time for changes is less than one month |
| D010 | Time to restore service is less than one week |
| D014 | Change failure rate is less than 45% |
| E010 | Same process (scripts) to deploy to every environment |
| Item | Description |
|---|---|
| T004 | Commit stage test coverage > 50% |
| T014 | "Requirement - Acceptance Test" mapping coverage > 20% |
| B006 | Available analysis tools are actively used on new code (80% of sonar-way) |
| B007 | Build environment can be automatically created from version control |
| B008 | No manual configuration of CI/CD agent machines |
| E004 | Automated infrastructure provisioning from scratch |
| E007 | Automated data migration while deploying |
| E005 | Automated infrastructure upgrade |
| E014 | All transitive dependency versions are defined |
| D003 | Deployment frequency is once per day |
| D007 | Lead time for changes is less than one week |
| D011 | Time to restore service is less than one day |
| D015 | Change failure rate less than 15% |
| Item | Description |
|---|---|
| T015 | "Requirement - Acceptance Test" mapping coverage > 50% |
| E008 | Data migrations are tested |
| D004 | Deployment is on-demand (multiple deploys per day) |
| D008 | Lead time for changes is less than one hour |
| D012 | Time to restore service is less than one hour |
| E009 | Data migration can be rolled back, automatically |