Creating a process for software development is very delicate. In a large project there are so many steps that might go wrong. It makes much sense to add process to minimise risk in these steps. But, the road to process hell is paved with good intentions!
Many people feel very passionately about certain pieces of a software development process, and may be quite persistent. It is easy to cave in and just add whatever makes remotely sense.
As an example, code reviews makes sense. Writing a document listing all review comments also sounds reasonable. But it is one of the things that makes us hate code reviews. Noone ever reads those inspection records anyway, so why write them? It sure sucks to write them. Instead, just take notes, or do the whole code review by email.
So, for each proposed process step, the claimed benefit must be weighed very critically against its cost. Because my goodness process has costs!
