Change Request
Change Request: {{CR_TITLE}}
Project: {{PROJECT_NAME}} Version: {{VERSION}} Date: {{DATE}} Author: {{AUTHOR}} Status: Draft | In Review | Approved Reviewers: {{REVIEWERS}}
Document History
| Version | Date | Author | Changes |
|---|---|---|---|
| 0.1 | {{DATE}} | {{AUTHOR}} | Initial draft |
1. Change Request Metadata
| Field | Value |
|---|---|
| CR ID | CR-{{XXX}} (assigned by PM) |
| Date Submitted | {{DATE}} |
| Submitted By | {{NAME}} — {{ROLE}} |
| Project | {{PROJECT_NAME}} |
| Priority | Critical / High / Medium / Low |
| CR Type | Scope Change / Budget Change / Timeline Change / Requirements Change / Design Change / Technical Change |
| Current Phase | Planning / Design / Development / Testing / Deployment |
| Decision Deadline | {{DATE}} (by when a decision must be made to avoid impact) |
2. Change Description
2.1 Summary of Change
{{ONE_PARAGRAPH_SUMMARY_OF_WHAT_CHANGES}}
2.2 Current State (Before)
{{DESCRIPTION_OF_CURRENT_STATE}}
Currently approved in: {{DOCUMENT_NAME_AND_VERSION}}, Section {{X.X}}
2.3 Proposed State (After)
{{DESCRIPTION_OF_PROPOSED_STATE}}
2.4 Out of Scope for This Change
This CR does NOT include:
- {{EXPLICITLY_EXCLUDED_ITEM_1}}
- {{EXPLICITLY_EXCLUDED_ITEM_2}}
3. Reason & Justification
3.1 Reason for Change
| Reason Category | Applies? | Details |
|---|---|---|
| New business requirement discovered | Yes / No | {{DETAILS}} |
| Regulatory / compliance mandate | Yes / No | {{DETAILS}} |
| Client feedback from UAT / prototype | Yes / No | {{DETAILS}} |
| Technical blocker / infeasibility | Yes / No | {{DETAILS}} |
| Market opportunity / competitive pressure | Yes / No | {{DETAILS}} |
| Error/omission in original requirements | Yes / No | {{DETAILS}} |
| Performance / quality improvement | Yes / No | {{DETAILS}} |
Primary Justification: {{CLEAR_BUSINESS_JUSTIFICATION_WHY_THIS_CHANGE_IS_NECESSARY}}
3.2 Consequence of Not Changing
If this change is not approved: {{CONSEQUENCE_OF_REJECTION}}
4. Impact Analysis
4.1 Scope Impact
| Deliverable Affected | Current Scope | Proposed Scope | Impact Type |
|---|---|---|---|
| {{DELIVERABLE}} | {{CURRENT}} | {{PROPOSED}} | Added / Removed / Modified |
| {{DELIVERABLE_2}} |
Scope Change Size: Small (< 1 day) / Medium (1–3 days) / Large (3–10 days) / Major (> 10 days)
4.2 Timeline Impact
| Milestone | Current Date | New Date (if approved) | Delay |
|---|---|---|---|
| {{MILESTONE}} | {{DATE}} | {{NEW_DATE}} | {{DAYS}} days |
| Project completion | {{DATE}} | {{NEW_DATE}} | {{DAYS}} days |
Timeline Impact: None / Minor (≤ 3 days) / Moderate (4–14 days) / Major (> 14 days)
Critical Path Impact: Yes / No If yes: {{WHICH_CRITICAL_PATH_ITEMS_AFFECTED}}
4.3 Budget Impact
| Cost Category | Current Budget (NOK) | Additional Cost (NOK) | Notes |
|---|---|---|---|
| Development | {{CURRENT}} | {{ADDITIONAL}} | {{NOTES}} |
| Design | |||
| Testing | |||
| Infrastructure | |||
| Total Additional Cost | {{TOTAL_ADDITIONAL}} |
Budget Impact: None / Minor (< 5%) / Moderate (5–15%) / Major (> 15%)
Funding Source for Additional Cost: {{HOW_WILL_ADDITIONAL_COST_BE_COVERED}} (e.g., contingency reserve, client additional purchase order, scope reduction elsewhere)
4.4 Resource Impact
| Resource | Current Allocation | Required if Approved | Impact |
|---|---|---|---|
| {{ROLE}} | {{CURRENT_ALLOCATION}} | {{NEW_ALLOCATION}} | {{NOTES}} |
4.5 Risk Impact
| Risk | Probability | Impact | Notes |
|---|---|---|---|
| {{NEW_RISK_INTRODUCED}} | H/M/L | H/M/L | |
| {{EXISTING_RISK_CHANGES}} | H/M/L | H/M/L | Risk score changes from {{OLD}} to {{NEW}} |
4.6 Quality Impact
- Test cases affected: {{LIST_OF_TEST_CASES_NEEDING_UPDATE}}
- Regression risk: {{HIGH/MEDIUM/LOW}} — {{EXPLANATION}}
- NFRs affected: {{LIST_ANY_NFRs_IMPACTED}}
4.7 Affected Deliverables / Documents
| Document | Section | Type of Change | Owner |
|---|---|---|---|
| {{DOCUMENT}} | {{SECTION}} | Update / Add / Remove | {{OWNER}} |
functional-requirements.md |
FR-{{XXX}} | Modify | BA |
user-stories.md |
US-{{XXX}} | Add new story | BA |
| Test cases | TC-{{XXX}} | Update | QA |
5. Alternative Approaches Considered
| Alternative | Description | Why Rejected |
|---|---|---|
| Option A (Proposed) | {{THIS_CR}} | Recommended |
| Option B | {{ALTERNATIVE}} | {{WHY_NOT_CHOSEN}} |
| Option C — Do Nothing | Reject the change | {{CONSEQUENCE_OF_REJECTION}} |
Recommendation: Option {{A/B/C}} Rationale: {{WHY_THIS_IS_THE_BEST_OPTION}}
6. Implementation Plan
6.1 Implementation Steps
| # | Task | Owner | Effort | Target Date |
|---|---|---|---|---|
| 1 | {{TASK}} | {{OWNER}} | {{EFFORT}} | {{DATE}} |
| 2 | ||||
| 3 | Update test cases for affected features | QA | {{EFFORT}} | {{DATE}} |
| 4 | Update requirements documents | BA | {{EFFORT}} | {{DATE}} |
| 5 | Regression testing | QA | {{EFFORT}} | {{DATE}} |
6.2 Dependencies
| Dependency | Type | Blocking? |
|---|---|---|
| {{DEPENDENCY}} | Internal / External | Yes / No |
6.3 Test Plan for This Change
- Unit tests: {{WHICH_UNITS_NEED_NEW/UPDATED_TESTS}}
- Integration tests: {{WHAT_INTEGRATIONS_TO_RETEST}}
- Regression scope: {{WHICH_EXISTING_FEATURES_TO_REGRESSION_TEST}}
- UAT: {{DOES_THIS_REQUIRE_CLIENT_UAT? Y/N — WHICH_SCENARIOS}}
7. Rollback Plan
Rollback Trigger: {{WHAT_CONDITION_TRIGGERS_ROLLBACK}}
Rollback Steps:
- {{STEP_1}}
- {{STEP_2}}
- {{STEP_3}}
Rollback Owner: {{WHO_EXECUTES_ROLLBACK}} Rollback Time Required: {{ESTIMATED_TIME}} Data Recovery Needed: Yes / No — {{IF_YES_HOW}}
8. Approval Workflow
8.1 Approval Matrix
| Budget / Timeline Impact | Required Approvals | Target Decision Time |
|---|---|---|
| None | PO + PM | 1 business day |
| < 5% budget OR < 3 days | PO + PM + John | 2 business days |
| 5–15% budget OR 3–14 days | PO + PM + John + Client Sponsor | 3 business days |
| > 15% budget OR > 14 days | PO + PM + John + Client Sponsor + Alem | 5 business days |
8.2 This Change Requires
- PM Review — Impact analysis complete and accurate
- Tech Lead Review — Technical feasibility and effort confirmed
- Product Owner — Requirements and priority alignment
- John (AI Director) — Delivery accountability
- Client Sponsor — Business justification and budget approval (if client-side change)
- Alem (CEO) — Budget changes > 15% (only if required)
8.3 Decision Record
| Level | Reviewer | Decision | Date | Comments |
|---|---|---|---|---|
| PM | {{NAME}} | Approved / Rejected / Deferred | {{DATE}} | {{COMMENTS}} |
| Tech Lead | {{NAME}} | Approved / Rejected | {{DATE}} | |
| Product Owner | {{NAME}} | Approved / Rejected | {{DATE}} | |
| AI Director (John) | John | Approved / Rejected | {{DATE}} | |
| Client Sponsor | {{NAME}} | Approved / Rejected | {{DATE}} | |
| CEO (Alem) | Alem | Approved / Rejected | {{DATE}} | (if required) |
Final Decision: APPROVED / REJECTED / DEFERRED Decision Date: {{DATE}} Effective From Sprint: Sprint {{X}}
9. Change Log
| Date | Changed By | What Changed |
|---|---|---|
| {{DATE}} | {{NAME}} | Updated impact analysis after Tech Lead review |
Approval
| Role | Name | Date | Signature |
|---|---|---|---|
| Author | |||
| Reviewer | |||
| Project Manager | |||
| AI Director (John) | |||
| Approver |
No comments to display
No comments to display