Checklist Examples

Here is an example

Checklist for V1 release on 07th Dec.

Branch - master

Tag - V 1.0.0

Repos Details -



Backend -


Devops -



Ownership - Identify the team members who would be responsible for the success of the deployment

  • Ownership: Service owners are identified. Contact information and methods are provided.

    • OffSite Details

    • Himanshu (DevOps)

    • Piyush Agarwal(Frontend)

    • Jagdish (Backend)

  • OnSite Details

    • John Doe(Frontend)

    • Morgan(Data Mgmt and Backend)

    • Piyush (Backend) - emails - (+1 647 XXXX)


Defined Service-level objectives (SLOs) / service-level agreements (SLAs):

SLO or Service Level Objective is a goal that the service provider wants to reach.

In this Release, we are targeting to launch the product adhering to the MVP details -MVP (Minimum Viable Product) Details andMVP Phase 1 Details (plus added details on Jira board), with keeping in mind the release of the XXX NETWORK (link - ).


Deployment strategies:

Zero Downtime Deployments Details

Check for Auto Deploy Feature and Auto Scaling Groups

Check for Env variables Updates

Check for Secrets

Check for Docker Images Tagging and Storage and Cleanup

Configure CPU/Mem and GC settings

Deployment Rollback Strategy

Rollback Mechanism ( Via Developers Through PR)

Manual Rollback Mechanism (For immediate/ button click)


Continuous integration: When engineers commit their changes, the system kicks off automated builds, tests, and deployment to a lower-level environment.

Continuous delivery: Deploying to production involves nothing more than approval and a click of a button. Changelogs and release notes indicate what changes exist in each environment.

Static code analysis: Code is automatically scanned, formatted, or linted according to coding standards.

DataBase Checks

Database Credentials and Permission check

Database Backups and Restoring Mechanism

Security and Networking


Authentication/authorization: Each service or application requires proper authentication and authorization.

Secrets management: Secrets are secured properly in a vault or secret store. Tools like truffle hog or git-secrets scan code to identify potential secrets.


Check for VPC’s, Subnet, ACLs.

Static Ips’s And Security Group

Configure DNS Using Route 53

Monitoring and Alerting

Graphs and Thresholds check

Alerting Check

Track availability and application and server metrics

Logging Check

Handbook and Troubling Shooting Steps

Doc or Confluence Link