Very tricky post this about Governance. Microsoft defines governance as "...the set of policies, roles, responsibilities, and
processes that control how an organization's business divisions and IT
teams work together to achieve its goals". SO it's basically a list that specifies Who does what, and who's responsible for a specific point in Sharepoint, wether it's infrastructure, content or regulations.
I 'd rather stay with this definition: a list of who's responsible and who's to blame, that is: who takes the decission regarding a specific doubt.
Usually, a good rule is that Servers are managed by the IT team, and the Developments are managed by the DEV team (duh!). However, there are a few gray areas between:
- Content Publishing. Usually should be definied a team inside the company (or Department) that mantains the content of the site, managed by someone aware of company highlights (release dates, news, etc). An usual good practice is that if company has a Public Relations/Press group/communications they're in charge of this part.
- Dev alignment with Business requirements. This is usually the Analyst job. But at some point a decission has do be made: if the development is OK or is missing functionality, how far they're from the business requirement and/or, a previous step: if the Business Requirement is even achievable with current Technology. At some point, the analyst has to face the owners (those folks who define the business requirements, and that in the end, should be paying for all this) and present all this info, so they take the decission.