change-management.md

Change Management

Table of Contents

• The Key Person
  • Responsibilities
• Risk Analysis
  • Risky Items
  • General Guide
• Action
  • Deployment Check
• Reference

The Key Person

Release Manager is a role that everyone should work on.

Responsibilities

• Make sure CD is working as expected (green)
• Be in charge of the release flow from UAT to Production
• Health check after the release to production has done
• Make sure the tasks in JIRA do flow if they have stayed without any reasons (usually less than two days)
• Handle and communicate between the operators if necessary
• Make sure the smoke tests are passed before confirming the deployment succeeds

Risk Analysis

Risky Items

• Infrastructure Change
• New Environment Variables
• DB Schema Change
• Seed Data
• Incompatible Endpoint Interfaces (Params, Query, Body)
• Large Code Change
• Deploy during Peak Hours?

General Guide

• 0 to 1 => Normal
• 2 to 3 => Medium
• More than 4 => High

The last one is super risky in all cases!

Action

Normal Risk

• Production Cross Check
• Health Check

Medium Risk

• Test Cases Demonstration (Either manual or automated)
• Feature Toggles
• Always Dark Launch first

High Risk

• Blue Green Deployment
• Canary Release

Deployment Check

• An engineer who deploys the change should do at least a health check in the test entity on the production environments
• Please make sure you have the access to the test entity before the deployment
• If you do not have it, please ask your engineering lead

Reference

• How can rotating release managers improve a project's velocity and stability?