1. SharePoint 2010 Governance Planning and Implementation

2. Agenda Why do you need a Governance Plan? What does Governance mean in the context of SharePoint? Governance Top Ten Governance Details for SharePoint 2010 Summary

3. … but solution success is not just about technology … Training Technology 20% Support Policies Communication Deployment Documentation

4. … and it’s easy to make mistakes Not defining policies on what to use SharePoint for (and what not to use it for) Empowering users without appropriate training and guidance Letting users manage security when they have no clue what they are doing Not treating SharePoint like an enterprise application Letting users add lots of items to a list – literally kills the server Not planning for scale and/or growth Not providing SharePoint as a centralized service for the organization Not testing the backup/recovery process

5. So, why do you need a Governance Plan? Avoid portal, team site, and content "sprawl" Ensure that content quality is maintained for the life of the portal Consistently provide a high quality user experience by ensuring that the governance plan is followed Establish clear decision making authority and escalation procedures so that policy violations are dealt with and conflicts are resolved on a timely basis Ensure that the portal strategy is aligned with business objectives so that it continuously delivers business value

6. Moreover, a Governance Plan is important because … SharePoint often overlaps with other installed applications in particular capabilities Many of SharePoint’s capabilities are not ‘required’ or ‘mandated’; users need to understand the value to get the benefit Users can do a lot – we give them “great power” and need to ensure they accept their “great responsibility”

7. What is SharePoint governance? Your governance plan defines people roles, technology and policy guidelines, and processes to resolve ambiguity, manage short and long-range goals, and mitigate conflict within an organization Your governance plan Clarifies your plan for SharePoint design and usage Creates structure and framework to measure and manage the success of your solution over time

8. Concepts Incorporated in an Effective Governance Plan People Define a clear Vision for the solution Articulate Roles and Responsibilities Technology Define policies for service levels and appropriate use Policy Articulate design and usage principles - best practices and formal policies Process Define procedures for common tasks such as creating a new site or requesting new business requirements

9. Top 10 Governance ‘Must Haves’

10. Governance Top Ten Clear Vision Key Roles and Responsibilities Deployment Model One Size Does Not Fit All Policies Guiding Principles Launch and Roll-out (Adoption) Strategy Content Management Plan Training Plan Governance Plan Document

11. 1. 1 Vision: What are the business goals? Improve collaboration with partners Create a searchable central repository of marketing assets Provide a one-stop shop for firm-wide information Share best practices and collaborate across teams with online collaboration workspaces Replace shared drives with searchable, organized document repositories Provide a platform for document management Showcase a business process dashboard

12. 1. 2 Vision: What are the business outcomes? Provide easier and more timely access to the information employees need to get their work done Provide easier and more effective mechanisms to move work between business entities, such as self-service for customers or partners, enabling outsourcing by providing business partners with access to a collaboration environment or business data on an extranet Provide an organized "one stop shop" for information by making it easier to find authoritative information Improve the ability to share and exchange information across the organization by providing an electronic publishing method that is easy for users to leverage Improve the "time to talent," the speed with which new employees become productive Capture knowledge of retiring employees in a collaborative environment

13. 2. Roles and Responsibilities Put the right team together…early Use an upgrade as an opportunity! Don’t assume SharePoint can be managed with existing resources (even if SharePoint is already in place). Getting the right people in place is an important step in the process. Include both business process and IT process contacts on the governance team Work with the PMO and standards teams within the organization to leverage ITIL, ISO, Six Sigma, and other standards that may be in place

14. Enterprise Roles and Responsibilities

15. Site Roles and Responsibilities

16. 3. Deployment Model

17. 4.0 One Size Does Not Fit All Corporate Business Taxonomy With Divisional Stakeholders Central Portal Aggregation & Navigation Division Portals Business Process Management Division News Group Reporting & Scorecards Self-Service Site Creation +Life Cycle Management Loosely Structured Group, Team, Project Sites and Workspaces Provisioned per User Individual Contributors Blogs, Social Networking

18. 5. Policies Design Policies Policies and Best Practices for Site Designers Usage Policies Clear instruction on how and when users should work with SharePoint What constitutes abuse or misuse of system How to keep information secure information When to use SharePoint versus other alternatives Help Policies Get support and training Request design and development services Request new functionality

19. 6. Guiding Principles Guiding Principles help Site Designers narrow the scope of the “possible” to focus on the “practical” and “valuable.” Guiding Principles help Site Designers make trade-offs (“if this is the problem, choose this approach”) Guiding Principles remind users of the behaviors necessary to achieve business objectives (such as “send links, not attachments”)

