DevOps maturity assessment Part 2 – Continuous Delivery, Logging & monitoring, Infrastructure as Code/Disaster Recovery

We need to understand our organization current state to reach where we want to be. Following DevOps Assessment will identify the current state of team’s DevOps maturity.

Read through DevOps maturity assessment Part 1

Continuous Delivery 

  1. Zero-downtime release practices are followed(Blue-green, Canary, Dark Launch, Expand/Contract)
    1. Yes
    2. No
    3. Partially
  1. Feature toggle enabled for all the new features
    1. Yes
    2. No
    3. Partially 
  1. same build package used to deploy to QA, Staging and Prod
    1. Yes
    2. No
    3. Partially 
  1. We release small batches regularly
    1. Yes
    2. No
    3. Partially 
  1. Team member can independently deploy to production without any external dependency
    1. Yes
    2. No
    3. Partially 
  1. We release at the end of every sprint(small and Frequently)
    1. Yes
    2. No
    3. Partially 
  1. Bug resolution released to live immediate
    1. Yes
    2. No
    3. Partially 
  1. Staging testing runs on Production-Like system both Web and Database environment
    1. Yes
    2. No
    3. Partially 
  1. Code always in Deployable state
    1. Yes
    2. No
    3. Partially 
  1. Done means released
    1. Yes
    2. No
    3. Partially
  1. Release Pipeline have been configured for automated deployment
    1. Yes
    2. No
    3. Partially 
  1. Release pipeline has automated database script changes
    1. Yes
    2. No
    3. Partially
  1. Development and QA has separate Database environments
    1. Yes
    2. No
    3. Partially
  1. We have automated rollback scripts
    1. Yes
    2. No
    3. Partially

 

Logging and monitoring

  1. We have logging and monitoring enabled for all the Servers
    1. Yes
    2. No
    3. Partially 
  1. We have logging and monitoring enabled for all the Applications
    1. Yes
    2. No
    3. Partially 
  1. We have logging and monitoring enabled for all the Services
    1. Yes
    2. No
    3. Partially 
  1. Notifications from failures/alerts are configured
    1. Yes
    2. No
    3. Partially 
  1. Bug/Issue raise from alerting systems are fixed and released immediately
    1. Yes
    2. No
    3. Partially

 

Infrastructure as Code/Disaster Recovery

  1. Web Environments are consistent across Prod, Staging, QA, Dev
    1. Yes
    2. No
    3. Partially 
  1. Database Environment consistent across Prod, Staging, QA, Dev
    1. Yes
    2. No
    3. Partially 
  1. We can automatically recreate live server through scripts in few minutes
    1. Yes
    2. No
    3. Partially 
  1. We rebuild infrastructure for every release
    1. Yes
    2. No
    3. Partially 
  1. Environments are always stable
    1. Yes
    2. No
    3. Partially 
  1. Developers have production-like environment at their workstation
    1. Yes
    2. No
    3. Partially

 

Micro service/Serverless

  1. Our Services are small Independently Deployable services that work together, modelled around a business domain
    1. Yes
    2. No
    3. Partially 
  1. We follow Domain Driven Design
    1. Yes
    2. No
    3. Partially 
  1. Micro services are running in containers
    1. Yes
    2. No
    3. Partially 
  1. Micro services are running on Service fabric
    1. Yes
    2. No
    3. Partially 
  1. Both Front End and Back end are combined as micrsoservice
    1. Yes
    2. No
    3. Partially 
  1. follow Strangler pattern for all new development
    1. Yes
    2. No
    3. Partially 
  1. Service deployments automated, repeatable, and predictable
    1. <10%
    2. 10 – 30%
    3. 30 – 50%
    4. 50 – 70%
    5. 70 – 90%
    6. 90-100% 
  1. Microservies CI\CD pipelines are enabled
    1. <10%
    2. 10 – 30%
    3. 30 – 50%
    4. 50 – 70%
    5. 70 – 90%
    6. 90-100%

Read through DevOps maturity assessment Part 3

Advertisements