Waterfall Methodology: Technology Solution Release Management Process

Process Owner: Manager, Solutions Development and Support

Note: An owner must be a PCES-level manager or higher.

This process establishes standard tools and processes for the TSLC Waterfall Release Management phase within the Postal Service Technical Environment.

1. PURPOSE

The purpose of the Technology Solution Release Management process is to ensure that pre-implementation tasks are defined, IT change management is followed correctly, and post-implementation steps are executed.

2. SCOPE

The Technology Solution Release Management Process applies to all technology solutions including, but is not limited to:

• Development of application or system software
  
• Configuration of Commercial Off-The-Shelf software
  
• Telecommunications / network implementations
  
• Database changes
  
• Testing / training environments
  
• Infrastructure projects
  

Exemptions:

If neither CAT nor SIT can be performed, the same SIT/CAT Exemption_PPR Form must have been completed for both SIT exemption and CAT exemption, and uploaded to the project in the TSLC Artifacts Library in the following folders before implementation:

• System Integration Test: SIT Exemption folder
  
• Customer Acceptance Test: CAT Exemption folder
  

In addition, the Post-Production Review portion of the same SIT/CAT Exemption_PPR Form must be completed.  The entire form must then be uploaded to the TSLC Artifacts Library in the Release phase of the project in the Post-Production Review folder within 5 business days of implementation. The form must now include:

• SIT Exemption with approval
  
• CAT Exemption with approval
  
• PPR with approval

For additional information, please refer to the SIT-CAT Exemption and Post Production Review (PPR) Process.

3. PROCESS DESCRIPTION

The Technology Solution Release Management Process is composed of the following sub-processes:

1. Pre-Implementation Plan

Within this sub-process step, the Technology Solution Stakeholders develop the Pre-Implementation Plan, which outlines the tasks that need to be executed, when they should be executed, and by whom, before promotion of the technology solution into the production environment. 

The Pre-Implementation Plan may also include such items as: preparing for data migration, configuration settings, field training, contingencies, etc.  The information from this planning step is included in the change request that will be entered into the IT Change Management system.

2. Execution of the Release

Within this sub-process step, the Technology Solution Coordinator (TSC) initiates the IT Change Management Process, which includes entering the requested change, obtaining appropriate Technology Service Provider approval(s), and executing the change request.  All projects which included the creation or update of a Host Diagram are to post this project deliverable to the TSLC Artifacts Library.

3. Post-Implementation Review

During this step, the TSC verifies that the release was successful and monitors the tasks developed in the pre-implementation step.  This also includes a review so that identified problems might be prevented in the future or improvement to the processes can be made.

4. PROCESS DIAGRAM

An asterisk (*) denotes a Baseline requirement.

5. PROCESS INPUTS/OUTPUTS

Inputs

• Final Code and Build Package: Finalized package that originates from Build and has made it through testing.
  
• Customer Acceptance Approval*: Official letter indicating acceptance for CAT and the C&A process necessary for completion of the product release.
  
• Verify artifacts are uploaded to the TSLC Artifacts Library: Verify that all artifacts, with emphasis on Baseline and SOX artifacts, are uploaded to the TSLC Artifacts Library.
  

Outputs

• Pre-Implementation Plan: Outlines the tasks that need to be executed, when they should be executed, and by whom, before promotion of the Technology Solution into production.
  
• IT Change Request: During execution of the release, the Technology Solution Coordinator executes any change requests.
  
• Post-Implementation Review: The Technology Solution Coordinator verifies the release was successful and monitors the tasks developed in the pre-implementation plan.
  

An asterisk (*) denotes a Baseline requirement.

6. PROCESS RELATIONSHIPS

An asterisk (*) denotes a Baseline requirement.

7. ROLES AND RESPONSIBILITIES

• Change Control Board (CCB): Reviews and approves any changes submitted to the project that have an impact on its scope, cost, or schedule.
  

• Customer: Continues to provide input into the pre-implementation planning and assists with post-implementation tasks as defined.
  

• Technology Solution Coordinator (TSC): Responsible for coordinating the development and schedule of the pre-implementation plan and the IT change management system request.  This role may be the responsibility of any TSP, but is typically performed by IBSSC.
  

• Technology Solution Project Manager (TSPM): Responsible for updating the overall project plan to include all release management steps and ensures the technical activities are integrated correctly with the overall project activities.
  

• Technology Solution Providers (TSP): All Technology Solution Stakeholders provide input into the pre- and post-implementation plans, support the IT change management process as required, and ensure their tasks are executed within the schedule and cost as defined.

8. SUPPORTING DOCUMENTATION

• SIT-CAT Exemption and Post Production Review (PPR) Process

For access to the following documents, contact the US Postal Service. See Publication 5, Let's Do Business for further information about local US Postal Service contacts.

• SIT/CAT Exemption_PPR Form
• TSLC Templates, Waterfall
  

9. REVISION HISTORY