Page 1 of 2

Backlog CAB Form

Change Information

1. Change Request Number

2. Date Submitted

3. Change Requestor

4. Project Name

Change Description

1. Title of Change

2. Detailed Description of Change

Purpose of Change
Detailed technical description
Systems or services affected
Impact Assessment

1. Business Impact

Impact on Business Operations
Benefits of the change

2.Technical Impact

Impact on infrastructure
System downtime required
Risk Assessment

1. Identified Risks

Potential issues during and after implementation

2. Mitigation Strategies

Steps to minimize risks

Testing and Validation

1. Testing Plan

Details of how the change will be tested

2. Validation Criteria

Success criteria and rollback plans

Implementation Plan

1. Implementation Steps

Detailed step-by-step implementation guide

2. Responsible Parties

Roles and responsibilities of team members involved
Approval and Authorization
Estimated Hours

CAB Member Names and Date

Comments
CAB Terms
Testing Obligations: Assigned personnel are responsible for conducting functional and integration testing of the application within their available time and according to their professional capabilities. The Company recommends allocating dedicated Quality Assurance (QA) resources to improve system testing and enhance overall QA effectiveness. To maintain quality and productivity, the client acknowledges that their team has conducted systematic testing, especially when QA resources are shared or constitute less than 30% of the total monthly allocated hours.
Issue Resolution: For regular sprints, issues reported within 15 days following deployment to the LIVE environment will be addressed in the subsequent sprint without additional charges, provided they are directly related to the tasks completed during the preceding sprint. This policy does not cover pre-existing issues or rare edge cases not identified during initial testing phases. After the approval of the next sprint, any newly identified issues will be added to the regular development pipeline and will be subject to standard billing.
System Approval: The Client acknowledges that the system has been thoroughly tested and meets the objectives and requirements of the sprint. The Client also recognizes that minor requirements and features may have been modified to prioritize sprint release. It is impractical to document every developer-level decision, trade-off, and verbal communication or approval. Any requirements sacrificed to meet deadlines or features deprioritized due to various factors will be treated as new requirements and addressed in future sprints as billable tasks.
Approval of Efforts: Should there be any concerns or questions regarding approved efforts or billable hours, the Client is urged to communicate with the Company within two weeks from the date of notification. The Company is committed to addressing any such inquiries promptly. Failure to communicate within the two-week review period will be interpreted as the Client's tacit approval of the recorded efforts and associated charges.