The Steps To Effective Governance - SharePoint Saturday New York


Published on

Published in: Technology, Business
1 Like
  • Be the first to comment

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

No notes for slide
  • My dedication to you before I begin. By the end of this you will have gained 3 things. It might be new knowledge, it might be a new method but you MUST gain 3 things by the end. If you don’t my first challenge to you is to stalk me, hunt me down and make sure you get 3 things from me. Because I owe you 3 things! This is meant to help you. 
  • Dominating the skyline of Arkhangelsk, a city in Russia's far north-west, it is believed to be the world's tallest wooden house, soaring 13 floors to reach 144ft - about half the size of the tower of Big Ben. The house that Sutyagin built is also crumbling, incomplete and under threat of demolition from city authorities determined to end the former convict's eccentric 15-year project. When Sutyagin began work on his dacha in 1992, he claims he was only intending to build a two-storey house - larger than those of his neighbours to reflect his position as the city's richest man, but certainly not a contender for the Guinness Book of Records. However, convinced by a trip to see wooden houses in Japan and Norway, he concluded that he had not used roof space efficiently enough and decided to keep building. "First I added three floors but then the house looked ungainly, like a mushroom," he said. "So I added another and it still didn't look right so I kept going. What you see today is a happy accident."There were other motives too. Having grown up in a Soviet communal flat, Sutyagin said he felt lonely living by himself.Not only would his house make a perfect love nest for his molls, it could also accommodate the 18 executives at his construction company.
  • This is to set the conceptual sceneYou will see this diagram a lot.
  • A lot of this can seem daunting and I know one of the hardest things is figuring out how to do some of the things I have shown today. If you are interested in further training or assistance please let me know. Based on the number of people who are interested and the areas of interest we can schedule further training sessions to help everyone better use the SharePoint portal.It's our commitment to you that we will continue to hear your feedback and identify the issues. I encourage you to give us feedback during the coming months, and we will continue to deliver more and more functionality, more and more guidance to help you be successful with your application of SharePoint.Thank You for Reading/Listening
  • The Steps To Effective Governance - SharePoint Saturday New York

    1. 1. The Steps To EffectiveSharePoint Governance<br />Presented By: Richard Harbridge<br />#SPSNY @rharbridge<br />
    2. 2. Who am I?<br />I<br />
    3. 3. Our Goal Today…<br />From Here To Here<br />
    4. 4. Why Do I Need Effective Governance?<br />
    5. 5. There are big risks that are almost always realized when you don’t have it!<br />
    6. 6. SharePoint Sprawl<br />He was only intending to build a two-storyhouse - larger than those of his neighbors to reflect his position as the city's richest man.<br />“First I added three floors but then the house looked ungainly, like a mushroom," he said. "So I added another and it still didn't look right so I kept going…”<br />Risk: Un-Managed Sites and Content were not periodically reviewed for accuracy and relevance.<br />
    7. 7. Quality Deterioration<br />Risk: Did not ensure that content quality is maintained for the life of the portal.<br />
    8. 8. Frustration Failure<br />Risk: Did not consistently provide a high quality user experience.<br />
    9. 9. Priority Paralysis<br />Risk: Did not establish clear decision making authority/ownership and escalation procedures so that conflicts and/or policy violations are resolved in a timely manner.<br />
    10. 10. Ineffective Use of Time/Resources<br />Risk: Did not ensure that the portal strategy is aligned with business objectives so that it continuously delivers business value.<br />
    11. 11. It’s not just about insuring against or mitigating those risks!<br />
    12. 12. What does that mean?<br />Without effective governanceorganization, performance, andcapability are significantly reduced.<br />
    13. 13. Without Governance<br />
    14. 14. Executing Governance<br />
    15. 15. With Governance<br />
    16. 16. The Outcome<br />You can now communicate why Governance is important/required.<br />
    17. 17. What to watch out for…<br />It’s not insurance. It makes your SharePoint investments more successful.<br />
    18. 18. Building The Governance Teams<br />
    19. 19. How do we start?<br />
    20. 20. RecommendedGovernance Teams<br />There are typically 5 teams for SharePoint Governance:<br /><ul><li>Business Strategy Team
    21. 21. Solutions/Technical Strategy Team
    22. 22. Tactical Teams:
    23. 23. Tactical Operations Team
    24. 24. Tactical Development Team
    25. 25. Tactical Support Team</li></li></ul><li>Alternative Teams<br />If the organization or implementation is small enough you might only need to start with two and break them apart as you mature/grow.<br /><ul><li>Tactical Team
    26. 26. Operations
    27. 27. Development
    28. 28. Support
    29. 29. Strategy Team
    30. 30. Business
    31. 31. Technical</li></li></ul><li>The Strategy Teams<br />
    32. 32. Governance Teams<br /><ul><li>Business Strategy Team
    33. 33. Solutions/Technical Strategy Team
    34. 34. Tactical Teams:
    35. 35. Tactical Operations Team
    36. 36. Tactical Development Team
    37. 37. Tactical Support Team</li></li></ul><li>Business Strategy Team<br />Role: Provide strategic insight, direction and prioritization for the portal.<br />Decentralized<br />Business<br />Centralized<br />IT<br />
    38. 38. Define,Prioritize and Plan<br />
    39. 39. Ensure Clear Priorities<br />
    40. 40. Governance Teams<br /><ul><li>Business Strategy Team
    41. 41. Solutions/Technical Strategy Team
    42. 42. Tactical Teams:
    43. 43. Tactical Operations Team
    44. 44. Tactical Development Team
    45. 45. Tactical Support Team</li></li></ul><li>Solution (Technical)Strategy Team<br />Role: Provide technical insight, direction and prioritization for the portal.<br />Tip: If a business direction requires new integration or effort with other technologies then a technical representative for that technology will be necessary. <br />
    46. 46. Map Solutions to Objectives<br /> Direct Relationship Indirect Relationship<br />* Objectives should be more specific – Example purposes only.<br />
    47. 47. SharePoint will be…<br /><ul><li>Utilized by Business Users to develop and implement business solutions that use technology without IT’s direct involvement.
    48. 48. Our primary unified application delivery platform.
    49. 49. Our primary workflow/business process automation platform.
    50. 50. Our intranet and communication center for internal corporate communications.
    51. 51. …</li></ul>SharePoint will not be…<br /><ul><li>Our (external) web content management platform.
    52. 52. Our primary document management platform.
    53. 53. Our contact management platform.</li></li></ul><li>Strategic Responsibilities<br /><ul><li>Defining Clear Objectives and Priorities
    54. 54. High Level Solutions Definition and Ownership
    55. 55. High Level Platform Classification
    56. 56. Communication Planning and Management
    57. 57. Resource/Capability Management
    58. 58. Expectation Management</li></li></ul><li>Define a Governance Pyramid<br />
    59. 59. The Tactical Teams<br />
    60. 60. Governance Teams<br /><ul><li>Business Strategy Team
    61. 61. Solutions/Technical Strategy Team
    62. 62. Tactical Teams:
    63. 63. Tactical Operations Team
    64. 64. Tactical Development Team
    65. 65. Tactical Support Team</li></li></ul><li>The Tactical Operations Team<br />Role: Provide operational (IT- related) support and maintenance for the system infrastructure<br />They manage the more routine maintenance of the system by performing nightly backups, performance monitoring and analysis, and keeping the environment current with security releases and upgrades.<br />
    66. 66. Operations Responsibilities<br /><ul><li>Objectives/Priorities
    67. 67. Disaster Recovery Plan
    68. 68. Storage and Quota Policies
    69. 69. Monitoring Plans
    70. 70. Maintenance Plans
    71. 71. Service Level Agreements
    72. 72. Security Policies
    73. 73. Deployment Process, Policies, and Schedule</li></li></ul><li>Governance Teams<br /><ul><li>Business Strategy Team
    74. 74. Solutions/Technical Strategy Team
    75. 75. Tactical Teams:
    76. 76. Tactical Operations Team
    77. 77. Tactical Development Team
    78. 78. Tactical Support Team</li></li></ul><li>The Tactical Development Team<br />Role: Customize/configure, personalize, and leverageSharePointto achieve business objectives.<br />This team is a loosely-knit community who's membership ranges from highly skilled programmers to technically savvy end users in charge of personalizing departmental team sites.<br />
    79. 79. Development Responsibilities<br /><ul><li>Objectives/Priorities
    80. 80. Branding Guide
    81. 81. SharePoint Designer Policy
    82. 82. Workflow Policy
    83. 83. Development Standards (Including OOTB vs Custom)
    84. 84. Development Environment Policy
    85. 85. Testing Requirements
    86. 86. Deployment Process, Policies, and Schedule</li></ul>SharePoint Standards Online<br />
    87. 87. Deployment Process/Policies<br />Extremely Important! Ensure you have clear schedules and ownership.<br />
    88. 88. Governance Teams<br /><ul><li>Business Strategy Team
    89. 89. Solutions/Technical Strategy Team
    90. 90. Tactical Teams:
    91. 91. Tactical Operations Team
    92. 92. Tactical Development Team
    93. 93. Tactical Support Team</li></li></ul><li>The Tactical Support Team<br />Role: Provide support of the SharePoint applications and platform.<br />Creates and manages a support system with effective training and proper channels of question or issue escalation and resolution. This team should also include influential users and leaders.<br />
    94. 94. Support Responsibilities<br /><ul><li>Objectives/Priorities
    95. 95. Site Classification and Platform Classification
    96. 96. Site Provisioning Process/Questionnaire
    97. 97. User Expectations Agreement
    98. 98. Roles and Responsibilities
    99. 99. Support Agreement(s)
    100. 100. Training and Communication Plans
    101. 101. MySite Policies (Pictures)…</li></li></ul><li>Support Responsibilities<br /><ul><li>User Lifecycle Policy
    102. 102. Taxonomy Management
    103. 103. Social Policies
    104. 104. Content Standards
    105. 105. Legal and Compliance Policy
    106. 106. Search Management</li></ul>SharePoint Standards Online<br />
    107. 107. Multiple Tiers for Escalation<br />(You can’t know everything)<br />
    108. 108. Measure Support<br />Learn and use data to be proactive.<br />
    109. 109. Diversify Support<br />resources/mediums<br /><ul><li>Books and Manuals
    110. 110. Online
    111. 111. MSDN
    112. 112. TechNet
    113. 113. Blogs
    114. 114. Cheat Sheets
    115. 115. One on One
    116. 116. Classroom Training
    117. 117. Forums
    118. 118. Help
    119. 119. Etc</li></li></ul><li>Sample Support Flow<br />Consultants, MS and Vendors<br />Consultative Support<br />
    120. 120. IS <br />Use them.<br />
    121. 121. Governance Tip<br />If possible have one member in all of the Governance teams or some members across multiple teams!<br />
    122. 122. The Outcome<br />Everyone Achieves a Shared Understanding of SharePoint Related Processes.<br />
    123. 123. What to watch out for…<br />Not just documents, policies, and procedures. It is an active and ongoing process.<br />
    124. 124. Setting Up A Governance Site<br />
    125. 125. Why a Governance Site?<br />It’s a lot of content.<br />It’s a collaborative process.<br />It’s an ongoing process.<br />Each piece of content should have a clear owner.<br />Content will need tobe shared.<br />
    126. 126. Governance Announcements<br />
    127. 127. SharePoint Solutions Listing<br />In addition you can also create a ‘Roadmap’ or basically a Gantt Chart or visual indicator of solutions to show what you have achieved and where you are going with SharePoint.<br />
    128. 128. Team Rosters and Definitions<br />
    129. 129. Policies, Standards and Guidelines<br />Use Search, Metadata, and Approval Workflows to help improve management and user experience.<br />For living documents/standards that require many authors try a Wiki!<br />SharePoint Standards Online<br />
    130. 130. FAQs and a Glossary<br />SharePoint Glossary Online<br />
    131. 131. Patterns and Practices<br />
    132. 132. TeamResources and Minutes<br />
    133. 133. Feedback and Surveys<br />Embed feedback options throughout the sites!<br />Don’t forget to share stories!<br />
    134. 134. Self Help and Support Resources<br />
    135. 135. Self Help and Support Resources<br />
    136. 136. Complete Site Listing<br />Include things like:<br /><ul><li>The owner and secondaryowner of the site.
    137. 137. The purpose of the site.
    138. 138. The URL, Size, and Usage Level of the site.
    139. 139. The last time the site was engaged by the support team.</li></li></ul><li>The Outcome<br />Using the SharePoint Platform we can effectively manage SharePoint Governance.<br />
    140. 140. What to watch out for…<br />Just having the Governance site isn’t enough. Content must remain fresh.<br />
    141. 141. Governance Resources<br />
    142. 142. IS <br />Use them.<br />
    143. 143. Governance Checklist<br />
    144. 144. TechNet, Community and More..<br />
    145. 145. Frameworks<br />are <br />Use them.<br />
    146. 146. No Single “Approach”<br />Projects<br />Communities<br />Tasks<br />Practices<br />
    147. 147. Governance Triangle<br />Permanent central portal<br />- Few authors/Many readers<br />Communication Portal<br /><ul><li>Central navigation
    148. 148. Central taxonomy
    149. 149. Divisional stakeholders
    150. 150. Enterprise search</li></ul>CentralPortal<br />Departmental portlets<br /><ul><li>Departments
    151. 151. Resources
    152. 152. Business Processes</li></ul>- Few authors/Many readers<br />Increasing Strictness of Governance<br />Collaboration<br /><ul><li>Local taxonomies
    153. 153. Local search</li></ul>Semi Structured <br />Team sites<br />- Multiple authors<br />Blogs, bios, <br />Social<br />Personal<br />Above The Line versus Below The Line<br />
    154. 154. ITIL Framework<br />
    155. 155. COBIT Framework<br />
    156. 156. SharePoint Deployment and Governance using COBIT 4.1<br />Chennault & Strain<br /><br />
    157. 157. Microsoft Operations Framework (MOF)<br />
    158. 158. SharePoint Maturity Model<br />Sadalit van Buren<br /><br />
    159. 159. The Outcome<br />There is a ton of material out there to support you.<br />
    160. 160. What to watch out for…<br />External best practices, policies, standards, and ideas may or may not be the right fit.<br />
    161. 161. Steps to Effective Governance…<br />Understand The Need For Governance<br />Build Your Governance Teams<br />Understand How SharePoint Is/Should Be Used<br />Develop/Practice Guidance and Policies<br />Return to Step 2 and Repeat Steps 2 through 4<br />You Have Perfect Governance<br />You Can Never Truly Achieve Perfect Governance. So long as you are performing the steps you are achieving Effective Governance.<br />
    162. 162. Thank You Organizers, Sponsors andYoufor Making this Possible.<br />Questions? Ideas? Feedback? Contact me:<br /><ul><li>Twitter: @RHarbridge
    163. 163. Blog:
    164. 164. Email me at:
    165. 165. Resources:,,</li>