SharePoint 2010 Pragmatic implementation and use at a corporate level Carol Van der Donck.
-
Upload
melinda-carpenter -
Category
Documents
-
view
214 -
download
1
Transcript of SharePoint 2010 Pragmatic implementation and use at a corporate level Carol Van der Donck.
SharePoint 2010Pragmatic implementation and use at a
corporate level
Carol Van der Donck
Agenda
• What is SP2010• Some facts• SharePoint Governance• Conclusion
Agenda
• What is SP2010• Some facts• SharePoint Governance• Conclusion
SharePoint 2010 OverviewSharePoint Server 2010
Ribbon UISharePoint WorkspaceSharePoint MobileOffice ClientOffice Web App IntegrationStandards Support
Tagging, Tag Cloud, RatingsSocial BookmarkingBlogs and WikisMy SitesActivity FeedsProfiles and ExpertiseOrg Browser
Enterprise Content TypesMetadata and NavigationDocument SetsMulti-stage DispositionAudio and Video Content TypesRemote Blob StorageList Enhancements
Social RelevancePhonetic SearchNavigationFAST IntegrationEnhanced Pipeline
PerformancePoint ServicesExcel ServicesChart Web PartVisio ServicesWeb AnalyticsSQL Server IntegrationPowerPivot
Business Connectivity ServicesInfoPath Form ServicesExternal ListsWorkflowSharePoint DesignerVisual StudioAPI EnhancementsREST/ATOM/RSS
Communities
Search
Sites
Composites
ContentInsights
Agenda
• What is SP2010• Some facts• SharePoint Governance• Conclusion
SharePoint adoption
©AIIM 2010 www.aiim.org
How it is used
©AIIM 2010 www.aiim.org
Organizational challenges
©AIIM 2010 www.aiim.org
Agenda
• What is SP2010• Some facts• SharePoint Governance• Conclusion
SharePoint Governance
Governance is the set of policies, roles, responsibilities, and processes that guides, directs, and controls how an organization's business divisions and IT teams cooperate to achieve business goals.
Governance stakeholders
– Information architects or taxonomists
– Compliance officers– Influential information
workers– IT technical specialists– Development leaders
– Trainers– IT managers– Business division leaders– Financial stakeholders– Executive stakeholders
Form and use a governance group to create and maintain the policies and include the following roles:
SharePoint governance
Scope of sites
IT governance
•Quotas•Site lifecycle management and Self-service site provisioning•Asset classification•Data protection (backup and recovery)•Branding and navigation•Security, infrastructure and software updates•…
Multiple servicesBasic service Premium service
Description A server farm that hosts 10.000s of site collections. Short-lived sites with small team sites
A server farm hosting a highly critical site or highly customised site
Example Collaboration site to plan an event Enterprise intranet with back-end system integrations
Customisations Only user interface Extensive, tested and reviewed before deployment.Sandboxed.
Cost Minimal High
Self service provisioning Yes No
Backup frequency Twice weekly Daily
Backups maintained for 14d 60d
Problem resolution 2d 3h
Information management governance
• Wikis and blogs• Anonymous
comments• Anonymous access• External data• Terms
What to govern?• Pages• Lists• Documents• Records• Rich media
Information management governance
• Workflows• Approval• Content types• Information management policies• Managed metadata• Content Organizer• Blocked file types• …
Customisation governance
Lifecycle management• Separation of environments• Testing• Source code control and version tracking
Branding• Consistent branding with a corporate style • Store approved master pages in site galleries • Define which parts of the template can be changed by site owners • Allow room for sub-branding of individual team or project brands.
Customisation governance
•Features•Specific policies regarding each type of customization (code-based/ no-code)•Sandboxed solutions•Processes for analyzing customizations•Process for piloting and testing customizations•Guidelines for packaging and deploying customizations•Guidelines for updating customizations•Approved tools for development•Who is responsible for ongoing code support•Service level descriptions
Agenda
• What is SP2010• Some facts• SharePoint Governance• Conclusion
Outcome I
• General guidelines– Objective– Vision Statement– Roles and responsibilities– Principles
• Content Management– Posting content to exisiting pages/sites– Posting content to the Home Page– Posting content to personal pages– Social tags and ratings– Records retention– Auditing and review
Outcome II
• Design policies and standards– Creating new subsites– Page layout and organisation– Content types and metadata– Security– Branding
• Customisation policies and standards– Browser based updates– Updates based on SharePoint Designer– Sandboxed solutions– Centrally deployed / 3rd party solutions
Lessons learned
©AIIM 2010 www.aiim.org
Set up a proper IM vision for the enterprise before starting the real implementation
Don't customize if there's a way to avoid itGet a consultant and
implement policies. SP can become a black hole unless managed carefully
SP is rather easy to roll out and is attractive to end-users, so the risk is that everybody becomes an administrator and that governance is neglected
Define your problems so you know what you're solving for. Just changing to SP is not going to help unless you understand the business issues you're solving for
Sort out governance. Sort out training. Sort out an IA. Sort out a basic taxonomy
Focus on business requirements - don't let IT drive the implementation People achieve business
objectives, not software