The release code to production for a mission critical enterprise application, we don't just "push to production" and see what the customer thinks. There is a stewardship governance process, even while the development of the software is done with Scrum. One fault and 10's of 1,000's of users are impacted.

1. Promotion Rhythm – Through QA, Performance Testing, UAT to Production, Using Release 1.0 + New Features to Produce Release 2.0 as a candidate for Production
Change Control Board Weekly Rhythm
ProductionUATPERFDEV
InitiatorChangeManagementCCBResources
QA
Phase
Phase
Environments
CyberSecurity
Training
Compliance
R2.0
QA
Test
R2.0
Yes
No
QA Fix
Perf
Test
Perf
Test
Perf
Fix
R2.2
No
R2.0 UAT
R2.0
Yes
R2.1
Yes
Yes
R2.1
Perf
Test
QA
Test
R2.2
Yes
Yes
Perf
Fix
No
R2.1 UAT
Yes
UAT
Fix
No
R2.1
QA
Test
UAT
R2.2
Yes
R2.2
Yes
UAT
Fix
No
No
QA Fix
No
No
Perf
Fix
UAT
Fix
QA Fix
No
R2.3
Repeat QA/PT/
UAT Cycle
HelpDesk
EnterpriseInfrastructure
ChangeControlBoard
Capture
Request Change
Validate
Request Change
Urgent
Urgent Change
Procedure
Accepted
Notice to
Initiator
Std Change
Major
Minor
Evaluate
Change
Authorized
Evaluate
Change
Authorized
Coordinate
Implementation
Release and
Deployment
Management
Execute
Change
Post
Implementation
Review
Change Close
Out
R1.0 R2.0
text
text
c
ctext texttexttexttext
text
text text
Entry and Exit criteria for each
decision gate in the promotion flow
is defined in separate worksheets.
The Exit criteria are owned by the
accountable manager for that
process. That same manager is
accountable for accepting the Entry
criteria before performing their role.
The process assures the interfaces
between processes and the process
owners is defined through
measureable outcomes of progress
toward production release.
Roles in the Production Release
text
text