How do we keep environments from drifting apart?
Configuration driftManage relevant configuration as controlled information and verify important differences. Some environment variation is intentional, but unexplained drift can invalidate tests and complicate recovery.
What to do now
- Identify configuration that affects behavior
- Record authorized environment differences
- Use repeatable deployment and checks
- Investigate unexpected divergence
When to escalate
Drift creates security exposure or invalidates release evidence.
The technical owner and authorized release decision maker
Example
A configuration comparison reveals a missing timeout setting before the release.
Mistake to avoid
Making manual production changes without preserving their history.
Prevent a repeat
Review real execution evidence and maintainability alongside feature completion; do not treat an unrun test as passed.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Approvals
Track delivery tasks and attach engineering evidence; keep source control, build execution and technical controls in their actual engineering systems. See the platform
Related cases
- Developers keep adding new libraries. What should we control?Unmanaged software dependencies
- How do we know a technical project is ready for handover?Incomplete technical transition
- How do we stop approved scope from drifting between versions?Baseline version drift
- The supplier says its certificate proves our configuration is secure. Is that true?Assurance scope mismatch