Agile & Process

Scrum is an Agile framework built on fixed-length iterations called sprints (~2 weeks); the team commits to a sprint backlog and ships at the end. The Agile manifesto values individuals, working software, and responding to change.

CI merges code into a shared branch often, building and testing each merge. CD is either Continuous Delivery — automating the pipeline up to a manual prod approval — or Continuous Deployment — shipping changes to prod with no gate.

The future cost of choosing a quick, suboptimal solution now — like financial debt you repay later with interest as slower changes. In Cunningham's original sense it is a deliberate trade-off to ship sooner, not sloppy code.

Both are Agile. Scrum works in fixed sprints with committed scope measured by velocity; the goal is finishing the sprint. Kanban is continuous flow — no sprints, tasks reprioritized anytime, measured by Cycle Time.

Strategies: incremental refactoring with debt tasks in the backlog next to features, a full rewrite once flexibility is gone, or consciously accepting it. Prevention helps too: MVP prototypes, versioned APIs, and a clear definition of done.

Since every passing change ships to prod automatically with no gate, it demands strong monitoring, fast rollback, feature flags, and high automated-test confidence — teams usually automate staging first and keep prod one-click first.