# Why Agile Exists

Why agile emerged as a response to uncertainty and expensive late learning.

Duration: 8 min

Agile began as a response to a recurring problem: for complex work, important knowledge appears only after people see and use something real. A plan made entirely up front cannot absorb that learning cheaply.

In February 2001, seventeen practitioners from different lightweight software methods met in Snowbird, Utah. They described shared values and principles in the Manifesto for Agile Software Development. The Manifesto is a short practitioner-written reaction to heavyweight process, not a product or an owned certification standard.

The ideas began in software. Applying them elsewhere is a context-specific inference, not a claim that every kind of work should use an agile framework.

**Try it.** Choose a piece of work that has not started. Name one assumption that could be wrong, the smallest safe result that could test it, and the decision that test would change. If there is no safe or useful way to learn early, record that as a reason to use more prediction or a deliberate hybrid.

## fmap-m1-l1-v1

The native HTML explainer and equivalent written path teach why agile exists with synchronized narration, captions, chapters, and a readable transcript.

## fmap-m1-l1-digest

### Why agile exists

Traditional big-project delivery often moved through one-way phases: define requirements, design everything, build, test, then deliver. This can fit stable, well-understood work. Its weakness under uncertainty is the assumption that everything important can be known before anything real is built.

For complex work, people discover needs by seeing and using results. Late discovery can make change expensive and encourages teams to treat new information as planning failure.

In February 2001, seventeen practitioners from competing lightweight software methods met in Snowbird, Utah. They agreed on a deliberately short set of values and principles. The Manifesto was a practitioner-written reaction to heavyweight process. It is a movement's founding document, not a product or rulebook owned by a certification body.

The original document concerns software development. The broader lesson is an inference: when a setting permits a safe, usable early result, earlier feedback can improve the next decision. It does not establish that every uncertain activity should adopt a named agile method.

**Worked example.** A service team thinks a new appointment reminder will reduce missed visits. Instead of specifying a full communications programme, it can test one reminder wording with a small, consented group, check whether it changes attendance, and then decide whether to expand, revise, or stop. Privacy, safety, and operational constraints may still require predictive planning around the test.

## fmap-m1-l1-q1

Public formative answer keys are intentional. This activity does not affect completion or certificate eligibility.

## fmap-m1-g1

Use the course definition of agile rather than treating a branded framework as the definition.