Sps Ottawa Share Point 2010 Governance Best Practices


Published on

SharePoint 2010 Governance Best Practices presentation made at SharePoint Saturday Ottawa on Saturday December 1st 2012

  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Thank you for coming to this session on SharePoint Governance.Quick question; How many of you have currently deployed SharePoint? Which version 2007, 2010.How many of you are thinking of deploying SharePoint 2013?No mater which version of SharePoint you are planning on using – this session is for you.This session does not have a demo – it is all information.In May 2012 I attended the SharePoint Summit in Toronto. I was privileged to attend a session by Susan Hanley on SharePoint Governance.I was so moved by her presentation that I asked her to re-purpose it internally to my organization – they had not even considered Governance as part of our SharePoint deployment. My presentation quickly changed their minds and we are now full fledged into Governance.This presentation contains some content from that initial presentation.
  • My Biography…10 Years of SharePoint experience22 Years of IT work with the Provincial Government- Ontario (30 years with company)Seasoned IT Professional in SharePoint / Business Intelligence / Project Server / Microsoft Office / Virtualization Social Media Enthusiast (Twitter / LinkedIn / Facebook / Pinterest)SharePoint evangelist for my organization and on Social MedaiLover of Dogs – especially Westie’s & Keshounds
  • What is Governance?Why should we care?Governance is based upon reachSharePointPain PointsCollaborative Governance FrameworkGovernance ProcessImplementing GovernanceGovernance Teams (Strategic / Tactical)Governance Planning Roadmap OverviewKey points to remember…References
  • GOVERNANCE is….Definition of Governance: The set of policies, roles, responsibilities, and processes that you establish in an enterprise to guide, direct, and control how the organization uses SharePoint 2010 based solutions to accomplish business goals.Effective governance anticipates the needs and goals of both your organization's IT teams and its business divisions. Governance also provides policies and guidelines that make the deployment of products and technologies such as SharePoint Server 2010 both manageable for IT and also effective as a business tool. Governance can help protect your enterprise from security threats or non-compliance liability. It can also help promote the best return on your investment in technologies by enforcing best practices in content management or information architecture.A SharePoint 2010 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. To help get you started, we need a governance plan. The Governance plan describes how our SharePoint environment will be managed.It describes the ROLES, RESPONSIBILITIES, and RULES applied to both the back end (hardware infrastructure) and the front end (user experience architecture and taxonomy).Some features in SharePoint 2010 will be new to users of past versions of SharePoint, but "digital natives" will feel right at home with the platform because of its similarities to the "social web," which encourages users to participate actively rather than simply reading static content.The new world of SharePoint is both "flat" and "social," and an effective governance plan is critical if we want to build effective solutions on this platform
  • A set of policies, roles and responsibilities and processes to guide how organizations and divisions at Microsoft best use of SharePoint to keep SharePoint sites under control, limit security threats, and practice document lifecycle management.Helps to:Keep SharePoint sites & access under controlLimit security threatsPractice document lifecycle managementWhat do we govern? Govern Information Architecture &SharePoint Services
  • A portal or collaboration solution is only as good as the value of its underlying content. It’s hard to strike a true balance between IT Control / Security and User Adoption / Empowerment.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 save them a lot of time and energy when creating and deploying new sites.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 8: Getting Social” 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 in order to leverage. In addition, a 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 Content Management Work” 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. Our Governance Plan now needs to include decisions regarding how, where, and when to allow configuration using these expanded capabilities.
  • Demo the Model / Governance based upon “reach”SharePoint is a broad platform of technologies that can be configured and implemented in unique ways based on the organization’s needs. Any implementation—whether it's for a team, a department, or the organization as a whole—needs to adhere to organizational standards. As can be seen from the diagram above the governance policies required will vary based on the impact (number of users accessing) of the site. In case of My Sites, used for social collaboration at an individual level, the governance policies required are simpler and less constraining than for an enterprise portal or an internet site with a very large number of users accessing the content with high availability requirements.Public Sites: (Tightly controlled, formal governance)Home PageFunctional AreasPublic DivisionsPrivate Sites: (Some control, some formal governance)Private DepartmentsTeam Sites: (Looser control, less formal governance)Team SitesPersonal Sites – “My Sites”
  • Document versioning is turned on without limitation – e.g. a single document with 2GB of versionsFeatures installed in the environment and no longer used – now have to clean these up as part of the migrationEvery single FAB 40 server admin template installed and activated in the farm – installed just because and made available to everyone
  • In working with our governance committee we highlighted these major problems. Being in the IT department where our counterpart Ops team had to manage Sharepoint and meet SLA 99 up time. One of the first things we wanted to address was our exponential growth. We were going at 1 Terabyte / quarter and we needed to have proper lifecycle management.Search results are outdated and irrelevant – nobody wants to use searchWith Sites and content proliferating on SharePoint farm this made it also difficult for users to find relevant and fresh content. Sensitive information was leaked. Users inadvertantly uploading information to sites where sites where opened to broad access.
  • Governance as defined earlier is a set of policies, roles, responsibilities, and processes that are established to guide, direct, and control the use of technologies to accomplish business goals.An effective governance approach depends on:Teams that define and enforce the policies.Well defined set of policies that govern the activities of stakeholders and deployed SharePoint features.Effective use of governance features provided in SharePoint Server 2010 and associated technologies (for example, Microsoft® Visual Studio® 2010) to implement the policies.A governance plan should be created to document the governance approach. Governance plan provides a framework to facilitate the management of risk, cost, and adoption associated with a successful implementation of SharePoint.Implementation of a governance approach can be top-down or bottom-up, or a hybrid depending on the needs of the organization. The governance plan should accommodate for the evolutionary nature of the governance approach. The governance plan should help define the initial team, an initial set of policies and the implementation of the policies. More importantly the governance plan should define a set of environment characteristics (like number of sites, feature functionality, number of users, types of content, and corpus size) for each policy in which the policy is most effective.When the environment characteristics change the policy needs to be analyzed for effectiveness and updated as necessary.
  • This is the general approach taken to implementing our governance strategy. We are continual process where we working with our governance committee and reviewing our governance strategy.LCA = Life Cycle AnalysisIT = Information TechnologyIW = Information WorkerINS = Information Network SecurityOrganize Governance Committee including the following roles, LCA, Records Management, Taxonomist, IT Ops, IW worker and INS teamReview Information Architectures and identify potential inefficienciesDetermine goals & policiesOrganize contents, pilot and deploy management process & policiesDevelop Education Strategy & Training materialDevelop ongoing assessment & evaluation of Governance strategy
  • GoalsManage SharePoint growthReduce # unused site collections100% of sites compliance with classificationsClear end-user responsibility & accountability of contentPoliciesSite lifecycle management & expiration Site ownership validationSite decommission processSite storage & quota management
  • Timing: 30 secondsProvide a jumping off point that makes it easy for employees to find information. Create a hub that is the starting point of reference for the entire company globally. Microsoft is a global company so it’s important that everyone across the globe is able to find the information that they need.Provide a standard structure for other company-wide portals
  • Governance TeamsA successful deployment of SharePoint Server 2010 provides functionality that the enterprise's business divisions require in a way that is manageable and sustainable by the enterprise's IT department. It therefore requires an ongoing dialog and partnership between IT professionals, business managers, and information workers in the enterprise. To achieve this, effective governance of a deployment of SharePoint Server 2010 requires the participation of representatives of all these stakeholder groups in a governance body.The nature of any dynamic environment is a mixture between short terms (day-to-day) and long terms (strategy and vision). There should be a clear separation between strategic actions (where to go) and Tactical actions (how to do).There are two teams:Strategy:IT & BusinessTrainingUser AdoptionTacticalDevelopmentSupportOperation
  • This team consists of appropriate business owners willing to provide strategic insight and direction for the portal, who can drive strategic initiatives into their respective organizations. Resources represent a good balance between business and IT, and also centralized control versus decentralized empowerment. This team is a small, evolving team reconstructed on a quarterly basis with new volunteers to maintain a fresh perspective on the business to leverage the collective wisdom of the company. The team would have the following skills:Visionary – survey the portal landscape, developing, and directing its future directionEvangelist – serve as champions for the portal technology and what it can do for the businessUser adoption – facilitate user adoption through focused, one-on-one tutorials (primarily with executives who don’t have time to sit through training programs), incentive programs (for best collaborative sites, and so forth), and feedback surveys.Training – as primary trainer for SharePoint, will hold regular training sessions for advanced users and site administrators.Support – serve as top level support for Portal administrators and site administrators (infrastructure support will be provided by IT).Business Analyst and Developer Liaison – meet with business leaders to gather requirements for new portal projects and manage development efforts of development team.
  • Operations TeamInfrastructure (IT) resources provide operational support for the system as they help to promote the enforcement of the governance plan and manage the more routine maintenance of the system by performing nightly backups, usage monitoring and analysis, scheduled task validation, and keeping the system current with security releases and system upgrades.Support TeamSharePoint site owners, system administrators, help desk personnel, and other various support resources create an effective support system with proper channels of escalation for end users of the SharePoint environments. This team handles application questions, bugs, and other problems requiring issue resolution.Development TeamTechnically talented people both willing and able to customize, personalize, and use SharePoint in a manner that fulfills the business opportunities as identified by the strategy team. This team is a loosely-knit community of developers with varying degrees of proficiency in software development. Members can range from highly skilled programmers to technically savvy end users in charge of personalizing departmental team sites. Skilled developers will handle large change requests, new features, and program management while ensuring adherence to standards.
  • It’s easy to make mistakes..What’s wrong with putting one person in charge of the effort?Nothing – in fact, there is usually one person who leads the governance steering committee.But, with a cross-functional membership, you have a much better chance at cross-functional engagement.In fact, there is another guiding principle that helps bring this point home – we’re all responsible for the intranet.
  • It is important to PLAN!A Governance Plan establishes the processes and roles required to:Avoid solution, team site, and content sprawl (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
  • You must be prepared to commit to support your Governance Plan once created.
  • Governance Planning Roadmap courtesy of Susan Hanley:Design FirstIdentify an Inclusive TeamDocument the VisionReview the Deployment ModelDiscuss “Framing” OptionsIdentify Roles and ResponsibilitiesDevelop Guiding PrinciplesGet Social?Understand Policies / Define Guidelines Document Socialize, Promote and Verify
  • Timing: 1.5 minutesPresenter ScriptBest Practices:It’s very important to know who your audience is. Make sure to build the site to service that audience. Don’t just build a site to build a site (common in IT departments).Know who your partners are. MSIT brings people into the dogfood program that will help to drive adoptions in the future. Our customers can find business partners in their own organizations who will be their allies for rolling out services in the future.Build SLAs that you know you can deliver to. Communicate. It’s crucial to have a good communications plan. In the early days, the Microsoft SharePoint team didn’t communicate effectively, which ended up reflecting poorly on the service. For example, the team didn’t always communicate when they were going to take a site down, or sometimes they scheduled a downtime during the worst time for business without checking first to determine the impact. Things are much better that way now. Get user feedback. It’s also important to communicate successes. The SharePoint service has very high availability, but when the service is down, users tend to focus only the outage. By communicating availability statistics, users can see that those outages are actually rare occurrences. So to sum up, create strong partnerships and a good communication plan.
  • The governance plan should be about the basics:Target specific audiencesDon’t‘ read with trainingJust in time and just enough – make it consumable it digestible chunks that are easy to understand.Basics 1st, then the harder stuff (10/2 rule)
  • Lessons Learned:It’s really about both assurance and guidance – and it takes COMMITMENT – plan, plan, planNo one cares about governance – until you make it all about them!Less is more – avoid unnecessary bureaucracy – and documentsCreate and communicate a roadmapBuild best practices into your site templates and automate everything you canA governance plan doesn’t replace training … and training should include the governance plan
  • Elements of a Governance Plan:Review / discuss the chart
  • Key Points to remember…Establish a governance plan to ensure quality and relevance of contentKeep the governance model SIMPLE (Don’t OVER DESIGN)Think about how we will ensure compliance with the plan over timeAn EFFECTIVE governance plan does not have to constrain every move – it has to provide guidance to users to ensure that the solution is remains effective and vibrant over time.Ensure a strong advocate / Executive Sponsor
  • We will be drawing for a copy of “Essential SharePoint 2010 Overview, Governance and Planning” (signed by one of the authors – Susan Hanley)
  • Microsoft OverviewDescribes and illustrates how to develop a governance plan that includes IT governance, information management governance, and application management governance.http://www.microsoft.com/en-ca/download/details.aspx?id=13594
  • ReferencesMicrosoft Office SharePoint Server 2007 SharePoint Governance Checklist Guide: http://office.microsoft.com/download/afile.aspx?AssetID=AM102306291033Governance Resource Center for Microsoft Office SharePoint Server 2007: http://technet.microsoft.com/en-us/office/SharePointserver/bb507202.aspxMicrosoft SharePoint Team Blog: http://blogs.msdn.com/SharePoint/archive/2006/12/13/management-and-governance-resources.aspxGovernance overview (SharePoint Server 2010):http://technet.microsoft.com/en-us/library/cc263356(office.14).aspxPlan to share terminology and content types (SharePoint Server 2010):http://technet.microsoft.com/en-us/library/ee519603(office.14).aspxManaged metadata service application overview (SharePoint Server 2010):http://technet.microsoft.com/en-us/library/ee424403(office.14).aspxManaged metadata overview (SharePoint Server 2010):http://technet.microsoft.com/en-us/library/ee424402(office.14).aspxBest practices for My Sites:http://technet.microsoft.com/en-us/library/cc262706.aspx
  • Sharepoint 2013 Preview: Over 50 Powerpoint presentations for IT Pro'shttp://technet.microsoft.com/en-us/library/cc261970(v=office.15)
  • IvorReview the list of additional resources in Social Media that are available to assist in user adoption:SharePoint 2010 Group on LinkedInSharePoint 2013 Group on LinkedInTwitter – Hashtags - #sp2010 / #sharepointFollow us on Twitter - @BrainStormInc / @IvorDavies59BrainStorm on FaceBook (Company Page)50 Must-Follow Tweeters for SharePoint Enthusiasts
  • Sample Supplement - Quick Guide to Writing Great Content for SharePoint Sites courtesy of Susan Hanleyhttp://cloud2.snappages.com/b8898dc2c08e137d03449de65b9e82e108c15658/SharePoint_Content_Authoring_Quick_Guide.pdf
  • The End!
  • Many thanks to all the sponsors that made today possible!At the end of the day, please ensure your evaluation is signed and handed in for door prizes. The draw takes place in Room 102A.
  • Don’t’ forget about the SharePint tonight at Pub Italia!
  • Sps Ottawa Share Point 2010 Governance Best Practices

    1. 1. SharePoint 2010December 1st, 2012 Governance Best PracticesIvor DaviesSharePoint Evangelist &Senior Technical Specialist@IvorDavies59 (Twitter)
    2. 2. My Biography….– 10 Years of SharePoint experience – back to 2003– 22 Years of IT work with the Province of Ontario (30 years with company)– Seasoned IT Professional in SharePoint / Business Intelligence / Project Server / Microsoft Office / Virtualization– Social Media Enthusiast (Twitter / LinkedIn, Facebook / Pinterest / Klout / Yammer)– SharePoint Evangelist in Social Media!– Lover of Dogs!
    3. 3. Agenda:• What is Governance?• Why should we care?• Governance is based upon reach• SharePoint Pain Points• The Governance Process• Implementing Governance• Governance Teams (Strategic / Tactical)• Governance Planning Roadmap Overview• Governance Plan Elements• Key points to remember…• References
    4. 4. Governanceis…..A set of policies, roles andresponsibilities and processesto guide how organizations anddivisions at Microsoft best useof SharePoint to keepSharePoint sites under control,limit security threats, andpractice document lifecyclemanagement. 4
    5. 5. SharePoint Governance• A set of policies, roles and responsibilities and processes to guide how organizations and divisions at Microsoft best use of SharePoint to keep SharePoint sites under control, limit security threats, and practice document lifecycle management.• Helps to: – Keep SharePoint sites & access under control – Limit security threats – Practice document lifecycle management• What do we govern? Govern Information Architecture SharePoint Services
    6. 6. Why should we care? 6
    7. 7. Governance is based on “reach” Home Page“PUBLIC” SITES: Open to Tightlyall employees controlled, Function formal al Areas governance Divisions– ―Public‖“PRIVATE” SITES: Open Some control,to business group Departments – some formalmembers ―Private‖ governanceTEAM SITES: Team Sites Looser control,Generally open to less formalteam members governance Personal Sites – My Sites 7
    8. 8. SharePoint Pain Points• Too many sites; users cant find content• Users don’t know the security of the library before saving. (Not easy to know.)• Users cant remember URLs• Orphaned Team & Personal Sites, Document & Meeting Workspaces• Rollover of site ownership• Users consistently exceeding site quota• No Site Recycle Bin complicates cleanup
    9. 9. SP Pain Points Continued…• Document versioning is turned on without limitation – e.g. a single document with 2GB of versions• Features installed in the environment and no longer used – you should clean these up as part of any migration• Every single FAB 40 server admin template installed & activated in the farm – installed just because & made available to everyone
    10. 10. Problems with Unmanaged SharePoint1. SharePoint growth which is costly to manage2. Sensitive content not properly secured, information leaked3. Outdated & irrelevant search results4. Difficulty in finding desired information
    11. 11. Governance Process Define or Update Policies Implement Measure & Policies Analyze according toEffectiveness definition Enforce Policies
    12. 12. Implementing Governance• Organize Governance Committee including the following roles, LCA, Records Management, Taxonomist, IT Ops, IW worker and INS team• Review Information Architectures and identify potential inefficiencies• Determine goals & policies• Organize contents, pilot and deploy management process & policies• Develop Education Strategy & Training material• Develop ongoing assessment & evaluation of Governance strategy
    13. 13. Governance Goals and Policies• Goals – Manage SharePoint growth – Reduce # unused site collections – 100% of sites compliance with classifications – Clear end-user responsibility & accountability of content• Policies – Site lifecycle management & expiration – Site ownership validation – Site decommission process – Site storage & quota management
    14. 14. • Quality – Provide easy access to information – Intuitively designed navigation and information architecture – Offer hosting service packages – Provide feedback to teams• Awareness – Showcase SharePoint as an intranet/portal solution• Usage – Promote frequent use of SharePoint among all employees – Maintain portfolio of hosted content
    15. 15. Governance Teams Strategy Tactical
    16. 16. Strategic Team• How do we improve business processes & how do we deliver on that?• What structures need to be in place to deliver this value?• What areas of the business offer the most opportunity for growth?• How can we align our activities with the goals of the business?• Are there synergies that can be created between divisions and departments?• What ways can we reduce inefficiencies and duplication?
    17. 17. Tactical Team• The tactical team consists of three sub teams all charged with supporting the directives of the strategy team: – Operations – Support – Development
    18. 18. It’s easy to make mistakes … 18
    19. 19. …so it’s especially important to plan!• Avoid sprawl• Ensure quality• Deliver a great user experience• Consistency in UI (User Interface) experience across the portal• Consistent navigation• Clear decision-making authority• Align portal with business objectives• Communicate best practices• Content ownership (who owns the content?) 19
    20. 20. But, the plan is not enough – it must be CONSUMABLE …What percent of employees say they don’t always their company’ssecurity policies?What percent say the aren’t even of the policies? 20
    21. 21. … and most importantly, you must be prepared to 21
    22. 22. Governance Planning Roadmap 11. Socialize, Promote, Verify 5. Discuss 10. Document “Framing”1. Design First Decisions 7. Develop Guiding 4. Review the Principles 9. Understand Deployment Model Policies; Define Guidelines 3. Document2. Identify an the Vision Inclusive Team 6. Identify Roles and Responsibilities 8. Get Social? 22
    23. 23. Governance Best Practices• Define your audience• State the service opportunity• Identify stakeholders• Operational requirements (i.e., maintenance windows)• Good Communication plan• Get user feedback• What is out of scope?• Create strong partnerships
    24. 24. Governance Best PracticesTarget specific audiencesDon’t read without trainingJust in time, just enough – make it consumableBasics first, then the hard stuff – 10/2 rule 24
    25. 25. Lessons Learned• It’s really about both assurance and guidance & it takes COMMITMENT – plan, plan, plan• No one cares about governance – until you make it all about them!• Less is more – avoid unnecessary bureaucracy & documents• Create & communicate a roadmap• Build best practices into your site templates & automate everything you can• A governance plan doesn’t replace training• … & training should include the governance plan 25
    26. 26. Governance Plan ElementsGovernance Plan Description TargetElement AudienceOverview Explains the vision, why governance is important, and the All Users overall modelGuiding Principles Key statements that support the vision All UsersRoles and Describes the key roles required to ensure success Users with aResponsibilities key roleContent Authoring Describes policies and best practices for content publishing ContentPolicies and and content management AuthorsGuidelinesDesign Policies and Describes what must be done (policies) and best practices Site Owners/Guidelines (guidelines) for site configuration Solution AnalystsProcesses and Describes key processes (for example: request or de- Site OwnersProcedures commission a site) 26
    27. 27. Key Points to remember…
    28. 28. http://technet.microsoft.com/en-us/library/cc789336.aspxhttp://technet.microsoft.com/en-us/library/ff848257.aspxhttp://www.microsoft.com/download/en/details.aspx?id=23613
    29. 29. Governance – SharePoint Server 2010 Governance Areas Governance and Site Types Governance Stakeholders Governance and TrainingConcepts Governance is the set of policies, roles, Different types of sites frequently require different You must ensure that your governance policies are Typical degree of governance responsibilities, and processes that guides, directs, Central published site governance policies. appropriate to your organizations goals, and you must and controls how an organizations business Divisional published sites keep them up-to-date as business needs change. Form Typically, published sites have tighter governance divisions and IT teams cooperate to achieve and use a governance group to create and maintain the over information and application management than business goals. Group and team sites policies and include the following roles: team sites and My Site Web sites. Three major areas for governing SharePoint 2010 Projects and workspaces Information architects or Trainers Products: Each type of site should have a specific IT Service taxonomists My Site IT managers Web sites plan, so that the service level agreements match the Governance doesnt work IT governance of the software itself and the importance of the site to the organization as a Compliance officers without user adoption and services you provide Site types in a typical environment Business division whole. compliance. Influential information leaders Application governance of the custom solutions workers End-user training and you provide Financial stakeholders education, good content, and IT technical specialists Information Management governance of the Executive stakeholders search are keys to user content and information that users store in those Development leaders adoption. services. IT Governance For IT governance, you can control the services that you offer, and you can control or track software installations in your Information Management Information management is the governance of information in an enterprise — its documents, lists, Web sites, and Web Application Management How will you manage the applications that are developed for your environment? What customizations do you allow in your environment to prevent proliferation of unmanaged servers for which you cant provide support. What will you provide with each pages — to maximize the information s usability and manageability. Another aspect of information management is applications, and what are your processes for managing those applications? service, and what will you include in service-level agreements for each service? determining who has access to what content – how are you making content available internally and externally and to whom? IT Governance Information Management Application Management Tightly managed Loosely managed Strictly managed Loosely managed Centrally managed Locally managed development development Content is tagged with structured metadata, Content is tagged only socially and not Customizations must adhere to Software, services, and sites are Software, services, and sites are permissions are tightly controlled, content is tracked; permissions and archiving are not Rules about development hosted and managed centrally by a hosted and managed locally by customization policy, deployments and environments or customizations are archived or purged per retention schedules. monitored or managed. updates tested and rigorously managed. core IT group individual groups less rigid. Appropriate for: Appropriate for: Whats the right balance for your Structured content Whats the right balance for your Low-business-impact content Whats the right balance for your organization? High-business-impact content organization? Short term projects organization? Personally identifiable Collaboration information Records IT service governance Information architecture Customization policy When you develop an IT service to support SharePoint 2010 Products, a key to success is your enterprises ability to govern Information architecture determines how the information in that site or solution – its Web pages, documents, lists, and data – is Determine which types of customizations you want to allow/disallow, and how you will manage customizations. Your the service and ensure that it meets the business needs of your organization in a secure and cost-effective way. A organized and presented to the sites users. Information architecture is often recorded as a hierarchical list of content, search keywords, customization policy should include: successful IT service includes the following elements: data types, and other concepts. Service level descriptions Approved tools for development A governing group defines the initial offerings of the service, defines the services ongoing policies, and meets regularly Good information architecture supports the following goals: Processes for analyzing customizations Who is responsible for ongoing code support to evaluate success. Manageability: can the IT team effectively implement and manage the information? Process for piloting and testing customizations Specific policies regarding each potential type of The policies you develop are communicated to your enterprise and are enforced. Requirements: does the information architecture meet regulatory requirements, privacy needs, and security goals? customization, whether the customization is code- Guidelines for packaging and deploying customizations Users are encouraged to use the service and not create their own solutions – installations are tracked and rogue based or no-code (done through the user interface or Business: does the architecture add to your organizations effectiveness? installations are blocked. Guidelines for updating customizations SharePoint Designer) Multiple services are offered to meet different needs in your organization. Offering a set of services enables you to apply Questions to ask when designing a site or solution: unique governance rules and policies at various levels and costs. In addition, you can phase in services in a manageable way. How will the site or solution be structured and divided into a set of site collections and sites? Sandboxed solutions What to govern: How will data be presented? Consider using a restricted execution environment, called a sandbox, to isolate custom solutions. Sandboxed solutions cannot use certain computer and network resources and cannot access content outside the site collection they are deployed in. Sandboxed Quotas – Quota templates define how much data can be stored in How will site users navigate? a site collection and the maximum size of uploaded files. Service-level How will search be configured and optimized? solutions can be deployed by a site collection administrator. Only a farm administrator can promote a sandboxed solution to run directly on the farm, outside its sandbox, in full trust. Associate different quota templates with site collections at agreements should Is there content you specifically want to include or exclude from search? different service levels. include: What types of content will live on sites? Site lifecycle management – You can govern how sites are created, the size of sites, and the longevity of sites by using self- How will content be tagged and how will metadata be managed? Does any of the content on the sites have unique security needs? Branding service site management and site use confirmation and deletion. Length of time and approvals Consistent branding with a corporate style guide makes for more cohesive-looking sites and easier development. Store approved What is the authoritative source for terms? master pages in site galleries for consistency so that users will know when they visit the site that they are in the right place. Define Set expiration and access policies to control content in sites. necessary to create a site. How will information be targeted at specific audiences? Integrate your information architecture with your environments which parts of the template can be changed by site owners and which cannot. Allow room for sub-branding of individual team or Asset classification – Classify sites and content by value and Costs for users/departments. search strategy. Take advantage of Enterprise search features project brands. Do you need to have language- or product-specific versions of your sites? like best bets, people search, and content sources and impact of the content to the organization (such as high, medium, Operations-level agreement – which connectors for external content. or low business value/impact). Classification then controls other teams perform which operations and behaviors, such as requiring encryption for high business impact information. how frequently. Policies around problem resolution Information access Lifecycle management Follow these best practices to manage applications that are based on SharePoint 2010 Products throughout their lifecycle: Impact = Exposure Value = Availability through a help desk. Be sure to consider access to content when you design your solution and sites. This overlaps with IT Governance as you consider your If this leaks, will it hurt my If this isnt available, can my Negotiated performance targets for first entire environment. Ask the following questions: Use separate development, pre-production, and production environments (see Deployment model) and keep these business? business run? environments in sync. load of a site, subsequent loads, and performance at remote locations. Information Management: Permissions and Audiences Test all customizations before releasing initially and after any updates have been made before you release them to your IT Governance: Access Data protection (backup and recovery) – Vary the level of data How do I structure permissions in a site? How do I make this content accessible to external users? Recovery, load balancing, and failover How do I target content to specific audiences? production environment. protection that you offer based on service levels. Plan the How do I make sure that only people who need access have it? strategies. Should I use Information Rights Management (IRM) to protect content? frequency at which you back up the farms and the response time Use source code control and solution and feature versioning to track changes to code. that you will guarantee for restoring data. Customization policies. Security, infrastructure, and Web application policies – how is the system and infrastructure maintained and who has access at what levels. Are you controlling use of fine-grained permissions? Storage limits for content and sites. How to handle inactive or stale sites. Information management tools Summary of lifecycle management process Govern your content by using tools for content management, When thinking about content, consider the balance between Multi-language support. 1 Initial requirements are gathered and tasks including: the following factors. Which of these factors is the highest assigned. priority for each type of content? 2 Developers use tools to track development and Use workflows and approval for document centers and site pages store source code for customizations. Deployment governance – wherever official documentation is stored. Use approval for published Web sites to control pages. Content needs to be Shared copies 3 4 Automated builds are generated for integration testing. Build verification farm is used for additional testing (larger environments). available when users Availability Redundancy reduce redundancy, In addition to governing services that you offer, you also need to govern installations of SharePoint 2010 products in your Use version history and version control to maintain a history and need it, and where and provide one 5 Testing personnel test the customizations. they can get to it. version of the truth. environment. You can block all installations, or track and monitor installations. And you should make sure that your master document. After testing, customizations are deployed to pre- 6 installations have the current software updates installed. production environment. Use content types with auditing and expiration for document 7 Pre-production environment matches production Block installations Track installations environment as closely as possible. libraries to manage document lifecycle. 8 After verifying in pre-production, customizations are Access Consider who has deployed to production. You can block installations of SharePoint 2010 Products to An Active Directory Domain Services (AD DS) marker Manage uploads to large libraries by using the Content Organizer. access to the 9 Previous testing ensures that when customizations content. If it should prevent users from installing them to unauthorized servers named Service Connection Point identifies the SharePoint Use site use confirmation and deletion to manage site collection be secure, is it? are deployed to production, there are no unexpected issues or problems encountered. that you cannot support. You use a group policy in Active 2010 Products servers in an organization. To use this lifecycles. 10 End users use the production environment, provide Directory Domain Services (AD DS) to set a registry key on marker, create a container in AD DS and set the For example, having a single copy of a document is good for additional feedback and ideas. Issues are reported all servers that block installations. permissions for the container before you install any Identify important corporate assets and any sites that contain reducing redundancy, but it is a problem for availability and and tracked. SharePoint 2010 Products in the environment. Then, when personally identifiable information – be sure that they are properly access if it is deleted. 11 Feedback and issues are transformed to requirements and tasks, cycle begins again. secured and audited. Keep current with you or another user in your domain runs the SharePoint Products Configuration Wizard as part of installing Map out the preferred content lifecycle. What steps need to Use Records Centers to store, audit, and control records in software updates SharePoint Server 2010, this marker is set and can be compliance with regulations or laws. happen when a list item, document, or page is created, updated, or deleted? For best results, develop a long term For a full explanation of this process, see the video Development Lifecycle for SharePoint 2010 at: tracked by using AD DS. You must set this marker for each Always keep your servers current with the latest rather than a temporary solution. http://go.microsoft.com/fwlink/?LinkId=200174. domain in your organization if you want to track Determine the rules or policies that you need to have in software updates. For more information, see the installations in all domains. This marker is removed from place for the following types of items: Much of this should be covered by your document and Updates for SharePoint 2010 Products Resource AD DS when the last server is removed from a farm. records management plans, but also consider the storage Center at http://go.microsoft.com/fwlink/ Pages Blogs and Wikis costs for the content. Understand the capacity planning ?LinkID=160585. Lists Anonymous comments limits for documents and items, and keep performance and scale in mind. Documents Anonymous access Records Terms and term sets Rich media External data © 2010 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at ITSPdocs@microsoft.com.
    30. 30. References:• Microsoft SharePoint Team Blog: http://blogs.msdn.com/SharePoint/archive/20 06/12/13/management-and-governance- resources.aspx• Governance overview (SharePoint Server 2010): http://technet.microsoft.com/en- us/library/cc263356(office.14).aspx• Plan to share terminology & content types (SharePoint Server 2010): http://technet.microsoft.com/en- us/library/ee519603(office.14).aspx
    31. 31. References (continued):• Managed metadata service application overview (SharePoint Server 2010):• http://technet.microsoft.com/en- us/library/ee424403(office.14).aspx• Managed metadata overview (SharePoint Server 2010): http://technet.microsoft.com/en- us/library/ee424402(office.14).aspx• Best practices for My Sites: http://technet.microsoft.com/en- us/library/cc262706.aspx
    32. 32. Additional Resources on Social Media• SharePoint 2010 Group on LinkedIn: – http://www.linkedin.com/groups/SharePoint-2010- 1869506?trk=myg_ugrp_ovr• SharePoint 2013 Group on LinkedIn: – http://www.linkedin.com/groups?gid=3854668&trk=myg_ugrp_ovr• Twitter Hastags for SharePoint 2010 – #sp2010 / #sharepoint / #spsottawa• 50 Must-Follow Tweeters for SharePoint Enthusiasts http://www.topsharepoint.com/50-must-follow-tweeters-for- sharepoint-enthusiasts• Follow Ivor Davies on Twitter – @IvorDavies59
    33. 33. Supplement ExampleFor an example of a“quick guide” for ContentAuthoring for SharePoint,visit: http://bit.ly/H03c42 33
    34. 34. Thank You !@IvorDavies59
    35. 35. Thank you to all of our Sponsors!!
    36. 36. Remember to fill out your evaluation forms to win some great prizes! & Join us for SharePint today!Date & Time: Dec 1st, 2012 @6:00 pmLocation: Pub ItaliaAddress: 434 ½ Preston StreetParking: On street with meters $Site: http://www.pubitalia.ca/