DevOps Professional · Module 8: Architecture decisions and defense · Lab
Revise the Design When a Requirement Changes
50 min hands-on · Advanced
The L70 comparison plus a changed-requirement brief (capacity doubling or new security rule); the ADR file as the working document.
Local guide: run the steps below on your own machine in order, then check the validation list.
Objectives
- Write the change brief naming invalidated comparisons
- Supersede with revised numbers, not patches
- Notify affected fixture teams with timeline and support
Step 1
Brief the change
Write the one-page brief: what changed, which comparisons it invalidates, who is affected, by when. Quote the invalidated numbers from the L70 record.
Step 2
Supersede cleanly
Write the new ADR with revised numbers for exactly the invalidated parts, link the old as superseded, and record the migration cost honestly. No silent edits to the old record.
Step 3
Tell the teams
Notify the affected fixture teams with the brief, the new decision, timeline and migration support. Record the notification; surprise is the failure mode being practiced against.
How to confirm it worked
- Change brief with invalidated comparisons quoted
- Superseding ADR linked with honest migration cost
- Team notification recorded with timeline and support