20. Example Guiding Principles – Design Consistent user experience Design with the end user in mind – minimize the need for training Standards tied to scope (audience) Just because you can, doesn’t mean you should (“with great power comes great responsibility”) Existing rules still apply (privacy, use of IT resources, records retention) Default access is “read only” for all – apply additional “read” security only as needed

21. Example Guiding Principles – Usage and Content Management No e-mail attachments – send links Publish once, link many 2007: Use Metadata, not Folders – more flexible in responding to a dynamic environment 2010: Use folders, inherit metadata Content management is everyone’s responsibility but site owners are accountable Content owners are responsible for ensuring their content is managed according to corporate records retention policies. The metadata paradigm shift – likely to be your biggest challenge: relevant examples are critical!

22. 7. Launch and Roll-out (Adoption) Strategy Potential Issues: The new system will require time for the company culture to adapt to it – build that time into the schedule Users may lack sufficient training – ensure they get the training they need Users may continue to do things the way they are used to – encourage users to adopt new business practices Tactics: Fun and engaging launch event “Lunch and Learn”/”Get Sharp on SharePoint” Power Users Community of Practice More on this topic tomorrow: SPC255: Driving End User Adoption!

23. 8. Content Management Plan What is the only thing we can guarantee about your solution? Everything will change! Establish who can change and approve content Establish how often content needs to be reviewed – better yet, build in automated processes to route content for review Establish policies regarding who will manage content security Establish policies on what customization is allowed on a site Establish policies for code deployment Plan for your Governance Plan to change!

24. 9. Training Plan 24 Not a “one time” thing Not just about features and functions – it’s also about guiding principles, value proposition, etc. Don’t forget that everyone is listening to the same radio station: WIIFM – make it personal! Who to train: Site Collection Administrator(s) Engineers, ops, developers, designers HELP DESK!!! End users What to train: Skills to design, manage and support Consider a variety of approaches – not everyone learns the same way More on this topic tomorrow: SPC255: Driving End User Adoption!

25. 10. Governance Plan Document Consider breaking the document into “consumable” chunks Vision, Roles and Responsibilities, Guiding Principles Policies, Guidelines/Best Practices, and Procedures Don’t include: Implementation Details Network Requirements Feature Requirements TIP: The process of creating the document is the most important part!

26. SharePoint 2010: Detailed Governance Considerations

27. SharePoint 2010 Considerations Social Computing Implications 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.

28. SharePoint 2010 Considerations Managed Metadata Consistent Terminology Better Navigation/Filtering Better Search Results Easier on Users But…potential for confusion What is Metadata? Managed Keywords vs Managed Terms Document Columns vs Social Tags

29. SharePoint 2010 Considerations Records Management In-Place Records vs Records Archive You’ll likely use both – need to decide which and when Has effect on: Record retention rules Which users can view records Ease of locating records (Collaborators vs Records Managers) Maintaining each version as a record Records Auditing Site Organization (and number of sites used) E-Discovery Security If you are doing Records Archive, you need a records manager role!

30. SharePoint 2010 Considerations Resource Governor For >5,000 Items in a List Will prevent some sites from working – know how to communicate this Content Organizer Partitioning Mechanism Do you use it? “Where did my document go?”

31. SharePoint 2010 Considerations SharePoint Customization SharePoint Designer: Off or On? Partially Trusted vs Fully Trusted Code SODA: SharePoint On-Demand Applications Excel and Access Solutions

32. Summary Establish a governance framework to ensure quality and relevance of content and to ensure that all users understand their roles and responsibilities. Make sure that you have a Governance Board with a strong advocate in the role of Executive Sponsor. Keep your governance model simple. Solutions need a strong governance model, but they don't need complicated models with lots of bureaucracy. Don't make the solution itself more complicated than it needs to be. Just because SharePoint has a cool feature doesn't mean that you need to deploy it – at least not right away. An effective Governance Plan doesn’t have to constrain every move – it has to provide guidance to users to ensure that your solution remains effective and vibrant over time.

33. Remember to fill out your evaluations onMySPCfor your chance to win two HD web cams and a designer mouse (3 prizes awarded daily)

34. Learn More about SharePoint 2010 Information forIT Prosat TechNet http://MSSharePointITPro.com Information forDevelopersat MSDN http://MSSharePointDeveloper.com Information forEveryone http://SharePoint.Microsoft.com

35. © 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.