Where do you begin when your organization decides to deploy the SharePoint collaboration platform? What are the...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
key aspects of implementing this widely used technology? Essential SharePoint 2010: Overview, Guidance, and Planning by Scott Jamison, Susan Hanley and Mauro Cardarelli aims to answer these questions and more surrounding planning and implementing SharePoint to get valuable business results from across the enterprise. Our featured excerpt from the chapter, “Planning for Governance,” addresses the importance of SharePoint governance, what a governance plan is, how one is created and who should be responsible for its vision, principles and guidelines. In short, it offers a starting point for your research into the topic.
The governance plan describes how your SharePoint environment will be managed. It describes the roles, responsibilities, and rules applied to both the back end (hardware, farm, application, database configuration, and maintenance) and the front end (information architecture, taxonomy, and user experience). Effective governance planning is critical for the ongoing success of your SharePoint solution. In the previous edition of this book, we embedded the discussion of governance in the chapter on strategy. In this edition, we give governance a well-deserved chapter of its own but focus primarily on front-end governance because this is the topic that is, quite frankly, hardest to get right. A good governance plan is “necessary but not sufficient” to ensure success, so be advised: A governance plan alone will not guarantee the success of your solution. You still have to ensure that the governance plan is applied. However, not having a governance plan or having a plan that is either impractical or unrealistic is a clear recipe for disaster. This chapter contains the following key sections:
■ Why Is Governance Planning So Important?
■ How Do I Create a Governance Plan?
■ What Is in the Governance Plan?
Why Is Governance Planning So Important?
A portal or collaboration solution is only as good as the value of its underlying content. A strong governance plan is essential to ensure that a solution delivers worthwhile content to its users in an effective way. Moreover, governance planning is especially important for SharePoint solutions because SharePoint is designed to empower end users who are typically not Information Technology (IT) or content management experts and may not be aware of best practices that will not only improve usability but also save them a lot of time and energy when creating and deploying new sites.
Excerpted from Essential SharePoint 2010: Overview, Guidance, and Planning by Scott Jamison, Susan Hanley and Mauro Cardarelli (Addison-Wesley). ©2011 Pearson Education, Inc. All rights reserved. Printed with permission from Addison-Wesley, a division of Pearson Education. Copyright 2011. For more information on this title and other similar books, please visit www.pearson.com.
Read a Q@A with the author about key governance issues
A governance plan establishes the processes and roles required to
■ Avoid solution, team site, and content “sprawl” (that is, unmanaged sites and content that is not periodically reviewed for accuracy and relevance) by defining a content and site review process.
■ Ensure that content quality is maintained for the life of the solution by implementing content quality management policies.
■ Provide a consistently high-quality user experience by defining guidelines for site and content designers.
■ Establish clear decision-making authority and escalation procedures so policy violations are dealt with and conflicts are resolved on a timely basis.
■ Ensure that the solution strategy is aligned with business objectives so that it continuously delivers business value.
■ Ensure that content is retained in compliance with record retention guidelines.
Win a free copy of this book
Want to win a free copy of Essential SharePoint 2010: Overview, Guidance, and Planning? Email us a question for the author on SharePoint governance or planning, and you will automatically be entered to win.
Adoption of a new SharePoint solution often involves a dramatic change in user behavior—specifically, greater integration of technology into day-to-day work and increased collaboration. In more traditional IT solution deployments, the solution business logic changes relatively infrequently. In a SharePoint solution, both the back-end database and business logic change frequently and often significantly. Moreover, the business, market, and technology are guaranteed to change during the lifetime of the solution. This implies that business stakeholders must be continuously engaged given that SharePoint’s ability to meet user needs is critically dependent on areas such as data quality, content relevance and currency, and frequent updates, all of which are business user responsibilities.
What new aspects of governance do you need to consider for SharePoint 2010?
■ Governance planning is even more important in SharePoint 2010 because the increased emphasis and availability of social computing features means there are more types of content to govern.
■ SharePoint 2010 offers users a far more participatory role in the solution information architecture through the use of “social data” such as tags, bookmarks, and ratings. Users need to understand and internalize the value proposition for leveraging these features. Solution designers will likely need to provide both guidance and encouragement for their use. Refer to Chapter 7, “Getting Social: Leveraging Community Features,” for additional governance guidance regarding the use of SharePoint 2010’s social computing features.
■ SharePoint 2010 introduces new capabilities for sharing metadata across multiple Site Collections and even server farms, which require planning and control to leverage. An additional new role is required to manage and maintain the dictionary of shared metadata.
■ SharePoint 2010 includes new and more user-friendly records management capabilities, including the ability to declare a record “in place.” (Refer to Chapter 6, “Making Enterprise Content Management Work: Documents and Records,” for a description of the new records management capabilities in SharePoint 2010.) While many organizations had records management plans and policies for their MOSS 2007 implementations, enforcing and acting on these plans was not consistent. The new records management capabilities introduce an opportunity to create and enforce your records management plan.
■ SharePoint 2010 offers many more opportunities for users to customize their sites with easy-to-apply themes, SharePoint Designer, and the opportunity to create “sandbox solutions.” Your governance plan now needs to include decisions regarding how, where, and when to allow configuration using these expanded capabilities.
You should prepare a governance plan prior to the launch of your solution, but do not think of it as being “done” at any one point in time. Your governance plan is a living, breathing document—make time in your project plan to revisit the plan as you learn more about how users are using the solution and capture feedback from their experiences. As your SharePoint environment evolves, revisit your governance plan to adapt to changing needs. You may find that you need greater oversight to ensure conformance. You may also find that you need less oversight to encourage more creative application of core features.
Communicating the substance of the governance plan is a core component of launch planning and the ongoing management of your SharePoint environment. It is especially important to ensure that page and site owners understand and commit to the content management responsibilities included in the roles and responsibilities section of your governance plan. Integrate relevant elements of your governance plan into the training and ongoing support you provide for site and content owners.
How Do I Create a Governance Plan?
If you are documenting your governance plan for the first time, you will probably find it most effective to put together a small team to help define the key “framing” decisions for governance and then divide up the work to document the details among the team members. The team should clearly include representatives from IT who are responsible for overall IT system use policies, but you will also want to include representatives from the team responsible for system maintenance within IT and outside of IT, people who can represent the interests of those responsible for training, human resources, corporate communications, and if this role exists, people responsible for knowledge management in the organization.
Use the vision statement your SharePoint project sponsors and stakeholders established as a foundation for your governance plan. Identify the basic governance principles at a high level before beginning to draft the actual governance plan. Meet with team members who have the appropriate expertise to draft sections addressing how the various aspects of your environment will be managed. Review each major component of your plan with sponsors, stakeholders and core team members to ensure you are in agreement about the major components of the plan: vision, guiding principles, roles and responsibilities, and key policy decisions.
ABOUT THE AUTHORS
Scott Jamison is managing partner and CEO of Jornata, a SharePoint and Microsoft Online Services consulting and training firm. He was previously director of enterprise architecture at Microsoft and led Microsoft-focused consulting teams at Dell.
Susan Hanley, president of Susan Hanley LLC, is an expert in designing, developing and implementing portal solutions, specializing in information architecture, user adoption, governance and metrics. Her clients include many of the world’s largest global SharePoint deployments.
Mauro Cardarelli is a SharePoint evangelist who has been active in the SharePoint community since 2001. He has 20 years’ experience designing and building technology solutions.