The usual fallacious argument that agile = no spec
Agility never asked to stop writing specs; it showed a path to work in an iterative fashion to drastically shorten the feedback loop and, in doing so, reveal misunderstanding and inadequacy earlier instead of after a 6-month or multi-year execution phase.
Developers chose to ignore what they were taught in school and forgo design work, not the Agile Manifesto.
That's the wonderful thing about the Agile Manifesto - it says so little you can use it to justify anything.
Specs? The agile manifesto never said to stop writing specs!
Standups? Checmkate waterfallists, the agile manifesto never mentioned that!
Real software engineers have written written real papers on these things. We can forego the manifesto, which is just a few platitudes from consultants on a website.
The usual fallacious argument that agile = no spec Agility never asked to stop writing specs; it showed a path to work in an iterative fashion to drastically shorten the feedback loop and, in doing so, reveal misunderstanding and inadequacy earlier instead of after a 6-month or multi-year execution phase. Developers chose to ignore what they were taught in school and forgo design work, not the Agile Manifesto.
That's the wonderful thing about the Agile Manifesto - it says so little you can use it to justify anything.
Specs? The agile manifesto never said to stop writing specs!
Standups? Checmkate waterfallists, the agile manifesto never mentioned that!
Real software engineers have written written real papers on these things. We can forego the manifesto, which is just a few platitudes from consultants on a website.