# Scrum in One Picture

Position Scrum within agile and explain its empirical loop of transparency, inspection, and adaptation.

Duration: 9 min

Scrum is a lightweight framework for tackling complex problems by delivering value in short cycles. It is one framework that expresses agile values, not another name for agile itself.

Its engine is empiricism: make the real state visible, inspect it often, and adapt from what you learn. The reusable loop is Product Backlog → Sprint → Increment → feedback → a wiser Product Backlog.

## fmap-m2-l1-v1

The native HTML explainer and equivalent written path teach scrum in one picture with synchronized narration, captions, chapters, and a readable transcript.

## fmap-m2-l1-digest

### Scrum in one picture

Scrum is a lightweight framework for tackling complex problems by delivering value in short cycles. **Lightweight** means it supplies a small skeleton rather than rules for every situation. **Complex** means the work cannot be fully known in advance. **Short cycles** bring learning back while it can still change the next decision.

Scrum is not another name for agile. Agile is a mindset; Scrum is one framework that expresses it. If Scrum's rhythms do not fit a particular stream of work, the agile mindset may still be served by another approach.

The engine is **empiricism**: make decisions from observed reality rather than prediction alone.

- **Transparency:** the real state of the work is visible.
- **Inspection:** people examine that state often.
- **Adaptation:** the next move changes in response to what inspection reveals.

Think of a cook who tastes and adjusts as the dish develops. Visibility, tasting, and adjustment make the result more responsive than following a recipe blind and hoping at the end.

The loop is Product Backlog → Sprint → Increment → feedback → Product Backlog. The ordered backlog supplies a small set of work to a fixed cycle. Daily coordination happens inside the Sprint. A usable Increment emerges, stakeholders inspect the product, and the team inspects its way of working. What everyone learns returns to a now-wiser backlog and the next cycle.

There is no phase called “finished planning.” Planning is present in every turn of the loop. Remember: Scrum is one lightweight framework; empiricism means see it, check it, change it; and the loop makes learning recurrent rather than terminal.

## fmap-m2-l1-r1

### The canonical Scrum loop

**Product Backlog** → **Sprint Planning** → **Sprint of one month or less** → **usable Increment**

Inside the Sprint: **Daily Scrum**

At the end of the cycle:

- **Sprint Review:** inspect the Increment with stakeholders; return product learning to the Product Backlog.
- **Sprint Retrospective:** inspect the team's way of working; carry one improvement into the next Sprint.

This text-first representation is the authoritative meaning of the reusable course diagram. Labels and structure carry the information; color is not required.