release sign off matrix v1.3

Release Sign-Off Matrix

document.xls 1 04/07/2023

Phase Deliverable Objective of Deliverable Purpose of Sign Off Input

Planning

Release Parameters NSRI Management GBPM Mngt OSCAR Roadmap

GBPM Initial Scope List Provides initial scope for the release. GBPM TRAC Leads GBPM Mgmt Release Parameters

Requirements

GBPM Service Desk - SC

Initial Scope ListASAT Service Desk - SC

DEV Service Desk - SC

QA Service Desk - SC


ASAT Service Desk - SC



Initial Estimates PM N/A Service Desk - SC N/A

AFT Service Desk - SC

Service Desk - SC


RM Validate final resource allocation based upon estimates and final scope list.

Design

DEV


Service Desk - SC

Responsible to Produce

DeliverableRequiredSign-Off

Location of Sign Off to be Captured

Identifies program priorities and technical contraints that could affect the final scope of the release.

Release Level - Email

Represents a full understanding of the program proirities and technical contraints in order to create the initial scope list.

Release Level-Excel File on Sharepoint

Represents initial scope list that has been approved by GBPM management. This scope list will be forwarded to NSRI management. The scope list is expected to meet Release Parameters based upon GBPM view point.

Milestone Established: Planning Complete

Requirement Detail Document (RDD)

Minor Specification Document (MSD)

Business Requirement Document (BRD)

Capture requirements for the enhancement or defect, in sufficient detail to provide understanding of what change is required.

GBPM responsible for content

ASAT is responsible for deliverable format

Ensure requirements accurately and thoroughly reflects business intention associated with upcoming system change, according to GBPM and RBPM (where necessary). Ensuring an FSD can be created based upon the details in the requirements, as stated, without question to the best of their ability.

Ensure requirement document follows standard formats and is documented in a clear way that can be understandable to others. Ensuring an FSD can be created based upon the details in the requirements, as stated, without question to the best of their ability.

Represents developer has reveiwed requirements and understands requirements, as stated, to ensure FSD and design documents can be created without question to the best of their ability.

Represents QA Tester has reveiwed requirements and understands requirements, as stated, to be able create test scenarios without question to the best of their ability.

Functional Specification Document (FSD)

Capture functional specifications for the enhancement or defect, in sufficient detail to provide understanding of what change is required.

GBPM responsible for content

ASAT is responsible for deliverable format

Ensure functional specifications are accurate and complete, based upon the requirements detailed in the RDD/BRD. Ensuring TSD/Protoype can be created based upon the details in the requirements, as stated, without question to the best of their ability.




Ensure functional specifications document follows standard formats and is documented in a clear way that can be understandable to others. Ensuring TSD/Prototype can be created/modified based upon the details in the FSD, as stated, without question to the best of their ability.

Represents developer has reveiwed funcional specifications and understands the specifications, as written. Ensuring a TSD/Prototype can be created/modified based upon the details in the FSD, as stated, without question to the best of their ability.

Represents QA Tester has reveiwed functional specifications and understands specifications, as stated, to be able create test cases without question to the best of their ability.

Capture initial estimates from development and QA based upon requirements.

Requirement Detail Document (RDD)Minor Specification Document (MSD)Business Requirement Document (BRD)Functional Specification Document (FSD)

Milestone Established: Final Requirements Sign-Off

Technical Assessment and Final Scope List

Capture technical risk of deploying requested changes into the current production environment, using the following criteria:1) Lack of confidence in complete requirements2) Concern of implication of changes (e.g. unknown impacts to other parts of the application)3) Concern of technical complexity of changes (e.g. interfaces to other systems are involved)4) Performance concerns5) Concern of code quality/implementation/design

Application Framework Team (AFT)

Ensure the functional/technical risk of deploying requested changes into the current production environment is reviewed, necessary prototypes based upon high risk is identified, and identify items to be descoped based upon high risk.

Release Parameters

Initial Scope List

Requirements

FSD

High Level Design/Implementation/Test Approach

Estimates and Resources Leveling

NSRI Management

