PRINCE2, baby. It's heavy-handed, produces mountains of paperwork that you hope to never have to look at again, and allows both parties complete clarity as to w

PRINCE2, baby. It's heavy-handed, produces mountains of paperwork that you hope to never have to look at again, and allows both parties complete clarity as to what is, and what isn't, in scope. You want to change the scope? Needs a change-request, a re-quote, a re-scope, and it all trickles back into the project plan. The only problem with this process is that it actively encourages the client to find any shred of loosely worded anything in any specification, and interpret the hell out of it, rather than having to go through change control.