El documento presenta una introducción a la gobernanza de SharePoint. Explica que la gobernanza incluye políticas, roles, responsabilidades y procesos que guían cómo las divisiones de negocio y los equipos de TI colaboran para lograr los objetivos de la empresa. También describe los problemas comunes de gobernanza como la proliferación y falta de cumplimiento, y cómo la automatización de gobernanza de AvePoint puede ayudar mediante la implementación de procesos, informes y cumplimiento. Finalmente, invita a los lectores a registrarse para la beta de
5. Govenance es el conjunto de políticas, roles, responsabilidades, y procesos que orientan , dirigen y controlan cómo las divisiones de negocio de una organización y los equipos de IT cooperan para lograr los objetivos de su empresa. ¿Qué es Governance? “ ” Microsoft – http://bit.ly/nmNSbj
There are many different “angles” on SharePoint Governance, but when reading/listening to the Governance Experts in the field such as Richard Harbridge, Ruven Gotz, Paul Culmsee, Scott Jamieson, Susan Hanley, Christian Buckley all of their models and approaches fit into these three pieces. People Policy Process
The “People” in SharePoint Governance are not just from IT but from people throughout the organization. Governance Committee Executives Business Owners IT Representatives Legal Records Management Corporate Communications Human Resources They each have their own business requirements & agendas within the organization and are allocated roles and responsibilities to ensure that the SharePoint platform is aligned to these.
IT Assurance Architecture Infrastructure Disaster Recovery SLAs Performance Project Governance Project management Stakeholder management Information Governance Information Architecture Information Management Technology & Business Alignment Agreeing what the business drivers are Telling the users what they can and can’t do Continuous Improvement Continually improving the processes in place
Can’t create policies unless you can enforce them Technical limitations SLAs Complexity of building Platform built in particular way
Search Content needs to be discoverable within the system and technical decisions should not reduce this discoverability .
Lifecycle Management Proliferation of Sites is obviously a key issue, but on top of this Ownership, Accuracy and Retention of content is important. Questions such as: Are you still using this site? Do you still own the site? Are there regulated users using this site?
My Site Photos Status messages Profile Note boards
In this demonstration, I will show how administrators can configure a content lifecycle service request type instance. And then I will demonstrate what this service request experience would look like to a business user.