Ensure AFT has completed the necessary functional/technical risk assessment and understand the risk associated with scope items before deployment to production. In addition, agree with action items for risk mitigation (i.e., prototyping), and recommend scope modifications based upon risk assessment and available resources. The technical assessment is expected to meet Release Parameters based upon NSRI view point.

Review and understand technical risks associated with requested scope items and agree on final scope, including suggested scope modifications.

Estimates re-verification and Resource Leveling

Re-verify estimates based upon technical assessement and final scope list. Conduct resource leveling.

NSRI Management

Release E-mail or meeting notes

Technical Assessment

Final Scope List

Initial Estimates

Milestone Established: Scope Freeze

Technical Specification Document (TSD)

Capture technical specifications for the enhancement or defect, in sufficient detail to provide understanding of what change is required.

Represents development has completed the TSD according to their understanding of the FSD. Ensuring development can be completed without question to the best of their ability.

FSD

Final Scope ListTech Lead and/or AFT

Ensures the TSD has been completed according to their understanding of the FSD, as well ensure best practices have been used as part of the design (i.e., with relation to being robust and optimizing performance). Ensuring development can be completed without question to the best of their ability.







Design

Prototype DEV

AFT Service Desk - SC

Service Desk - SC


Development

Coding Provide requested functionality. DEV N/A N/A N/A

Unit Test Cases DEV N/A N/A N/A

Unit Test Case ResultsDEV AFT TRAC

DEV QA Service Desk - SC

DEV AFT TRAC

Test

Release Test Plan QA N/A N/A

Test Scenarios QA




Test Cases/Data QA GBPM Service Desk - SC

PM RBPM Ensure the scope of SCs that the regions are to test are accurate and complete.

QA Test Execution QA N/A N/A N/A

QA Test Regression QA N/A N/A N/A Test Regression End-to-End Test Cases/Data

Test Results QA

QA Service Desk - SC Ensure test results are acceptable.

GBPM Service Desk - SC Ensure test results are acceptable for the scope to be deployed to staging and/or production.

Re

gre

ssio

n

QA

Ensure design functionality works as per the original requirements. Enable GBPM to clarify requirements and necessary detail. In addition, confirm the risk identified within the Technical Assessment.

Ensures the prototype has been completed according to their understanding of the TSD and the functionality detailed in the FSD. As well ensure best practices have been used as part of the design (i.e., with relation to being robust and optimizing performance).

FSD

Final Scope List

NSRI Management

Ensures the prototype has been completed, and signs off on the risk associated with the scope item before deployment into TEST.

Ensures design is accurate and complete, by validating the functionality works properly based upon the requirements detailed in the RDD/BRD/MSD/FSD.

Milestone Established: Design Complete (Scope Validation)

TSD

Prototype

Provide visibility into what Unit Test Cases will be executed by the developer to ensure quality of code.

Report Unit Test results so that all are aware of any risk identified by the testing.

Conduct code review to ensure quality standards are maintained in the code (i.e., with relation to being robust and optimizing performance).

Ensure QA has an understanding of the quality of code before testing begins. This is not a sign off or approval of the results.

Integration Testing Results (if applicable)

Report integration test results so that all are aware of any risk identified by the testing.

Conduct code review to ensure quality standards are maintained in the code (i.e., with relation to being robust and optimizing performance).

Milestone Established: Development Complete

The Test Plan defines test scenarios and test cases/data for a release. This will be updated at various intervals during the testing phase.

This document is a wrapper containing links to test scenarios and tes cases for all services within the release. No formal sign-off is required. The test scenarios and test cases are signed off individually and captured in the service call.

Final Scope List




Functional Specfication Document (FSD)

Technical Specification Document (TSD) - As Necessary

Prototype - As Necessary

Organize test scenarios to be executed, based upon requirements and business work flow.

Ensue the scenarios are accurately verifying all requirements as listed in the RDD, BRD, MSD, and FSD. QA is ready to begin creating test cases without question to best of your ability.

Represents the developer has reviewed and understands what will be tested based upon what was developed. This is the opportunity for the developer to provide input or advise into the test scenario.

Ensure the scenarios accurately represent the requirements and/or use cases as listed in the RDD, BRD, and MSD.

Provide visibility and structure into specifc testing activities that will define the successful completion of the test.

