Change Management

Overview

All changes to production systems follow a structured SDLC workflow that provides traceability from requirement to deployment.

Change Process

1. Requirements — Feature requirements are captured as PREQ issues and approved by a human before proceeding
2. Planning — Technical plan created, decomposed into SREQs, approach approved by human
3. Development — Code implemented following TDD, code review performed by automated agents
4. Validation — E2E testing, UAT performed by human
5. Integration — Merged to integration branch after all checks pass
6. Release — Deployed to production

Human Approval Gates

Gate	Who Approves	What They Review
PREQ Approval	Product owner	Requirements completeness and correctness
Plan Approval	Technical lead	Architecture decisions and approach
UAT	Product owner	Feature works as specified

Emergency Changes

Process for urgent production fixes that bypass normal flow.

Evidence

Each change produces:

• PREQ issue (requirements traceability)
• SREQ issues (implementation traceability)
• Code review report (review evidence)
• E2E report (test evidence)
• Git commits with conventional messages (audit trail)

---

Last reviewed: Not yet reviewed