Re:Manifesto for Half-Arsed Agile Software Development
by UK-AL on Wednesday January 15, 2014 @11:50AM
(#7064348)
That's odd because agile methods like scrum have a definition of done, which has to be complete before you can class an issue as done.
definition of Done usually includes things like written code, unit tests, code review, documented etc
I suspect most people doing a agile, don't actually do agile. And think its a term for little structure.
Agile methods, such as XP programming are highly disciplined methods, more so than traditional.
The main difference is that they react to customer change, and don't follow plan than stretches 6 months into the future. The priorities of tasks can change from sprint to sprint. Allowing the team to react to the outside world.
But then, try to suggest that there's a requirement that has changed or come to light and suddenly the "agile is open to new requirements" part of the approach is forgotten as the "progress" that's been made so far is too precious to change.
/rant