Change Management
Overview
ZirconTech has established processes to document, manage, and respond to requests for changes to project scope in AWS cloud operations engagements. These practices ensure controlled scope modifications while maintaining project quality and stakeholder alignment.
Our change management is integrated with our contractual framework through Work Orders governed by the Independent Contractor Consulting Agreement (ICCA), as referenced in Section 4.1: "Any changes to the original scope will be added to the planning and will be considered business as usual."
Change Request Documentation Process
Change Request Form
Required Information: - Change Request ID (CR-YYYY-MM-DD-XXX) - Requestor name and role - Date submitted - Current state description - Proposed change description - Business justification - Expected timeline
Documentation Template:
| Field | Description |
|---|---|
| CR Number | Unique identifier |
| Requestor | Name, role, organization |
| Date | Submission date |
| Description | Detailed change request |
| Justification | Business reason for change |
| Impact | Scope, timeline, budget implications |
Change Management Process
1. Impact Assessment
Technical Impact: - Architecture and infrastructure changes required - AWS services affected - Integration complexity
Resource Impact: - Team effort required - Timeline implications - Budget adjustments
Risk Assessment: - Implementation risks - Dependencies and constraints
2. Change Classification
| Size | Budget Impact | Approval Authority |
|---|---|---|
| Minor | <5% project budget | Project Manager |
| Moderate | 5-15% project budget | Customer Project Sponsor |
| Major | >15% project budget | Executive Sponsor + Contract Amendment |
Change Response Process
Approval Workflow
Step 1: Initial Review - Technical feasibility assessment by Solutions Architect - Resource impact evaluation by Project Manager - Preliminary approval recommendation
Step 2: Stakeholder Approval - Customer sponsor review and approval - ZirconTech project manager approval - Executive approval for major changes
Step 3: Implementation Authorization - Formal approval documentation - Updated project timeline and budget - Implementation plan approval
Response Timeframes
| Change Type | Response Time | Implementation Planning |
|---|---|---|
| Minor | 2 business days | 1 week |
| Moderate | 5 business days | 2 weeks |
| Major | 10 business days | Contract amendment required |
Change Tracking and Communication
Change Log
Tracking Requirements: - All change requests logged with unique IDs - Status tracking (Submitted → Reviewed → Approved/Rejected → Implemented) - Actual vs. estimated effort tracking - Lessons learned documentation
Stakeholder Communication
Notification Process: - Change request acknowledgment within 1 business day - Status updates provided weekly - Approval decisions communicated within 24 hours - Implementation progress reported in regular project updates
Communication Matrix:
| Stakeholder | Information Provided | Method |
|---|---|---|
| Executive Sponsors | High-level impact summary | Email + Dashboard |
| Project Sponsors | Detailed impact assessment | Meeting + Documentation |
| Technical Teams | Implementation details | Technical sessions |
Documentation Templates
Change Request Template
Change Request: CR-YYYY-MM-DD-XXX
Project: [Project Name]
Requestor: [Name, Role]
Date: [Submission Date]
Current State:
[Description of current situation]
Proposed Change:
[Detailed description of requested change]
Business Justification:
[Why this change is needed]
Impact Assessment:
- Scope: [Changes to deliverables]
- Timeline: [Schedule adjustments]
- Budget: [Cost implications]
- Risk: [Associated risks]
Approvals:
□ Technical Review: [Solutions Architect]
□ Business Approval: [Customer Sponsor]
□ Project Approval: [Project Manager]
Impact Assessment Template
Impact Assessment for CR-YYYY-MM-DD-XXX
Technical Impact:
- Architecture changes: [Description]
- AWS services affected: [List]
- Effort estimate: [Hours/Days]
Timeline Impact:
- Current milestone: [Date]
- Revised milestone: [Date]
- Critical path effect: [Yes/No]
Budget Impact:
- Additional cost: $[Amount]
- Budget variance: [Percentage]
Risk Assessment:
- Implementation risk: [High/Medium/Low]
- Mitigation strategy: [Description]
Billing Integration
Time and Materials Model
Change Billing Process: - All change-related work tracked separately - Transparent billing for additional scope - Regular updates on change-related costs - Clear customer communication about billing impact
Cost Tracking: - Professional services hours for change implementation - Additional AWS service costs - Third-party tool or license costs - Travel expenses if required
Success Metrics
Key Performance Indicators
| Metric | Target |
|---|---|
| Change request response time | <5 business days |
| Change implementation success rate | >95% |
| Budget variance from approved changes | <15% of original budget |
| Customer satisfaction with change process | >4.0/5.0 |
Quality Assurance
Process Controls: - All changes require formal approval before implementation - Regular review of change management effectiveness - Post-implementation validation for all changes - Continuous improvement based on lessons learned
This documentation demonstrates ZirconTech's systematic approach to documenting, managing, and responding to project scope changes, ensuring controlled flexibility while maintaining project quality and customer satisfaction.
Last updated: December 2024