Last week I had the opportunity to participate in the Tweetjam about SharePoint. One of the topics that came up was the importance of Governance. In this article I want to dive deeper into this topic and stress how important governance is within your environment.
Governance can simply be defined as a set of controls in place to ensure that your SharePoint environment remains stable, accessible and highly responsive. These are controls that you put in place to keep the environment from becoming the black hole of misplaced and misused content.
Governance in many cases, seems to be the latest buzz word, the thing that all environments have to have in order to get the stamp of approval for following best practices. The simple truth however, is that it doesn’t matter what you call it or how you manage it, as long as it is getting done.
Here are a few simple questions that I like to ask that help you see the types of areas that are typically covered in a governance plan.
- Why SharePoint? What purpose does SharePoint serve in your organization?
- If a user wants to create a new solution and they think SharePoint is a good fit for what they need, how do they go about creating one?
- Who in the organization has attended SharePoint training?
- Are there quotas in place within your environment to help control how large solutions can become?
- How does the typical user within your environment use SharePoint?
In a nutshell, a Governance plan should outline what the intended use of your environment is and then provide guidance on how users can successfully use the environment as a tool to increase their success within the organization. Once the goals are set and the process is outlined, you then look at what needs to be put in place to ensure that the environment can fulfill its intended purposes. Governance is really nothing more than creating a roadmap and then building a road to successfully reach the final destination.
Starts with the Business
The first step to any good plan is knowing where we are going. In terms of SharePoint, this means we need to understand the goals of implementation. The goals will greatly determine how we move forward and should be the guide to all things we do.
These goals should generate within the business and should be based on business needs and not technology. If we based our plans on the technology alone, we can definitely miss the mark. The goals should be owned by a single point of contact, even if that contact is a committee that is working together. These goals will help determine what we configure within SharePoint, so they need to have strong backing and encompass a large vision of the organization.
The more these goals align with the overall goals of the organization, the more successful overall user adoption will be. This is due to the fact that users will more rapidly adopt the toolset because they can see how using the toolset will help them achieve the greater goals of the organization.
It Doesn’t End with the Business
Once the business comes together and works through a set of goals for the implementation, it is important for the business to continue to work with the system administrators and developers to help develop the actionable plan to move forward with the SharePoint implementation.
While it is true that the best governance plans start with the business, it is also true that the only truly successful governance plans include information from all areas of expertise. System administrators know better than anyone how to best maintain the environment to ensure long term usability and impact. By working together, the best of both sides meet in the middle, allowing for users to have access to stable, reliable systems that help them achieve real world goals.
Continue reading this article:
Source : cmswire[dot]com