We need to understand our organisation current state to reach where we want to be. Following DevOps maturity assessment will help to identify the current state.

Source Control

  1. Front end codes are in Source Control
    1. Yes
    2. No
    3. Partially
  1. Backend Scripts are in Source Control
    1. Yes
    2. No
    3. Partially
  1. Test suits in Source Control
    1. Yes
    2. No
    3. Partially
  1. Everything in Source Control
    1. Yes
    2. No
    3. Partially
  1. Code gets code reviewed for every check-in
    1. Yes
    2. No
    3. Partially
  1. Code gets pushed to Master with every check-in
    1. Yes
    2. No
    3. Partially
  1. Everyone commits to the master every day
    1. Yes
    2. No
    3. Partially
  1. We follow Trunk based approach
    1. Yes
    2. No
    3. Partially

Continuous Integration

  1. Our code coverage is (at this point in time)
    1. <10%
    2. 10 – 30%
    3. 30 – 50%
    4. 50 – 70%
    5. 70 – 90%
    6. 90-100%
  1. Every check-in goes through pull request
    1. Yes
    2. No
    3. Partially
  1. Every check-in runs unit, acceptance test before check-in to master
    1. Yes
    2. No
    3. Partially 
  1. We Continuously analyse and measure source code quality with Sonarqube
    1. Yes
    2. No
    3. Partially 
  1. We maintain logs for every CI build
    1. Yes
    2. No
    3. Partially
  1. Build artefacts are created on a separate server from dev machine
    1. Yes
    2. No
    3. Partially 
  1. Automated build with Unit test doesn’t take more than 10 min
    1. Yes
    2. No
    3. Partially
  1. What is the average build time for builds with unit tests
    1. Yes
    2. No
    3. Partially 
  1. We create SQL Server unit test that verifies the behaviour of stored procedures
    1. Yes
    2. No
    3. Partially 
  1. Sonarqube Bugs & Vulnerabilities percentage
    1. 0%
    2. 1 – 10%
    3. 10 – 30%
    4. 30 – 50%
    5. 50 – 70%
    6. 70 – 90%
    7. 90-100% 
  1. Sonarqube Duplications percentage
    1. 0%
    2. 1 – 10%
    3. 10 – 30%
    4. 30 – 50%
    5. 50 – 70%
    6. 70 – 90%
    7. 90-100%
  1. What is the average build time for builds with unit tests
    1. 1 to 2 min
    2. 2 to 3 min
    3. 3 to 5 min
    4. 5 to 10 min
    5. > 10 min
  1. SQL script Bugs & Vulnerabilities percentage
    1. 0%
    2. 1 – 10%
    3. 10 – 30%
    4. 30 – 50%
    5. 50 – 70%
    6. 70 – 90%
    7. 90-100%
  1. SQL Sonarqube duplication
    1. 0%
    2. 1 – 10%
    3. 10 – 30%
    4. 30 – 50%
    5. 50 – 70%
    6. 70 – 90%
    7. 90-100%
  1. SQL script code coverage
    1. <10%
    2. 10 – 30%
    3. 30 – 50%
    4. 50 – 70%
    5. 70 – 90%
    6. 90-100%

Continuous Testing

  1. Unit testing covering all aspects
    1. Yes
    2. No
    3. Partially 
  1. We follow TDD
    1. Yes
    2. No
    3. Partially 
  1. We follow BDD
    1. Yes
    2. No
    3. Partially
  1. We do Security Testing
    1. Yes
    2. No
    3. Partially 
  1. We do Performance testing
    1. Yes
    2. No
    3. Partially 
  1. We do Load Testing in staging and production
    1. Yes
    2. No
    3. Partially 
  1. automated testing :Builds are Self-Testing
    1. Yes
    2. No
    3. Partially 
  1. Every Commit Builds the Mainline on an Integration Machine
    1. Yes
    2. No
    3. Partially 
  1. Regularly refactor test suits
    1. Yes
    2. No
    3. Partially 
  1. Regression and E2E test run Nightly
    1. Yes
    2. No
    3. Partially 
  1. QA team member pairs with Developer for Test implementation
    1. Yes
    2. No
    3. Partially 
  1. Our tests are independent of each other
    1. Yes
    2. No
    3. Partially 
  1. We test the code in Production-like system
    1. Yes
    2. No
    3. Partially 
  1. We have automated smoke test Deployments
    1. Yes
    2. No
    3. Partially 
  1. Dashboard captures all testing metrics and events
    1. Yes
    2. No
    3. Partially 
  1. We have automated Database script testing
    1. Yes
    2. No
    3. Partially 
  1. We automatically test Environment creation
    1. Yes
    2. No
    3. Partially 
  1. We don’t use record and playback to create test suits
    1. Yes
    2. No
    3. Partially
  1. As requirements are updated/changed, can systems auto-generate test-cases along with access to the required test data?
    1. Yes
    2. No
    3. Partially

Read through DevOps maturity assessment Part 2

Read through DevOps maturity assessment Part 3

Advertisements