Demo: finding drift in a delivery team's design
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
review a delivery team's design against the approved Larkspur architecture and report drift. This prepares ARC-042-LAB1.
Draft outline details
Step by step
- Collect the approved HLD, the relevant ADRs, and the team's current design for order fulfilment.
- Walk the three risky decisions: ERP access only through the integration layer, payment data never stored by Larkspur, events published for stock changes.
- Planned mistake: review only the team's slide summary and conclude "no drift". Fix: ask for the actual configuration and a sequence trace; the batch job and a cached card-token table appear.
- Classify each finding: bring back to design (batch job), or change the design with an ADR (cache to speed lookups, with token-only storage).
- Write the drift log entries with impact, decision, owner, and date; agree timing with the team lead.
- Feed unresolved items into the go-live readiness view as risks.
Check your understanding
What was the planned mistake?
Show answer
Trusting a summary instead of inspecting actual configuration and flows.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.