sharepoint governance: from chaos to success in 10 steps
DESCRIPTION
Key SharePoint and IT Governance considerations in a SharePoint Deployment. These 10 steps will keep you on the right path.TRANSCRIPT
SharePoint Governance: From Chaos to Success in Ten Steps
Joel Oleson – Sr. Consultant, Evangelist, BloggerSr. Product ManagerQuest Softwarewww.sharepointjoel.comwww.twitter.com/joeloleson
22
Who is this guy?
1) Confront Reality2) Create a Governance Plan3) Get an Exec Sponsor4) Create the Dream Team5) Build Services not Stuff6) Define Clear Policies and Standards7) Invest in Scalable Information Architecture8) Don’t forget Change Management9) Adoption is What Counts10)Keep it Simple Stupid.
10 Steps To Ensure Success
44
77
88
Through 2010, less than 35% of sites turning on Windows
SharePoint Services will put effective governance techniques in place.
Gartner
Governance uses people, process, technology, and policies to define a service, resolve ambiguity, and mitigate conflict within an organization
SharePoint Governance 10
Source: The Burton Group
1111
SharePoint Governance Plan
PeopleRoles and responsibilities
ProcessHow to accomplish common tasks such as creating a new site or requesting new business requirements
TechnologyLeveraging features and tools to enforce policies through technology
PolicyCollection of principles - What site owners, designers, developers should/shouldn’t do
1212
Clear Vision, Mission and Goals
1313
1414
Exec Sponsor with $$$$$$
Get me SharePoint or You’re FIRED!
Get me SharePoint or You’re FIRED!
1515
Data Governance Roles And ResponsibilitiesSeptember 2007 “Data Governance: What Works And What Doesn’t”
1616
1717
SharePoint is Plastic. What is your Creation?
1818 Cleverworkarounds.com
1919
Two Types of Service Models
Out of the box (Standard)
Custom (D
edicated)
2020
Containment Hierarchy
2121
Joel's Cheat Sheet for Hosting
Commodity Hosting Examples
Adhoc Structured
Short term Long term
Collaboration ServiceCollaboration ServiceOfferingOffering
2323
SharePoint Shared Services PlatformWell Managed, High Availability, DR
Team Sites My SitesCorporate Portal App 1 App 2
2424
SharePoint Governance Model
Permanent Central PortalEnterprise SearchEnterprise Browse
CorporateBusiness TaxonomyWith DivisionalStakeholders
PerUser
Ad Hoc SelfServicew/ Life CycleManagement
Permanent Division PortalsBusiness Process Division News, ScorecardsGroup Reporting
Semi StructuredGroup, Team, ProjectSites and Workspaces
Blogs, bios, Social
CentralPortal
2525
Multi Deployment/Global Model
Incremental Indexingover the WAN
(Federated Search)
2626
2828
SharePoint Operational Roles
Infrastructure Support
SharePoint Site Collection
Administrator
Content Administrator SharePoint
Developer(s)
BusinessIntelligence
BusinessForms
SearchContent
Management
Collaboration
PortalPlatformServices
2929
3030
3232
Defining Policies
Should I allow SharePoint Designer?What should I do with online web parts?Dev & Third party solutions?Solution Deployments!!! (.wsp)
Adhoc Structured
Self
Serv
ice
Sm
alle
r Q
uota
Q
uick
er E
xpira
tion
O
OB
IT P
rovi
sion
ed
La
rger
Quo
ta
P
erm
anen
t
Su
ppor
ted
Dev
env
.
$
$$ C
harg
e Ba
ck
3333
3434
3535
3636
Portal Information Arch exampleBuild initial site architecture and delegate
HomeHome
PayrollPayroll
SupportSupportT & E T & E
R & DR & D TrainingTraining
ExecutiveExecutive SalesSalesFinanceFinance ProductionProduction ITIT Customer Support
Customer Support
BODBOD
Site Contributors = Board of DirectorsSite Designers = SharePoint DesignersSite Managers = SharePoint Administrators
Site Contributors = Board of DirectorsSite Designers = SharePoint DesignersSite Managers = SharePoint Administrators
Site Visitors = EveryoneSite Contributors = EveryoneSite Designers = SharePoint DesignersSite Managers = SharePoint Administrators
Site Visitors = EveryoneSite Contributors = EveryoneSite Designers = SharePoint DesignersSite Managers = SharePoint Administrators
Site Visitors = Production TeamSite Contributors = Research and Development TeamSite Designers = SharePoint DesignersSite Managers = SharePoint Administrators
Site Visitors = Production TeamSite Contributors = Research and Development TeamSite Designers = SharePoint DesignersSite Managers = SharePoint Administrators
Site Visitors = Registered CustomersSite Contributors = Customer Support TeamSite Designers = SharePoint DesignersSite Managers = SharePoint Administrators
Site Visitors = Registered CustomersSite Contributors = Customer Support TeamSite Designers = SharePoint DesignersSite Managers = SharePoint Administrators
Source: The Burton Group
3737
3838
3939
Process Models for Dev Life Cycle
Release ManagementConfiguration ManagementOperations Monitoring, Security & Patch ManagementCommunications & Service ManagementCode Propagation Testing & Deployment
Microsoft Operations Framework 4.0
http://go.microsoft.com/fwlink/?LinkId=116390
4141
4242
4343
4444
K.I.S.S.
Do you really need that list def, site def, or wiz bang widget?Don’t start with BDC and Excel Services requirements if you’re trying to deploy a simple portal or search solution…Start with Search, it’s an easy win.Watch for Scope Creep it is very easy in SharePoint.
Keep It Simple Stupid.
Cutting corners – “My Devs are My Admins”The SharePoint project is no longer SharePoint (it’s so custom)“Production is test and dev, and where I introduce my service packs”SharePoint is a simple install... (c’mon it’s a Microsoft app... No one will even notice it.)“Let’s just get it out there, then we’ll figure out this “governance” and “operations” stuff...”
Key takeaways today...
4848
Resources and PlugsJoel’s Blog – http://www.sharepointjoel.com SharePoint Governance Resources
http://technet.microsoft.com/en-nz/office/sharepointserver/default(en-us).aspx
CodePlex Governance Toolshttp://www.codeplex.com/governance
Join a SharePoint User Group
SharePoint Deployment Essentials & Governance Checklist
5050
Quest SharePoint Site Administrator 3.5With Security ExplorerNew Auditing Capabilities
More at http://www.quest.com/sharepoint
5151
Enjoy the Saturday Party...
Questions?
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after
the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.