Programmer sabotage?

First of all, about two extreme options

- manager / customer - paranoid / idiot
- The programmers really deliberately, they delay the work and / or execute them so that there is a need to rework, cut off some functions in the project further work was complicated.

Which of the options, it happens and how to deal with this customer / manager?


')
If it is more detailed, then it is natural how to fight, divide into:
- how to diagnose
- what methods of prevention (requirements for code, documentation, etc.)
- motives above all programmers?
- methods of struggle, if already launched (replacement of the composition, completion of the project, etc.)

In the case of customer paranoia, idiocy:
- how should he check suspicions in order to remove for example paranoia
- how to treat idiocy, I'm afraid of offtopic :) so let's leave the option to the pro forma, if not off the top, then the society will respond
- Is the organization of third-party audit possible?
- How do programmers relate to third-party audit?
- who can do a third-party audit?

Probably something like this list of questions, because I’m not a programmer myself, I’m more likely to have a customer role, and since I hope that if I suffer from something, I’m paranoid and not idiotic :), I decided to put this topic up for discussion, maybe that would be useful. Yes, and on this thought I pushed reading this topic here .

PS I think that the topic itself is not offtopic, if it’s not right, then if you minus it, at least write, for what, content, design, offtopic, etc. :)