Change Requests
Change Requests (CRs) are formal requests to modify existing requirements, features, or functionality after approval or implementation.
Change requests answer: “What needs to change, and why?”
1. Definition
A Change Request (CR) is a formal request to modify an existing requirement, feature, design, or functionality after it has already been approved or implemented.
Change requests answer: “What needs to change, and why?”
2. Why Change Requests Occur
- Business needs evolve
- Stakeholder feedback
- Regulatory or compliance updates
- Defects in original requirements
- Market or customer demand changes
3. Types of Change Requests
3.1 Functional Change
- Modification to existing functionality
- Addition or removal of features
3.2 Non-Functional Change
- Performance, security, usability updates
3.3 UI / UX Change
- Layout, labels, workflow adjustments
3.4 Technical / System Change
- Configuration or integration changes (conceptual for manual testers)
4. Change Request Lifecycle (High-Level)
- Change request raised
- Impact analysis performed
- Approval or rejection
- Requirement updates
- Development & testing
- Validation and closure
5. Manual Tester’s Role in Change Requests
- Analyze impact on existing test cases
- Identify affected functionalities
- Update test scenarios and test cases
- Plan regression testing
- Update RTM and test reports
6. Impact Analysis (Tester’s View)
Testers analyze:
- Affected modules
- Test case updates required
- Regression scope
- Test data changes
- Timeline and risk impact
7. Change Request vs Defect
| Aspect | Change Request | Defect |
|---|---|---|
| Nature | New or modified requirement | Deviation from requirement |
| Reason | Business decision | Product flaw |
| Outcome | Requirement update | Bug fix |
8. Real-Time Example
Original Requirement:
- Password minimum length = 8
Change Request:
- Increase minimum length to 12
Tester Actions:
- Update BVA and test cases
- Execute regression testing
- Update RTM
9. Risks of Poorly Managed Change Requests
- Scope creep
- Missed regression defects
- Inconsistent documentation
- Release delays
10. Best Practices for Handling Change Requests
- Formal approval before implementation
- Clear documentation of changes
- Impact analysis before execution
- Mandatory regression testing
- Stakeholder communication
11. Interview-Ready Answers
Short answer:
A change request is a formal request to modify existing requirements or functionality.
Detailed answer:
Change requests capture approved modifications to requirements, and testers evaluate their impact, update test assets, and ensure changes do not break existing functionality.
12. Key Takeaway
Change Requests are inevitable—controlled change protects quality, uncontrolled change creates chaos.