1 / 42

Enforcing SharePoint Governance

Enforcing SharePoint Governance. Ken Shiomitsu AvePoint Singapore, Country Manager AvePoint Japan, COO. Ken Shiomitsu. Singaporean, brought up in Japan Pre-sales, Post-sales, Support, Product Overseeing operations in Tokyo and Singapore Co-authored SharePoint Consulting Book in Japanese

dusty
Download Presentation

Enforcing SharePoint Governance

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Enforcing SharePoint Governance Ken Shiomitsu AvePoint Singapore, Country Manager AvePoint Japan, COO

  2. Ken Shiomitsu • Singaporean, brought up in Japan • Pre-sales, Post-sales, Support, Product • Overseeing operations in Tokyo and Singapore • Co-authored SharePoint Consulting Book in Japanese • Worked in the SharePoint field for 8 years • Worked with Japanese and APAC customers • Love being active

  3. GOVERNANCE

  4. 4 What is governance

  5. Origin: Greek kybernân to steer (a ship) Latin gubernāre Medieval Latin gubernantia Old French gouverner Middle English governaunce ˈgʌvərnəns

  6. Governance is (much) bigger than SharePoint

  7. 8 What is SharePoint governance

  8. What is governance? 9 Governance defines the processes, people, policies and technologiesthat deliver a service

  9. MANAGEMENT BUSINESS GOVERNANCE SERVICE Sites Composites Communities Insights Content Search

  10. Differences in SharePoint 2013? • Governance Requirements Similar • More Data Entry Points • More Data End Points • Better Tools for Collaboration Social Cloud Mobile Apps

  11. Where the enforcement problems begin…

  12. “Site Map” http://intranet HR Finance Benefits Vacation & Sick Day Tracking Financial Performance Expense Reports

  13. Common site map (small organizations) http://intranet HR Finance Benefits Vacation & Sick Day Tracking Financial Performance Expense Reports = website = site collection

  14. Common site map (larger organizations) http://intranet HR Finance Benefits Vacation & Sick Day Tracking Financial Performance Expense Reports = website = site collection

  15. Common mistakes Site map = site hierarchy While easy to build out, manageability is constrained Governance challenges • Security management (chaos) • Policy enforcement • Classification challenges Lack of separation between portal and collaboration content Design must reflect both • Information architecture • Information management

  16. Organize and describe content Metadata Structure Relationships Inputs Knowledge Management team Librarians Content owners Subject matter experts (SMEs) Outcomes Site map (navigation) Taxonomy Search Audiences (targeting) Info Architecture vs. Info Management Information Architecture

  17. Organize and describe content Metadata Structure Relationships Inputs Knowledge Management team Librarians Content owners Subject matter experts (SMEs) Outcomes Site map (navigation) Taxonomy Search Audiences (targeting) Info Architecture vs. Info Management Information Architecture Information Management Manage the content & service Access levels (permissions) Lifecycle Storage Inputs Information management policies IT usage policies Regulatory environment SLAs Outcomes Access levels Records management Compliance Performance

  18. Organize and describe content Metadata Structure Relationships Inputs Knowledge Management team Librarians Content owners Subject matter experts (SMEs) Outcomes Site map (navigation) Taxonomy Search Audiences (targeting) Info Architecture vs. Info Management How you describe content is fundamentally different than how you manage it Information Architecture Information Management Manage the content & service Access levels (permissions) Lifecycle Storage Inputs Information management policies IT usage policies Regulatory environment SLAs Outcomes Access levels Records management Compliance Performance

  19. Does governanceinput affect your architecture? Absolutely! In fact, they’re interdependent • You cannot architect a farm without governance input • You cannot create a governable service without a solid architecture In other words, the architecture helps enforce governance policies These policies help determine how many farms, web applications, content databases, site collections you’ll need Let’s see why…

  20. Management controls and scopes SharePoint Service Isolation Service Application Configuration and Data Blocked File Types Farm SSL Zone Web Application Service Application Data Storage SLAs Content DB Quotas Ownership(Full Control) Site collection Security Permissions Features Top-level site Sub site List/Library Sub site Security Permissions [Folder] Item / Document

  21. Here’s a simple example…

  22. Translating Business Needs into Architecture Business needs • Human resources wants to work on 75 HR documents • Engineering wants to work on 25 engineering documents Policy requirements • Access to these documents must be restricted to users in respective department

  23. Information and Service Management Architecture Farm Zone Web App Service App Content DB Site collection Site Library [Folder] Document

  24. Sites Farm TEAMS Content DB Site collection Departments Content Security Engineering HR Scope(web site) Control(ACL)

  25. Farm Sites TEAMS Content DB Site collection Departments Content Security Engineering HR Business Requirements Content Security = + Scope(web site) Control(ACL) Governance Policy Management

  26. Some other examples “My Asia team must be able to collaborate locally” • Create a separate farm for users in Asia “Only my engineering group should be able to upload large AutoCAD drawings” • Store in a separate web application “I need to limit the amount of content that marketing creates” • Store in a separate site collection

  27. The Great Divide Management requirements  more “containers” • Web applications • Site collections • Content databases In order to manage something more effectively, you increase the management effort Out-of-box features scoped to a single site collection • Navigation • Security management • SharePoint Groups • Quotas, auditing, content types, content rollup, and many more

  28. The Management Headache Central Admin Too many setting pages… WebAppSettings WebAppSettings Site Collection Settings Site Collection Settings Site Collection Settings Site Collection Settings Site Settings Site Settings Site Settings Site Settings Site Settings Site Settings Site Settings Site Settings Site Settings List Settings Library Settings Site Settings List Settings Library Settings

  29. What’s the Solution?

  30. Start from the Business Collaboration Evolve Workstyle Knowledge Retention Business Intelligence Service Level Compliance Policy Governance Information Architecture

  31. Determine the Scope • 9. Contribution from Individuals • E. Publishing to Customers(Internet) • 8. Portals for Individuals • 7. Business Middleware • D. Collaboration with Partners (Internet) • 6. EUC Business Middleware • C. Collaboration with Subsidiaries (Extranet) • 5. Team Sites/Project Sites • 4. Business Portals • B. Global Collaboration(Intranet) • 3. Department Portals • 2. Corporate Document Center • A. Internal Collaboration (Intranet) • 1. Corporate Portal and Search • Business Usage • Access Scope

  32. Defining the Service Multiple Platforms, Scattered Collaboration One Platform, Evolved Collaboration Department Publishing • File Sharing Functions • Workflow Functions • Document Repository Functions Intranet Functions Public Folders Intranet Mail (5TB) Corporate Portal • Corporate Portal File Server (50TB) Department Site Operations Site Meeting Site Project Site Personal Portal • Personal Portal Community Site Role Oriented Site My Sites

  33. 1. Find the right balance when making design decisions Usage Control Considerations • Scalability • Performance • Ease of administration • Future requirements • Upgrade • Budget Most all are trade-off decisions Business Needs Technical Needs

  34. 2. Separate site map from architecture • Site Map (the “Interface”) http://apps http://apps http://intranet http://teams http://teams http://intranet http://intranet Site Collection / Site Collection / Finance HR Site Collection Engineering Site Collection Finance Site CollectionHR Search MMS User Profile Service Vacation & Sick Day Tracking Financial Performance Expense Reports Benefits Site Collection Custom App • Service Architecture (the “Back end”) HR Engineering Finance

  35. 3. Find ways to simplify administration If you can administer multiple objects at once • Farms • Web applications • Content databases • Site collections • … You can • Manage access, groups, provision users, audit • Enforce policies such as “We require checkout enabled for each library in the http://teams web application” • Minimize administrative burden Security Configurations Reports Search

  36. How is this done? Adaptive navigation • Manual top-link and quick launch menus • Third-party or custom navigation controls • Use portal site connection to link site collections together • Search-based navigation Automated administration • PowerShell • Write custom code • Consider automated provisioning for things like sites and site collections • Use third-party administration tools

  37. Enforcement best practices • Only define policies that can be enforced • Use your service architecture to proactively enforce as much as possible (automated) • Determine how other policies get enforced • Do not try to automate everything Manual Enforcement Semi-automated Automated Enforcement

  38. Important questions to ask… Have users been trained on your governance plan? • Don’t teach users how to use SharePoint • Train users to achieve the requirements of the solution • Have it involve day-to-day activities Will your users do the right thing? Are resources available to enforce? Has the farm been architected with governance in mind?

  39. Resources • TechNet • Governance resource center • http://technet.microsoft.com/en-us/sharepoint/ff800826.aspx • Governance features • http://technet.microsoft.com/en-us/library/cc262287.aspx • Plan for Software Boundaries • http://technet.microsoft.com/en-us/library/cc262787.aspx • White Papers: http://www.avepoint.com  Resources

  40. PLATINUM Sponsor Booth #2 Join AvePoint at Booth #2 Mini session both on Day 1 and 2 Microsoft Surface raffle on Day 2 Book Signing on Day2

  41. Thank you to our sponsors

More Related