Your SlideShare is downloading. ×
Fitting SharePoint into an IT Operations Model
Upcoming SlideShare
Loading in...5
×

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

Fitting SharePoint into an IT Operations Model

3,173
views

Published on

In many organizations, IT’s role in SharePoint is primarily reactive. SharePoint farm is installed and just handed over to users without any operating model, governance and/or proper training. …

In many organizations, IT’s role in SharePoint is primarily reactive. SharePoint farm is installed and just handed over to users without any operating model, governance and/or proper training. SharePoint being SharePoint, grows organically and takes deep roots within the Organization. Eventually, IT management realizes how essential SharePoint has become for their organization. Everyone agrees that they need to invest more in SharePoint infrastructure, services and support. But, where should we start? Should we just hire more people? Should we train our existing staff? How do we manage operating costs? What’s the chargeback model?

Published in: Technology

0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
3,173
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
4
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
  • Tradition web for collaborationIt takes too long to service tickets Users don’t have control over managing their own content. Creating new site is a long and involved project. Huge development effort.Branding is hard to maintain.Different groups have different sites. People within different groups started taking the role of a web master.
  • In
  • Server Side v/s Client SideThis guy is a code warrior… he knows his way around visual studio… he can probably code something faster than the time it takes to find if the functionality is available OOTBThis is the guy you will go to when you need to …
  • Legal / regulatory requirements.
  • Transcript

    • 1. Fitting SharePoint in IT operating model
    • 2. Operating Model
      An operating model is a set of guidelines for business architecture that enable a company to grow it’s business.
    • 3. IT Operating Model
      An operating model is a set of guidelines for business architecture that enable IT to grow it’s business.
    • 4. IT Operating Model
      An operating model is a set of guidelines for business architecture that enable IT to grow it’s services.
    • 5. IT Operating Model
      An operating model is a set of guidelines for technology and infrastructurethat enable IT to grow it’s services.
    • 6. SharePoint Operating Model
      SharePoint operating model is a set of guidelines for technology and infrastructurethat enable IT to grow it’s SharePoint services.
    • 7. People
      Governance
      Costs
      Key areas of SP Operating Model
    • 8. Before SharePoint
      “I have other, more important things to worry about” - CTO
      “I am overwhelmed” - IT
      “I hate our websites. We need something better” - Stu
    • 9.
    • 10. Everyone is Happy
    • 11. SharePoint grows like this
    • 12. After SharePoint
      How am I supposed to know what happened? I don’t even use SharePoint. Besides, the server is up and all the services are running” - IT
      “Just get it fixed.” - CTO
      “I can’t do my job. IT needs to get their act together and fix SharePoint.” - Stu
    • 13. Let’s hire a SharePoint guy!
      We don’t have any governance. That’s the problem!
      Let’s throw more hardware at it!
    • 14.
      • Should we hire more people?
      • 15. Should we train existing staff?
      • 16. Who needs training?
      • 17. What kind of Governance do we need?
      • 18. Do we need capacity planning, reporting, monitoring…?
      • 19. How to manage operating costs?
      • 20. What’s the chargeback model?
      • 21. Will it scale?
      Where do we start?
    • 22. Our Goal Today
      PEOPLEYou’ll be able to explain the different SP roles and responsibilities.
      You’ll be able to estimate how many people you need in your SP team.
      GOVERNANCE
      You’ll be able to explain why Governance is important.
      You’ll be able to identify what Governance will NOT do for you.
      You’ll be able to find more governance resources.
      COST
      You’ll be able to determine if chargebacks are right for you.
      You’ll be able to differentiate between different types of chargeback models.
      1
      2
      3
    • 23. 1
      People
      SharePoint team, Roles and Responsibilities
    • 24. SharePointConsultant
      Content Manager
      SharePointDeveloper
      Power User
      SharePoint Administrator
      Roles
      Project Manager
      SharePoint Architect
      Business Analyst
      SSP Administrator
      SharePoint Solutions Architect
      SharePoint Designer
      SharePoint Trainer
      Site Collection Administrator
      Farm Administrator
    • 25. SharePoint Consultant
      Content Manager
      SharePoint Developer
      Power User
      SharePoint Administrator
      Roles
      Project Manager
      SharePoint Architect
      Business Analyst
      SSP Administrator
      SharePoint Solutions Architect
      SharePoint Designer
      SharePoint Trainer
      Site Collection Administrator
      Farm Administrator
    • 26. SharePoint Administrator
      • Monitors and manages SharePoint farm.
      • 27. Manages services related to SharePoint.
      • 28. Maintains backups.
      • 29. Installs solutions, patches, third party software,
      • 30. PowerShell expert.
      • 31. Has working knowledge of other products such as Windows Server, SQL Server, IIS, Active Directory, MS Exchange.
      • 32. Maintains a basic understanding of .NET framework and ASP.NET.
    • SharePoint Developer
      • Knows his/her way around visual studio.
      • 33. Writes custom web parts. Understands business needs when developing solutions.
      • 34. Tests, debugs, deploys and documents custom solutions.
      • 35. Has a deep understanding of OOTB SharePoint web parts and functionality.
    • SharePoint Designer
      • Manages all visual content in SharePoint.
      • 36. Creates and maintains custom master pages, templates.
      • 37. Creates and maintains custom CSS and JS.
    • SharePoint Architect / Consultant
      • Knows SharePoint at a granular level.
      • 38. Understands what is available OOTB and knows the limitations of OOTB features.
      • 39. Can help out with either development or administrative tasks.
    • SharePoint Power Userno-code developer
      • Very important role.
      • 40. SharePoint Evangelists.
      • 41. Self-proclaimed SharePoint Designer experts.
      • 42. Candidates for SharePoint Governance / Steering Committee.
    • SharePoint Administrator
      SharePoint Developer
      SharePoint Designer
      SharePoint Architect / Consultant
      Power User
      Roles
    • 43. How many people do I need to hire/ train?
    • 44. How many people do I need to hire/ train?
      “It depends” on –
      • The number of SharePoint Farms
      • 45. SharePoint Version
      • 46. Type of install – internet, intranet, extranet
      • 47. Database Size
      • 48. Number of Users
      • 49. Branding Consistency?
      • 50. Training needs?
      • 51. Governance model?
    • Next up… Governance
      PEOPLEYou’ll be able to explain the different SP roles and responsibilities.
      You’ll be able to estimate how many people you need in your SP team.
      GOVERNANCE
      You’ll be able to explain why Governance is important.
      You’ll be able to identify what Governance will NOT do for you.
      You’ll be able to find more governance resources.
      COST
      You’ll be able to determine if chargebacks are right for you.
      You’ll be able to differentiate between different types of chargeback models.
      1
      2
      3
    • 52. 2
      GOVERNANCE
      and the role of IT
    • 53. Why do I need effective governance?
      • Ensure content quality (accurate and relevant)
      • 54. Provide quality user experience
      • 55. Deliver business value
    • Why do I need effective governance?
      • CONTENTEnsure content quality (accurate and relevant)
      • 56. UI / UXProvide quality user experience
      • 57. FUNCTIONALITYDeliver business value
    • Governance is not a project. It’s a process.
    • 58. Governance will not fix your SharePoint Farm.
    • 59. Don’t try to boil the ocean. You’ll only kill fish!
    • 60. Operational v/s Solution Governance
      Addresses Infrastructure, farm-level policies and architecture, SLAs
      Addresses how to manage solutions over time as they evolve in response to ever changing business needs.
    • 61. Essential elements of Operational Governance
      Availability
      Redundancy
      Monitoring
      Backup and Recovery
      Retention and Disposition policies
      DR
      Recovery Time Objective (RTO)is the duration of time and a service level within which a business process must be restored after a disaster or disruption.
      Recovery Point Objective (RPO)describes the acceptable amount of data loss measured in time.
      AvePointDocAve
    • 62. Essential elements of Solution Governance
      Site Lifecycle Management
      Provisioning, Retention, Archival
      Self-Service site creation
      MSIT Delete Capture
      Branding
      Classification of Content and Quality Control
      Search
    • 63. Lots of governance resources…
      SharePoint Products and Technologies Governance Checklist Guidehttp://technet.microsoft.com/en-us/library/cc261826(office.12).aspx
      Covers everything from information architecture, infrastructure, communication management, testing, provisioning, training, taxonomy, executive sponsorship.
    • 64. Lots of governance resources…
      SharePoint Governance Plan by Joel Oleson and Mark Wagnerhttp://technet.microsoft.com/en-us/library/cc262943(office.12).aspx
    • 65. Lots of governance resources…
      Tools for SharePoint governance and manageability http://governance.codeplex.com/
      SharePoint Cross-Site Configurator
      SharePoint Site Recycle Bin
    • 66. Next up… Cost
      PEOPLEYou’ll be able to explain the different SP roles and responsibilities.
      You’ll be able to estimate how many people you need in your SP team.
      GOVERNANCE
      You’ll be able to explain why Governance is important.
      You’ll be able to identify what Governance will NOT do for you.
      You’ll be able to find more governance resources.
      COST
      You’ll be able to determine if chargebacks are right for you.
      You’ll be able to differentiate between different types of chargeback models.
      1
      2
      3
    • 67. 3
      Costs
      Chargebacks and how to recover costs
    • 68. Corporate Overhead - tax
      IT costs are incurred by a centralized department in an organization.
      All business units share the cost equally and pay tax for IT services.
      Simple accounting strategy for cost allocation.
    • 69. Chargebacks
      IT plays the role of internally sourced service provider. Measures usage / consumption.
      Costs are literally charged back to the business units on whose behalf they were incurred.
    • 70. Can chargebacks work for SP?
      Internal chargeback model can work if it does not cause internal systems to compete with each other.
      Chargebacks can influence adoption.
    • 71. $ / Storage
      • Departments pay a fixed fee based upon site quota.
      • 72. Pricing model is easy to implement and manage.
      • 73. Pricing may cause internal systems to compete with each other – network drives, SharePoint, Exchange… etc.
      • 74. Users may circumvent cost by creating multiple sites with smaller quotas. This will in turn cause unmanaged and unorganized information growth.
    • $ / sites
      • Departments pay a fixed fee for each site provisioned for their use.
      • 75. Forces users to think carefully about site hierarchies and information management. Promoted structured growth.
      • 76. Users might spend too much time consolidating sites to save money.
      • 77. Manageability issue.
      • 78. May drive adoption down.
    • $ / Users
      • Departments pay a fixed fee for each contributor, owner, site administrator per site collection.
      • 79. Since users pay upfront for unlimited usage, they have a higher incentive to use SharePoint to maximize their ROI.
      • 80. May drive up adoption.
      • 81. Pricing model is hard to implement on existing installation.
    • Which chargeback model is right for you ?
      “It depends” on –
      SP Maturity
      Barriers of Entry
    • 82. Rate your organizations SP maturity
      Early stage
      document storage, some LAN drive replacement.
      Lists, task management
      Mid stage
      Information does not live elsewhere, System of Record
      Business specific lite apps
      Mature
      Lots of users, many contributors
      Reports and KPIs
      Workflows, Processes designed around SharePoint offerings
      Large scale enterprise solutions
    • 83. Are there any barriers of entry ?
      Lock-in
      IT is the sole server provider
      Competitive
      IT competes with external vendors
    • 84. The chargeback matrix
    • 85. The chargeback matrix
    • 86. Aspects of an Operating model…
      PEOPLEYou’ll be able to explain the different SP roles and responsibilities.
      You’ll be able to estimate how many people you need in your SP team.
      GOVERNANCE
      You’ll be able to explain why Governance is important.
      You’ll be able to identify what Governance will NOT do for you.
      You’ll be able to find more governance resources.
      COST
      You’ll be able to determine if chargebacks are right for you.
      You’ll be able to differentiate between different types of chargeback models.
      1
      2
      3
    • 87. Thank You
      Mayank Malik
      Blog: http://latenightsp.wordpress.com
      Email: malik.mayank@live.com