01. Sprint Chaos Without Principles — Heroic starts, cursed endings¶
~12 min read. Sprint 1 feels brave. Sprint 5 feels strangely haunted.
Built on the ELI5 in 00-eli5.md. the compass —
reminder of the decision framework — explains why every urgent ticket becomes a fresh argument.
1) Why early speed lies¶
Look. At the start, almost any team looks efficient. The backlog is small.
The architecture is still soft. The crew is excited. The course feels obvious.
So even weak habits hide well. A shaky process still produces visible motion. That is why Sprint 1 feels heroic.
Now see the same team later. More tickets arrive. Different stakeholders pull in different directions.
Bug fixes mix with experiments. Latency worries join quality worries. Security reviews appear.
Now weak principles stop hiding.
┌──────────────┬──────────────┬──────────────┐
│ Sprint 1 │ Sprint 3 │ Sprint 5 │
├──────────────┼──────────────┼──────────────┤
│ fast choices │ repeated │ repeated │
│ small scope │ confusion │ arguments │
│ few voices │ more voices │ slow motion │
└──────────────┴──────────────┴──────────────┘
│
▼
velocity hides drift
Demos still work. But each rushed decision bends the course slightly. Each missing rule weakens the compass.
Each undocumented compromise leaves the ship's log blank. Simple, no? You do not feel the damage immediately.
You feel it after compounding.
2) What actually compounds under the surface¶
So what to do? First name the invisible pile. It is not only technical debt.
It is decision debt. It is expectation debt. It is coordination debt.
It is risk debt. See the pattern. One urgent ticket asks for a faster model swap.
Another wants a new prompt chain. A third wants more logging. A fourth wants cheaper inference.
None of these asks are silly alone. The danger is unframed choice. Without the compass,
the team debates tools instead of principles. Without the course, every stakeholder imagines a different destination.
Without the crew aligned, handoffs become polite confusion. Without the weather check,
reversible experiments get treated like long-term commitments. Without the ship's log, the same debate returns next Tuesday in new clothing.
Yes? That is why urgent work starts feeling heavier. The work did not merely increase.
Ambiguity increased. And ambiguity compounds faster than ticket count. A cursed sprint is usually a confused sprint.
Not a lazy one.
3) Why this separates seniors from Leads¶
A strong senior can solve a hard ticket. That matters. A Lead must prevent ten future tickets from becoming philosophy fights.
That matters more. See the difference. The senior asks,
'How do we fix this case well?' The Lead also asks, 'What rule will guide the next five cases?'
The senior protects local quality. The Lead protects system clarity. The senior may spot a better library.
The Lead notices the crew has three different success definitions. The senior moves the boat through one wave. The Lead keeps the course steady through the whole route.
┌────────────────────┬──────────────────────────┐
│ Strong senior │ Effective Lead │
├────────────────────┼──────────────────────────┤
│ solves the ticket │ solves and sets rule │
│ optimises locally │ aligns the crew │
│ spots code issues │ names decision criteria │
│ ships this sprint │ protects future sprints │
└────────────────────┴──────────────────────────┘
When principles are missing, a senior feels busy. A Lead feels nervous.
Because the Lead can already see the recurring trap. Simple, no?
4) The minimum principle kit for AI work¶
Do not start with a giant manifesto. Start with a few repeated rules. See this starter kit.
- Prefer reversible choices when uncertainty is high.
- Write down one-way decisions in the ship's log.
- Match evidence level to investment level.
- Separate experiments from production promises.
- Use the weather check before adding new operational risk.
- Keep one visible compass for trade-off decisions. That is enough to change team behaviour. Why? Because repeated language creates repeated judgement.
Soon the crew starts asking better questions. Is this reversible? What evidence do we have?
Did we document why option two lost? What risk are we importing? Does this fit the course?
See how calm those questions feel. They do not slow good teams. They stop fake speed.
And fake speed is what poisons Sprint 5. A team without principles keeps rediscovering itself. A team with principles keeps refining itself.
That is the real separation.
Where this lives in the wild¶
- GitHub Copilot for Enterprise — engineering lead must stop every integration request from becoming a fresh architecture argument.
- Customer support copilot — product manager must align refund policy logic, escalation rules, and model behaviour across teams.
- Internal RAG search tool — platform lead must keep indexing, latency, and access-control decisions coherent across sprints.
- AI voice assistant for banking — delivery manager must balance compliance, speed, and reliability without weekly strategy resets.
- Healthcare summarisation workflow — staff engineer must protect quality criteria when research spikes keep changing scope.
Pause and recall¶
- Why can velocity look healthy while confusion is already compounding?
- Name three kinds of debt that grow when principles are missing.
- What extra question does a Lead ask beyond the senior's ticket-level question?
- Which placeholder keeps repeated decisions from being debated again later?
Interview Q&A¶
Q: Why does sprint chaos show up later instead of immediately?
A: Early sprints have less surface area, so weak rules stay hidden. Complexity later exposes every missing principle at once.
Common wrong answer to avoid: Chaos starts only when the team grows too slowly.
Q: Why is velocity alone a dangerous health metric here?
A: Closed tickets can hide growing ambiguity, rework, and unresolved trade-offs. Motion is not the same as aligned direction.
Common wrong answer to avoid: If tickets close fast, the system is definitely healthy.
Q: What separates a Lead mindset from a strong senior mindset?
A: The Lead creates reusable decision rules for future work, not just strong local fixes for current work.
Common wrong answer to avoid: Leads mainly review more pull requests and attend more meetings.
Q: Why do AI teams feel this pain faster than many normal feature teams?
A: AI work mixes uncertainty, evaluation gaps, cost trade-offs, and stakeholder anxiety. That combination punishes fuzzy principles quickly.
Common wrong answer to avoid: AI teams are chaotic only because models are immature.
Apply now (5 min)¶
Exercise: Pick one recent sprint. List three moments where urgent work triggered a hidden architecture debate.
For each moment, write the missing principle in one sentence. Sketch from memory: Draw Sprint 1, Sprint 3, and Sprint 5 as three boxes.
Under the boxes, label where the course drifted, where the compass failed, and where the ship's log stayed blank.
Bridge. Once the team wants a compass, the first real test appears fast: build vs buy. That choice reveals whether principles are real or decorative.