I think the problem there is the "on Friday" bit. "Good enough" can be any threshold you set, including rigorous security and maintainability thresholds where necessary, the arbitrary deadline isn't a part of the Agile process any more than its part of the Waterfall Model.
Also I'd have to say your answer is a bit flawed, a project that is 6000 lines of code shouldn't have a documentation trail the size of the Encyclopedia Brittanica. That's the attitude that drives people away from documentation heavy models, and its one of the great flaws with University teaching of Software Engineering, they require you to do rigorous documentation of a toy task, so the only thing it teaches people is that rigorous documentation is a pointless nuisance and waste of time.
Essentially appropriate documentation and testing for the task is the correct answer, you don't want to little or to much. If you're developing a life support system for hospitals everything should be documented and tested to the utmost extent.