Why Clean Core delivery has to be managed
What you'll learn
Clean Core is a cross-team programme competing with the feature backlog — without a named owner, reserved capacity, and someone managing the seams between teams, it stalls.
- Clean Core spans functional, Basis, security, integration, and business teams — it is not a solo refactor.
- It competes with the feature backlog, so it needs a named owner and reserved capacity or it slips.
- The burndown only stays down if remediation is continuous; new debt can outpace fixes.
Clean Core is rarely a solo refactor. It is a cross-cutting programme that touches functional configuration, the Basis/transport landscape, security roles, integration partners, and live business processes. The technical moves — the Custom Code Migration loop in module 8, the roadmap in the module 13 capstone — only land if someone manages the dependencies between those teams, the sequencing across systems, and the people whose work changes. Treating it as 'just code cleanup' is the most common way these initiatives stall.
The work also competes with the feature backlog. Without an explicit mandate, a named owner, and a slice of every sprint reserved for it, remediation is always the thing that slips. And Clean Core decays the moment new debt is added faster than old debt is cleared — the findings burndown from the management module (B1) is a trend, not a finish line — so the management job is continuous, not a one-off push.
Most of the risk, finally, is organisational rather than technical: a transport collision between two teams, a business owner surprised by a behavioural change, an exemption nobody re-reviewed. The practices in this module exist to surface those risks early, while they are still cheap to fix.
Key points
- Clean Core spans functional, Basis, security, integration, and business teams — it is not a solo refactor.
- It competes with the feature backlog, so it needs a named owner and reserved capacity or it slips.
- The burndown only stays down if remediation is continuous; new debt can outpace fixes.
- Most failure modes are organisational (collisions, surprises, stale exemptions), not coding errors.
- Managing the seams between teams is the core of delivery; the code change is the easy part.
Source notes: clean-core-curriculum (delivery synthesis)
Ask Claude
Build a prompt from this lesson + your question and open a fresh Claude chat with it pre-filled — handy for adapting a before/after pattern to your own object.