> One standout statistic was that projects with clear requirements documented before development started were 97 percent more likely to succeed. In comparison, one of the four pillars of the Agile Manifesto is "Working Software over Comprehensive Documentation."
Someone does not understand (or is intentionally misreading) the meaning of "Comprehensive Documentation".
The Agile Manifesto is not discouraging having requirements before you start implementing. It's against having a multi-month planning phase that produces hundreds of pages of detailed specs before you start implementing.
Agile development was a reaction to the status quo where that was done - and a staggeringly large percentage of projects failed.
Someone does not understand (or is intentionally misreading) the meaning of "Comprehensive Documentation".
The Agile Manifesto is not discouraging having requirements before you start implementing. It's against having a multi-month planning phase that produces hundreds of pages of detailed specs before you start implementing.
Agile development was a reaction to the status quo where that was done - and a staggeringly large percentage of projects failed.
It was called the "Software Crisis": https://en.wikipedia.org/wiki/Software_crisis