Why Agile Exists
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, but the underlying challenge—acting under uncertainty while reality continues to change—appears in many kinds of work.
Reading
coreWhy 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 makes 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 underlying problem is broader than software: reality continues changing after a plan is written. Adaptive work creates earlier feedback so the next decision can use newer evidence.
References
Visual
coreThe numbers behind the reaction
The Standish Group’s 1994 CHAOS report described 16.2% of its surveyed projects as successful, 52.7% as challenged, and 31.1% as cancelled. These figures became an influential industry alarm, but the study’s sampling and definitions have been criticized. Treat them as evidence of the era’s concern, not as a universal law or a current benchmark.
Edition: The CHAOS Report, Standish Group, 1994. As of: July 2026. Review semi-annually.
References
- The CHAOS Report, Standish Group, 1994 figures recorded in the FMAP verification ledgersecondary
Knowledge check
corePractice · formative check
Check the origin and problem
Choose the best answer and use the feedback to revisit the distinction.
Concepts: uncertainty, Manifesto origin
There is no attempt limit or pass/fail state. This check does not affect lesson completion or certificate eligibility.
Activity ready. Attempts are unlimited and do not affect certificate eligibility.
Equivalent non-interactive path
Answer and feedback guide
Which assumption makes a one-way predictive process risky for complex work?
- Important requirements can be fully known before building starts (best answer): Correct. Complex work often reveals important needs only after people see something real.
- People cannot be trusted to follow plans: The limitation concerns early knowledge, not whether people can follow a plan.
- Deadlines do not apply to creative work: Adaptive work still uses time constraints; it changes how learning informs the plan.
Which description of the Agile Manifesto is accurate?
- A short set of values and principles written by seventeen practitioners in 2001 (best answer): Correct. The Snowbird group found common ground across competing lightweight methods.
- A product maintained by a certification body: Certification businesses grew around agile, but no body owns the Manifesto.
- A compliance standard organizations must pass: The Manifesto is a values statement, not an audit or enforcement standard.
References
Glossary
coreUse the course definition of agile rather than treating a branded framework as the definition.
References
Agile
A movement and way of working that values people, usable results, collaboration, and responsiveness while using feedback to adapt under uncertainty.