Releasing software to production every Thursday evening requires care, discipline, ruthless process adherence, and a dedicated team of professionals

1. Intake
Intake
Role Based Release Management Process Flow – From Request for Change to Release to ProductionChangeManagementSecurity
Performance
Assessment
QualityAssuranceDevelopmentDatabaseBusinessAnalyst
Client
Management
ServiceDesk
(Level1Support)
ITInfrastructure
Collective Analysis of Requests
for Change by Technical
Leaders
Release to Production
Analyses Release Development Integration Test Review to Preproduction Review to Production Release to Production
Analyses Release Development Integration Test Review to Preproduction Review to Production
Staging
Staging
Pre-Production
Production
Software Development Life Cycle
Individual Business Areas
Create Request for
Change
Create RFC for
Defect found by
the Service Desk
Create RFC from
Client for Defect
discovered by
Client
Create RFC for
defect or New
Requirement found
by BA
Build the Release
Package and
Release with RFC’s
to answer WHAT
and WHEN
Verify and Run
Integration Test
Dependencies
Conflicts Resolved
Create RFC for
Database Change
or Defect
Create RFC for
Defect found in
Quality Assurance
or Verification and
Validation
Accept Package
Contents from CCB
to Release Process
Conduct
Performance
Assessment in
Staging
Develop Stored
Procedure for
Change Request
Make Changes to
Baseline DB
Assess Change
Request for
Security Impacts in
Pre-Production
Deploy Package to
Targeted Baseline
Environment
Run Verification
Tests to Confirm all
Fixes Still Work
Announce Release
to Production
Perform Post-
Release Cleanup or
Processes
Communicate
release content to
client
Update
documentation of
all changes to Help
Desk for support
Work
Around?
Revert to Previous
Version of Failed
Items
NO
YES
Release
Success?
NO
YES
Make Changes to
Code Baseline for
Package
Create a RFC for
Defect found in the
IT Infrastructure
YESCreate RFC for
Code Change in
DEV
Analyze TTPro
Ticket from
Client RFC
Analyze RFC from
discovered defect
on Help Desk
Analyze RFC from
IT Infrastructure
Defect,
configuration
change, or system
change
Analyze RFC
from BA for
defect or New
Requirement
Change
Analyze RFC from
discovered
defect from DB
Team or RFC
Package
Impacted?
NO
YES
Communicate
Status of Failed
Items to Owners
Analyze RFC for
discovered
defect from QA
Team
Change Control
Board
Define Client
Testing Processes
Conduct Client
Testing in UAT
Environment
Collective analysis
of RFC all
submitters of RFC’s
Requirements
Review and Test
Case Identification
QA Testing
Pass?
NO
Integration
Test Pass?
NO
PERF Passed
Security
Passed
NO
NO
QA Testing in
Staging
Pre-Production
Pass?
Validation in Pre-
Production
Change Control
Board
Deploy to
Pre-Production
YES
NO
Web Page
Deployment
DB Changes
Deployment
Create RFC for
Defect found in
Performance
Assessment
Create RFC for
Defect found in
Security
Analyze RFC for
discovered
defect from
Performance
Assessment
Team
Analyze RFC for
discovered
defect from
Security Team
YES