A shout out to this blog for providing a link to an Excel worksheet that is a good starting point for doing a SharePoint implementation (or reviewing an existing implementation). It’s not the prettiest thing in the world, but there’s a lot of great information even for experienced MOSS Architects.
Good question. I don’t know the exact answer (is there an exact answer for anything in technology?), but this article does a really good job of covering common sense approaches to site collection governance and MOSS. There are a few issues — what if you need to rollup content across site collections — but most of it is straight forward advice.
MOSS projects for a number of reasons, and it’s usually not the tool. (And only know this because with proper planning and design, our clients have raved about what a good product it is.) SharePoint can do great things when it’s used for what it’s designed for i.e. if you want to nail a nail, use a hammer, not a screwdriver. It’ll be ineffective if you use it like using that screwdriver.
CleverWorkarounds has a good article about it, comparing it to a drinking game which I think is classic. Again, it’s not the tool. They also have another article about selling MOSS that’s pretty “interesting”.