Ensure all detailed functions, including data, to be tested are adequately representing in all test scenarios/cases.

User Acceptance Test Scope

Scope items that the regions will be performing User Acceptance Testing on.

By Service Team -E-Mail

Milestone Established: Test Scenarios and Test Cases/Data Sign-off

Execute test cases, with data identified.

Test Scenarios

Test Cases/Data

Execute regression test cases, with data identified.

Report test results so that all are aware of any risk identified by the testing. The results will capture any issues that are considered acceptable to be deployed to production.

QA Test Execution

QA Test Regression

Milestone Established: Test Case Results Sign-offMilestone Established: Development Code Freeze

Iteration - 1

Regression Test Plan - Iteration 1

Provide visibility into the priority of the test scope, as well as the execution plan to complete the scope and define the successful completion of the Regression Iteration-1 Test, in order that sufficient testing can be completed within the time available.

NSRI Management


Upon review of the test plan and technical assessment, prioritization and risks will be identified and communicated.

Final Scope List

Technical Assessment







Re

gre

ssio

n

QA

GBPM

Test Execution QA N/A N/A N/A Regression Test Plan - Iteration 1

Test Results QA N/A N/A N/A Test Execution

UAT Test Results Regions RBPM UAT Test Execution

QA

Final Scope List

GBPM

Test Execution QA N/A N/A N/A Regression Test Plan - Iteration 2

Test Results QA

QA QA Manager ensures test results are acceptable.

Test Execution

GBPM

Deployment

RM CAB Final Scope List

Business Release Notes GBPM N/A Communicate to the end user what will be deployed.

Close Service Call GBPM Service Desk - SC Ensure deployed functionality meets requirements, according to the RDD/MSD/BRD. Final Scope List

RM

Agree on the action plan based upon lessons learned.

Production Deployment Release

Iteration - 1


Provide visibility into the priority of the test scope, as well as the execution plan to complete the scope and define the successful completion of the Regression Iteration-1 Test, in order that sufficient testing can be completed within the time available.


Ensure the test plan accurately reflects scope and priority to be tested for the release in Regression Iteration-1.


Report daily progress of test results so that all are aware of any risk identified by the testing.

Report User Acceptance testing results so that all are aware of any risks identified.


Ensure the results are acceptable, and accurately reflect the requirements as listed in the RDD, BRD, MSD or FSD.

Milestone Established: Regression Test Iteration-1 and UAT Complete

Iteration - 2


Provide visibility into the priority of the test scope, as well as the execution plan to complete the scope and define the successful completion of the Regression Iteration-2 Test.

NSRI Management


Upon review of the test plan and technical assessment, prioritization and risks will be identified and communicated.


Ensure the test plan accurately reflects scope and priority to be tested for the release in Regression Iteration-2.


Report daily progress of test results so that all are aware of any risk identified by the testing.

Release LevelE-mail

NSRI Management

Release LevelE-mail

Provides final Go / No Go decision for Production deployment based upon the STG regression test results. Signs-off on any outstanding defects that have not passed regression testing, and accepts the risk that the outstanding defects are acceptable to go into Production.

Release LevelE-mail

Ensure test results are acceptable. Sign-off on any outstanding defects that have not passed regression testing. This sign-off accepts the risk that the outstanding defects are acceptable to go into Production.

Milestone Established: Regression Test Complete & Go/No-Go Deployment Sign-Off

Technical Release Notes and Implementation Plan

Provides the deployment plan with the necessary details, including infrastructure and application information. This is required for implementing the release.

Service Desk - RFC

Ensure production deployment resource review and approve associated work orders to complete the production deployment according to the technical release notes and implementation plan.

Make the end user aware of the changes going into the release and how specifically the change will effect business process.

E-mail with a descriptive word document attached

Milestone Established: Production Deployment Release

Ensure deployed functionality meets requirements, according to the RDD/MSD/BRD.

Originator on Service Call

Lessons Learned and Associated Action Plan

Provides feedback on the release to NSRI Management, and identifies areas of potential improvements for future releases. Also lists the SCs (issues) that are attributed to the release being put into production.

NSRI Management

Release E-mail or meeting notes

release sign off matrix v1.3

Documents