Release Management
Configuration management
Release Management Goal



Coordinate the processes through the
project development life cycle
Ensure the quality of production version
Manage the project artifacts
Release Management Processes







Release Design
Monitor and Verify the progress of Release
Obtain sign-off
Approve Production Implementation
Coordinate Release Deployment Activity
Implement Release
Post Implementation Review
Supporting processes




Configuration management
Change management
Content management
Version control
Configuration Management

Manage





Project artifacts
Builds
Source code
Start Up Procedure
Documentation
Build





Is identified uniquely by number and date
Contains modules of different versions
After compiling may go to QA
After compiling remains unchanged
Is to be signed off to QA by Build Manager
Change Management





Build in QA or in production can be
changed only with Change Request
Change Requests are registered and
approved
Developers change a working build
Old source code remains in the storage
After changes done new build goes to QA
Content Management




Developed to manage particularly web site
content
Control over the processes of web site
updates
Design approval process
Store updated versions of web pages