On the surface, this contradicts the importance of documentation, which is often lacking in projects and can cause problems. This value isn't saying that documentation is not important, but, when it comes down to a choice between finishing a project with a working outcome and incomplete documentation or the project being overtime but with full documentation, I'm pretty sure I know what the project sponsor is going to choose.

Once again, that's not to say documentation is not important; it's a question of what to value more and given the failure rates of projects, actually delivering the project on time is an achievement in itself. Documentation, if it's really important to the client, can be completed after the project has been delivered. Mind you, most of the time, this approach means the documentation never gets finished. But, if the project has been delivered—how much does it matter? Sure, later it becomes an issue, there's no argument...