I read a lot the past few weeks about something that calls the 90% syndrome.
Basically, the syndrome describes a project that reaches about 90% completion on schedule, then stalls, finally finishing after about twice the originally projected duration.
I found old articles about this problem which describe it and tried to understand its root cause.
But I didn't find any new articles or information sources about how this problem is dealt with in Agile methodologies. Does Agile methodologies, and specifically extreme programming and Scrum, deal with this issue in some way that is different than what is done in Waterfall projects?
I believe that short cycles can have a positive impact reducing the damage and probability of this syndrome and that in XP, in particular, there are some methods such as TDD that help avoid rework and really get to done.