The answer should be obvious but I pointed out to a customer today - use a development process and tools to help your good staff work better, not to stop bad staff doing worse. If you do the later then you run the risk of implementing a rigid system that gets in the way of people and is ultimately self defeating. You need to manage your bad staff (out of the company) and not provide tooling for them. Some signs you might be doing the wrong thing are absolutes in your process definition e.g. no code can be checked in unless code coverage is at 90% [OK, I'll remove my error handling then!].