Your SlideShare is downloading. ×
0

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

The Steps To Effective Governance - SharePoint Saturday New York

1,295

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,295
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
31
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
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
  • Transcript

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

    ×