3 ms·

Study: 268% Higher Failure Rates for Agile Software Projects

• sharemywin 2y ago
  "However, the new research has found that projects which had a specification or documented requirements before development started were 50% more likely to succeed than those which didn’t, projects which had clear requirements before starting development were 97% more likely to succeed and projects which did not require making significant requirements changes late into the development process were 7% more likely to succeed." This is a complete mis-representation of how agile is supposed to work. Agile doesn't advocate for "no requirements" "significant requirements changes late into the development process were 7% more likely to succeed." even though your development cycle is 2 weeks you still can't change specs in the middle.