When is enough enough?

Something that I constantly hear is that there are no requirements and no supplementary specifications etc.

Quite to the opposite what I want to say here is "When is enough, enough?"

I have worked on several peices of work lately where I find myself feeling like some of the documentation is being produced for the sake of it rather than to aid in the system development lifecycle. Can it be that sometimes a formal process that describes rigid artifacts for testing and development can make extra work? The simple answer is "Yes" flexibility is needed to enable discretion to be taken on what needs to be produced and how the process should be adapted to suit all different situations.