There are 3 more real world lessons learned that should be mentioned here. These problems are not limited simply to web parts and related files. Items as simple as images and as complex site definitions (the blueprints that detail the creation of SharePoint sites) are all effected by improper non-WSP deployment. Site definitions, field types, event receivers, workflow, features all must be deployed via WSP. In addition CSS files, ASPX pages, and Master Pages will need to be deployed via WSP if they are to be used farm wide. As a general rule, if the item in question will affect the entire farm it will likely need to be deployed via WSP.

So, I’m going straight to the bad practice #2 because of conversations with some peers yesterday here in the UK. We see lots of blogs and articles about SharePoint Governance, and they are all very lengthy and probably applicable to most organizations. But, what I’ve seen is the average SharePoint administrator is the Exchange Admin, firewall admin, and sometimes the accountant! The point is – many folks don’t have time to go through a lengthy governance process. But, we know what kind of trouble they’ll get in without it! So, what’s the answer? I call it ‘Bare Metal Governance”

I’ve many customers that struggle with implementation and support of best practices because of organizational politics, budget constraints, and culture. While most of the SharePoint administrators and developers I work with want to implement best practices, they face impediments and many times just give up. When this happens, one of two outcomes is often the case: