<p>In your “enterprise” work environment, how are engineers held accountable for performing code inspections and unit testing?  What processes do you follow (formal methodology or custom process) to ensure the quality of your software?  Do you or have you tried implementing a developer "signoff" sheet for deliverables?</p>

<p>Thanks in advance!</p>

<p>Update:  I forgot to mention we are using Code Collaborator to perform our inspections.  The problem is getting people to "get it" and buy into doing them outside of a core group of people.  As stalbot pointed out below it is a cultural change but the question becomes, how do you change your culture to promote quality initiatives such as reviews/unit tests?</p>

We lean heavily on ITIL concepts. While we don't need the full scale ITSM that ITIL provides, we have implemented processes that draw from some of the best practices in ITIL, specifically in the areas of Change Management and Release Management.
Code reviews are part of our RM strategy. As a change or new piece of code makes its way through our RM process, a lot of eyes look at it. Ultimately the Release Manager makes the call on approval or rework, and all of this is documented (we use TFS and SharePoint). Formal code reviews are held by the Release Manager and the technical team he selects. The primary developer for a release candidate is held accountable for adherence to standards, functionality, and a verification of a completed test plan. If the quality standards aren't met, the deliverable is rejected and the project schedule is updated to reflect the rework.
Yes, this is all very heavy. I work in government and we have complex laws to follow, specifically in the areas of taxes, ADA compliance, and so on.