Scrum

concept
scrumagilefeedback-loopsempirical-process-control

Scrum is an agile framework for delivering work in short cycles (Sprints of one month or less) through empirical process control: transparency, inspection, and adaptation (bib). Introduced in 1995 by Ken Schwaber and Jeff Sutherland.

Three nested feedback loops

The user’s xettel identifies Scrum’s three inspect-and-adapt loops:

  1. Daily Standup — 1-day cycle. The team inspects progress toward the Sprint Goal and adapts the plan for the next 24 hours.
  2. Sprint Review — 1–4 week cycle (product loop). The team and stakeholders inspect the Increment and adapt the Product Backlog.
  3. Sprint Retrospective — 1–4 week cycle (process loop). The team inspects its own way of working and adapts its practices.

This makes Scrum a multi-frequency closed-loop system: the daily loop is the fast inner loop, the review and retrospective are the slower outer loops. Compared to OKR (quarterly), Scrum operates at 7–30x higher frequency.

Empirical process control

Scrum’s three pillars — transparency, inspection, adaptation — map directly to feedback control:

  • Transparency = observability: the system’s state must be visible to those inspecting it.
  • Inspection = the comparator: comparing actual progress against the Sprint Goal.
  • Adaptation = the effector: adjusting the plan, process, or product based on what is observed.

The user’s xettel notes that Scrum implements empirical process control and that empirical process control IS feedback control applied to work processes.

Position in the feedback frequency spectrum

In the knowledge base’s framing of management feedback cycle frequency:

  • OKR: quarterly (90-day loop)
  • Scrum: 1–4 week sprints, with daily inner loop
  • Kanban: continuous flow, no fixed iterations

Scrum sits in the middle — faster than OKR, but still batched into fixed-length sprints. The user’s xettel argues that even sprint-length loops are too slow for AI-native companies.

See also