Post on 25-Dec-2014
description
transcript
Assess Your SharePoint Maturity with
The SharePoint Maturity Model
Presented at SharePoint Saturday The Conference
13 August 2011
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 1
Agenda
• Logistics
• What’s in it for you?
• About Me
• About My Company
• Planning for SharePoint
• About the SharePoint Maturity Model
• Overview of the SharePoint Maturity Model
• Detail & case studies
• Future Plans
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 2
Logistics
• In Session – Questions welcome!
– Open wireless access is available at SSID: SPSTC2011
– If you’re tweeting / live blogging, please include: • #SPMaturity
• #spstcdc
• @sadalit
• Post-Session – Please fill out your evaluation
©2011 Sadalit Van Buren 3 8/13/2011 - #spmaturity @sadalit #spstcdc
What’s In It For You?
• The Maturity Model can help you measure what you have, develop your strategic roadmap, and ultimately lead to: – Greater business process efficiency – A more trustworthy SP environment – Happier, more empowered users – More time for YOU
• to innovate, rather than putting out fires or answering the same question over and over.
• You can get a quantitative sense of your progress by re-evaluating each year.
• You are helping to build a data model that will help answer larger questions about where organizations are in their SP maturity by industry, number of years of use, etc.
4 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
About Me
Senior Software Engineer, BlueMetal Architects
• Project Manager and Business Analyst focusing on SharePoint
• Working with SharePoint since beta 2003 version
• 50 SharePoint implementations
• Microsoft Certified IT Pro
5 8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren
About My Company
• Founded by ex-Microsoft product and technology executives
• Helping clients architect, build, and deploy software solutions in 4 areas: – Application Modernization – Cloud Platforms – Information Management – User Experience
• Deep and broad expertise in Microsoft and related technologies.
• 20 employees with over 125 years of previous experience working directly for Microsoft.
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 6
Stops on the Road to SharePoint Maturity
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 7
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 8
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 9
FAIRY DUST
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 10
GREAT DEPRESSION
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 11
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 12
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 13
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 14
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 15
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 16
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 17
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 18
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 19
About the SharePoint Maturity Model
• Developed in Fall 2010 for the purpose of bringing a
holistic view to a SharePoint implementation, and bringing standardization to the conversation around functionality, best practices, and improvement.
• Based on CMM and MS SP Pie • Starts at 100 rather than 0 • A framework rather than a formula • Typical rather than recommended • Does NOT currently cover:
– Public-facing websites – Compliance and regulatory issues – Visual design and branding – Cloud/online versions of SP
• Version 1 published 5 November 2010.
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 20
Area Description
Publication
Presentation of content in SharePoint for consumption by a varied audience of authenticated users. Areas of focus include navigation, presentation of content (static vs. personalized), content organization and storage, customizations to the template, and approvals and workflow.
Collaboration
Multiple individuals working jointly within SharePoint. Areas of focus include provisioning & de-provisioning, templates, organization (finding a site), archiving, using SP’s capabilities (i.e. versioning & doc mgmt, task mgmt, calendar mgmt, discussion thread, surveys, workflow).
Business Process
Linked business activities with a defined trigger and outcome, standardized by SharePoint and/or custom automated workflow processes. Areas of focus include data (unstructured/structured), workflow, user security / roles, reporting and analytics, tracking / auditing, process modeling and simulation, and process optimization.
Search The ability to query indexed content and return results that are ranked in order of relevance to the search query. Areas of focus include scopes, display of results, optimization, integration and connectors, and performance.
Competency Definitions - Core
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 23
Area Description
People & Communities
The human capital of the organization as represented in SharePoint by profiles, MySites, and community spaces (the virtual spaces that support particular areas of interest that may span or fall outside the organizational structure).
Composites & Applications
Custom solutions specific to the needs of the business (traditionally served by paper forms, Excel spreadsheets and/or Access databases) which may be accomplished by multiple technologies working together.
Integration
Line of business data and/or content from a separate CMS integrated with the system, allowing users to self-serve in a controlled yet flexible manner. Maturity proceeds through integration with single system, multiple systems, Data Warehouse, and external (partner/supplier or industry) data.
Insight The means of viewing business data in the system. Maturity proceeds through aggregation of views, drill-down and charting, actionability, and analytics and trending.
Competency Definitions - Advanced
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 24
Area Description
Infrastructure & Administration
The hardware and processes that support the system. Areas of focus include farm planning, server configuration, storage, backup/restore, monitoring, and updates.
Staffing & Training The human resources that support the system and the level of training with which they are provided.
Customizations
Custom development and/or third-party products that extend the out-of-box functionality of the system. Areas of focus include development environment, management of source code, method of build and deployment, testing, and development tier.
Competency Definitions - Readiness
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 25
SharePoint Level
Description
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. Governance is defined but may not be widely understood/followed.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area, or is limited to a single area.
100 Initial
The starting point of SharePoint use.
Mat
ura
tio
n
Maturity Level Definitions
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 26
The SharePoint Maturity Model – 1 – Core Concepts
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 28
Level Publication Collaboration Business Process Search
500 Optimizing
Content is personalized to the user. Content is shared across multiple functions and systems without duplication. Feedback mechanism is in place for pages and taxonomy. Automated tagging may be present.
Collaboration occurs outside the firewall – i.e. with external contributors. Automated processes exist for de-provisioning and archiving sites.
Power users can edit existing workflows to adapt them to changing business needs on the fly. Users leverage data from BPM to optimize process, simulate on real data, clear bottlenecks, balance work across workloads. Users have visibility into the process and can provide feedback to process improvements. Business processes extend to external users.
Users understand relationship of tagging to search results. Process exists to create content w/no results. Automated tagging may be used. High volumes can be handled.
400 Predictable
Content is monitored, maintained, targeted to specific groups. Usage is analyzed. Digital assets are managed appropriately. If more than one doc mgmt system is present, governance is defined. Mobile access considered.
Collaboration tools are used across the entire organization. Email is captured & leveraged. The system supports promotion of content from WIP to final. Mobile access considered.
Workflow is a component of SP-based composite applications with connectivity to LOB systems. Users have access to process analytics and audit trails. Collaboration happens in the context of a work item as part of a dynamic, nonlinear business process (the “case”).
Content types and custom properties are leveraged in Advanced Search and/or refiners. Results are customized to specific needs, may be actionable.
300 Defined
Site Columns/ Managed Metadata standardize the taxonomy. Custom content Types are created. Custom page layouts & site templates are configured. Approval process is implemented. Incoming email activated for some lists/libs. Site Map is present. Some content targeted to groups.
Collaboration efforts extend sporadically to discussion threads, wikis, blogs, and doc libs with versioning. Site templates are developed for specific needs. Incoming email activated for some lists/libs.
Process is considered as a whole, rather than as automating functional tasks. Transition from procedural document workflow to orchestration of dynamic business process. SharePoint is becoming the BP platform, w/the introduction of 3rd party BPM tool to support more complex business rules.
Search results are analyzed. Best bets and metadata properties are leveraged to aid the search experience.
200 Managed
Custom metadata is applied to content. Templates standardized across sites. Lists used rather than static HTML. Multiple document mgmt systems may be present w/out governance around purpose.
Mechanism is in place for new site requests. Collaboration efforts are collected in document libraries (links emailed rather than documents).
Business processes are designed; some custom, departmental “no-code” workflows (SP Designer, Visio, or third-party tool) may be implemented to handle simple business rules (decision-based routing). .
Custom scopes employed to aid the search experience. More complex iFilters may be applied. Content may be federated. Search Center created.
100 Initial
Navigation & taxonomy not formally considered. Little to no checks on content. Folder structure re-created from shared drives. Content that could be in lists is posted in Content Editor WP. Out of box site templates / layouts are used.
Out of box collaboration sites set up as needed without structure or organization. No formal process exists for requesting a new site.
Business process is loosely defined. Out of the box SharePoint workflows (approval, collect feedback) leveraged sporadically. A doclib or list provides a central base of operations. Any workflow is document- vs. application-centric.
Out of box functionality for query, results, and scopes; PDF iFilter installed; some additional content sources may be indexed.
Mat
ura
tio
n
Maturation also occurs along this vector
CRAWL
WALK
RUN
The SharePoint Maturity Model – 2 – Advanced Concepts
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 29
Mat
ura
tio
n
Level People and
Communities Composites and
Applications Integration Insight
500 Optimizing
Users can edit certain profile data that writes back to AD or HRIS. MySites template is customized. Communities extend to external participants.
Forms connect with LOB data. New capabilities & requirements are surfaced & integrated into downstream capabilities.
External data (partner/supplier or industry) is integrated with SP.
Analytics and trending are employed.
400 Predictable
Profile fields may integrate with LOB data. MySites are centralized (only one instance per user). Communities flourish under governance.
InfoPath forms improve the user experience. Mobile functionality is supported.
Most of the systems that are desired to be integrated, are integrated. A data warehouse may be integrated with SP.
Items are actionable.
300 Defined
Custom profile fields reflect company culture; photos are updated from central source. MySites rolled out to all users, supported, trained. Community spaces connect a particular set of users.
Most critical business forms are online; some involve automated workflows.
Multiple systems are integrated with SP.
Reports allow drill-down and charting.
200 Managed
MySites rolled out to pilot groups or users. Out-of-box profiiles implemented. Community spaces may be piloted.
Increasing use of SP lists to replace Excel spreadsheets and paper forms. Applications are opened up to a larger group of users.
A single system is integrated with SP (Line-of-business, document management, etc.).
Reports are aggregated through customization.
100 Initial
Basic profile data imported from AD or other source. MySites host not created.
Some paper forms converted to SP list forms. Many Excel spreadsheets, Access databases, paper forms still stored in / linked to from SharePoint.
Links to enterprise systems posted on SP site. Printed or exported business data is stored in doc libs. AD integrated with SP profiles.
Existing reports are used; data is brought together manually.
Maturation also occurs along this vector
The SharePoint Maturity Model – 3 – Readiness Concepts
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 30
Mat
ura
tio
n
Level Infrastructure and
Administration Staffing & Training Customizations
500 Optimizing
System health & error logs monitored. Processes for archiving & de-provisioning are in place.
Top-down support in place; dedicated IT business analyst, server admin, helpdesk, training staff; empowered user community. Multiple training offerings exist.
Deployment is fully automated via features . Source code is managed centrally as IP, re-usable and shareable. Content owners understand the importance of QA testing.
400 Predictable
Backup/restore has been tested. Dev and QA environments are present. Administration may be improved via third-party tools. BLOB integration may be present. Performance considered.
IT has more than one resource knowledgeable on the system. Requests for new functionality are tracked and prioritized. An end-user training plan is in place.
Deployment is fully automated – solution package and scripts. Total Cost of Ownership is considered.
300 Defined
Number of servers is appropriate to demands and scalable for future growth. Dev environment is present. Service Packs tested in QA and installed in a timely fashion.
SP evangelized around the organization by individual or small group. Content owners from some functional areas are trained and using the system. One IT resource knowledgeable on the system.
Mixed automated \ manual deployment process - some artifacts deployed via scripts, others by following list of manual steps. Source control is centralized.
200 Managed
Multiple server installlation or single-server is backed up on a regular basis.
SP evangelized to a subset of depts or functional areas by an individual; work mainly done by individual or small group. Training is informal, ad-hoc.
Changes are deployed from one environment to another using backup/restore. Source control is simple file storage.
100 Initial
Single-server installation, sometimes rogue . No plan for availability / disaster recovery.
One pioneer or small group pilots the product.
No development, or development is done in Production. No QA / development environments. No source control.
Maturation also occurs along this vector
Self Evaluation Matrix
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 31
Date of Assessment
Years the organization has used SharePoint
Current SP Version (year + standard or enterprise if known)
# of users organization-wide
# of IT staff supporting SharePoint (combine part-timers & include vendors if they are a regular part of your team)
Organization’s Industry
Publication Collaboration Business Process
Search People & Communities
Composites & Applications
Integration Insight Infrastructure & Admin.
Staffing & Training
Customizations
500 Optimizing
400 Predictable
300 Defined
200 Managed
100 Initial
100
199 200
299 300
399 400
499 500
599
Self Evaluation Matrix – Filled-in Example
Publication Collaboration Business Process
Search People & Communities
Composites & Applications
Integration Insight Infrastructure & Admin.
Staffing & Training
Customizations
500 Optimizing
400 Predictable
300 Defined
200 Managed
100 Initial
32
Date of Assessment 1/29/11
Years the organization has used SharePoint 7
Current SP Version (year + standard or enterprise if known) SP 2010 Enterprise
# of users organization-wide 50
# of IT staff supporting SharePoint (combine part-timers & include vendors if they are a regular part of your team)
2.5
Organization’s Industry Professional Services
100
199 200
299 300
399 400
499 500
599
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Data Model Examples
33 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Excel Template Available
34
Go to http://www.sharepointmaturity.com to get your own!
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren
Publication
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
Content is personalized to the user. Content is shared across multiple functions and systems without duplication. Feedback mechanism is in place for pages and taxonomy. Automated tagging may be present.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
Content is monitored, maintained, targeted to specific groups. Usage is analyzed. Digital assets are managed appropriately. If more than one doc mgmt system is present, governance is defined. Mobile access considered.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
Site Columns/ Managed Metadata standardize the taxonomy. Custom content Types are created. Custom page layouts & site templates are configured. Approval process is implemented. Incoming email activated for some lists/libs. Site Map is present. Some content targeted to groups.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
Custom metadata is applied to content. Templates standardized across sites. Lists used rather than static HTML. Multiple document mgmt systems may be present w/out governance around purpose.
100 Initial
The starting point of SharePoint use.
Navigation & taxonomy not formally considered. Little to no checks on content. Folder structure re-created from shared drives. Content that could be in lists is posted in Content Editor WP. Out of box site templates / layouts are used.
Presentation of content in SharePoint for consumption by a varied audience of authenticated users. Areas of focus include navigation, presentation of content (static vs. personalized), content organization and storage, customizations to the template, and approvals and workflow.
35 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Dynamic and personalized
Static and unorganized
Standardized and Targeted
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 38
236 243
272 266
300 278
350
100
150
200
250
300
350
400
450
500
550
1 2 3 4 6 7 9
Mat
uri
ty L
eve
l
Years of SharePoint Use
Publication
Publication – 100-level example
39 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Source: S. Van Buren
Publication – 500-level example
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 41
Source: Microsoft
Collaboration
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
Collaboration occurs outside the firewall – i.e. with external contributors. Automated processes exist for de-provisioning and archiving sites.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
Collaboration tools are used across the entire organization. Email is captured & leveraged. Work is promoted from WIP to Final which is leverageable. Mobile access considered.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
Collaboration efforts extend sporadically to discussion threads, wikis, blogs, and doc libs with versioning. Site templates are developed for specific needs.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
Mechanism is in place for new site requests. Collaboration efforts are collected in document libraries (links emailed rather than documents)
100 Initial
The starting point of SharePoint use. Out of box collaboration sites set up as needed without structure or organization. No formal process exists for requesting a new site.
Multiple individuals working jointly within SharePoint. Areas of focus include provisioning & de-provisioning, templates, organization (finding a site), archiving, using SP’s capabilities (i.e. versioning & doc mgmt, task mgmt, calendar mgmt, discussion thread, surveys, workflow).
43 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Outside the firewall
Team-centric, mostly doc storage
Cross-enterprise and fuller functionality
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 45
100
150
200
250
300
350
400
450
500
550
1 2 3 4 6 7 9
Mat
uri
ty L
eve
l
Years of SharePoint Use
Collaboration
Collaboration – 100-level example
46 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Source: S. Van Buren:
Collaboration– 400-level example
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 47
Source: Nielsen Norman Intranet Design Annual 2010
Business Process
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
Power users can edit existing workflows to adapt them to changing business needs on the fly. Users leverage data from BPM to optimize process, simulate on real data, clear bottlenecks, balance work across workloads. Users have visibility into the process and can provide feedback to process improvements. Business processes extend to external users.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
Workflow is a component of SP-based composite applications with connectivity to LOB systems. Users have access to process analytics and audit trails. Collaboration happens in the context of a work item as part of a dynamic, nonlinear business process (the “case”).
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
Process is considered as a whole, rather than as automating functional tasks. Transition from procedural document workflow to orchestration of dynamic business process. SharePoint is becoming the BP platform, w/the introduction of 3rd party BPM tool to support more complex business rules.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
Business processes are designed; some custom, departmental “no-code” workflows (SP Designer, Visio, or third-party tool) may be implemented to handle simple business rules (decision-based routing). .
100 Initial
The starting point of SharePoint use.
Business process is loosely defined. Out of the box SharePoint workflows (approval, collect feedback) leveraged sporadically. A doclib or list provides a central base of operations. Any workflow is document- vs. application-centric.
Linked business activities with a defined trigger and outcome, standardized by SharePoint and/or custom automated workflow processes. Areas of focus include data (unstructured/structured), workflow, user security / roles, reporting and analytics, tracking / auditing, process modeling and simulation, and process optimization.
48
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Analytics drive continuous improvements
There are workflows in SharePoint?
Applications consolidated, processes automated
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 50
100
150
200
250
300
350
400
450
500
550
1 2 3 4 6 7 9
Mat
uri
ty L
evel
Years of SharePoint Use
Business Process
Business Process – 100-level example
51 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Source: S. Van Buren
Business Process – 500-level example
53
Source: Global360
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Search
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
Users understand relationship of tagging to search results. Automated tagging may be used. High volumes can be handled.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
Content types and custom properties are leveraged in Advanced Search and/or refiners. Results customized to specific needs, may be actionable.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
Search results are analyzed. Best bets and metadata properties are leveraged to aid the search experience.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
Custom scopes and iFilters employed to aid the search experience. Content may be federated. Search Center created.
100 Initial
The starting point of SharePoint use. Out of box functionality for query, results, and scopes; some additional content sources may be indexed.
The ability to query indexed content and return results that are ranked in order of relevance to the search query. Areas of focus include scopes, display of results, optimization, integration and connectors, and performance.
54 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Content finds me based on the preferences I set
I use keyword search and don’t expect much from results.
I can filter queries and results
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 56
100
150
200
250
300
350
400
450
500
550
1 2 3 4 6 7 9
Mat
uri
ty L
evel
Years of SharePoint Use
Search
Search – 100-level example
57 8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren
Source: S. Van Buren
Search – 400-level example (query)
Source: Nielsen Norman Intranet Design Annual 2010
58 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Search – 400-level example (results)
Source: S. Van Buren
59 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
People and Communities
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. MySites may be allowed for external users.
Users can edit certain profile data that writes back to AD or HRIS. MySites template is customized. Communities extend to external participants.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
Profile fields may integrate with LOB data. MySites are centralized (only one instance). Communities flourish under governance.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
Custom profile fields reflect company culture; photos are updated from central source. MySites rolled out to all users, supported, trained. Community spaces connect a particular set of users.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
MySites rolled out to pilot groups or users. Out-of-box profiiles implemented. Community spaces may be piloted.
100 Initial
The starting point of SharePoint use. Basic profile data imported from AD or other source. MySites host not created.
The human capital of the organization as represented in SharePoint by profiles, MySites, and community spaces (the virtual spaces that support particular areas of interest that may span or fall outside the organizational structure).
60 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Unified Community Experience
Individual Needs
Availability of tools enterprise-wide
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 61
280
148
312
200
252
350
100 150 200 250 300 350 400 450 500 550
1
3
4
6
7
9
Average Maturity Level
Ye
ars
of
Shar
eP
oin
t U
se
People & Communities
People and Communities – 100-level example
62
Source: S. Van Buren
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
People and Communities – 500-level example
Source: Nielsen Norman Intranet Design Annual 2010
63 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Composites and Applications
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
Forms connect with LOB data. New capabilities & requirements are surfaced & integrated into downstream capabilities.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
InfoPath forms improve the user experience. Mobile functionality is supported.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
Most critical business forms are online; some involve automated workflows.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
Increasing use of SP lists to replace Excel spreadsheets and paper forms. Applications are opened up to a larger group of users.
100 Initial
The starting point of SharePoint use. Some paper forms converted to SP list forms. Many Excel spreadsheets, Access databases, paper forms still stored in / linked to from SharePoint.
Custom solutions specific to the needs of the business (traditionally served by paper forms, Excel spreadsheets and/or Access databases) which may be accomplished by multiple technologies working together.
64 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Seamless integration with LOB data
Replacement of a few key apps
Departmental Adoption
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 65
262
258
292
363
268
300
100 150 200 250 300 350 400 450 500 550
1
3
4
6
7
9
Average Maturity Level
Ye
ars
of
Shar
eP
oin
t U
se
Composites & Applications
Composites & Applications – 100-level example
Source: S. Van Buren
66 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Composites & Applications – 400-level example
Source: Nielsen Norman Intranet Annual 2010
67 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Integration
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
External data (partner/supplier or industry) is integrated with SP.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
Most of the systems that are desired to be integrated, are integrated. A data warehouse may be integrated with SP.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
Multiple systems are integrated.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
A single system is integrated with SP.
100 Initial
The starting point of SharePoint use. Links to enterprise systems posted on SP site. Printed or exported business data is stored in doc libs.
Line of business data and/or content from a separate CMS integrated with the system, allowing users to self-serve in a controlled yet flexible manner. Maturity proceeds through integration with single system, multiple systems, Data Warehouse, and external (partner/supplier or industry) data.
68 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Most systems integrated
Links to other systems
Some systems integrated
Integration – 100-level example
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 69
Source: S. Van Buren
Integration – 400-level example
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 70
Source: Nielsen Norman Intranet Annual 2010
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 71
212
221
247
338
255
300
100 150 200 250 300 350 400 450 500 550
1
3
4
6
7
9
Average Maturity Level
Ye
ars
of
Shar
eP
oin
t U
se
Integration
Insight
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
Analytics and trending are employed.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
Items are actionable.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
Reports allow drill-down and charting.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
Reports are aggregated through customization.
100 Initial
The starting point of SharePoint use. Existing reports are used; data is brought together manually.
The means of viewing business data in the system. Maturity proceeds through aggregation of views, drill-down and charting, actionability, and analytics and trending.
72 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
I can see what’s going to happen.
I can see what happened.
I can see what’s happening
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 73
212
191
183
338
247
300
100 150 200 250 300 350 400 450 500 550
1
3
4
6
7
9
Average Maturity Level
Ye
ars
of
Shar
eP
oin
t U
se Insight
Insight – 100-level example
74 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Source: S. Van Buren
Insight – 500-level example
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 75
Source:
Infrastructure
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
System health & error logs monitored. Processes for archiving & de-provisioning are in place. Disaster Recovery plan is in place.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. Users trust the system.
Backup/restore has been tested. Dev and QA environments are present. Administration may be improved via third-party tools. BLOB integration may be present. Performance considered.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. Remote access is available.
Number of servers is appropriate to demands and scalable for future growth. Dev environment is present. Service Packs tested in QA and installed in a timely fashion.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
Multiple server installlation or single-server is backed up on a regular basis.
100 Initial
The starting point of SharePoint use. Single-server installation, sometimes rogue . No plan for availability / disaster recovery.
The hardware and processes that support the system. Areas of focus include farm planning, server configuration, storage, backup/restore, monitoring, and updates.
76 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 77
342
244
408
338
362
450
100 150 200 250 300 350 400 450 500 550
1
3
4
6
7
9
Average Maturity Level
Ye
ars
of
Shar
eP
oin
t U
se
Infrastructure
Staffing and Training
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
Top-down support in place; dedicated IT business analyst, server admin, helpdesk, training staff; empowered user community. Multiple training offerings exist.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
IT has more than one resource knowledgeable on the system. Requests for new functionality are tracked and prioritized. An end-user training plan is in place.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
SP evangelized around the organization by individual or small group. Content owners from some functional areas are trained and using the system. One IT resource knowledgeable on the system.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
SP evangelized to a subset of depts or functional areas by an individual; work mainly done by individual or small group. Training is informal, ad-hoc.
100 Initial
The starting point of SharePoint use. One pioneer or small group pilots the product.
The human resources that support the system and the level of training with which they are provided.
78 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 79
342
244
408
338
362
450
100 150 200 250 300 350 400 450 500 550
1
3
4
6
7
9
Average Maturity Level
Ye
ars
of
Shar
eP
oin
t U
se
Staffing & Training
Customizations
Level Maturity Level Definition Competency
500 Optimizing
The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics.
Deployment is fully automated via features . Source code is managed centrally as IP, re-usable and shareable.
400 Predictable
The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed.
Deployment is fully automated – solution package and scripts. Total Cost of Ownership is considered.
300 Defined
The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization.
Mixed automated \ manual deployment process - some artifacts deployed via scripts, others by following list of manual steps. Source control is centralized.
200 Managed
The particular area is managed by a central group (often IT), but the focus and definition varies by functional area.
Changes are deployed from one environment to another using backup/restore. Source control is simple file storage.
100 Initial
The starting point of SharePoint use. No development, or development is done in Production. No QA / development environments. No source control.
Custom development and/or third-party products that extend the out-of-box functionality of the system. Areas of focus include development environment, management of source code, method of build and deployment, and development tier.
80 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Maturity per Years of Use
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 81
255
289
200
288
373
350
100 150 200 250 300 350 400 450 500 550
1
3
4
6
7
9
Average Maturity Level
Ye
ars
of
Shar
eP
oin
t U
se
Customizations
8/13/2011 - #spmaturity @sadalit #spstcdc
©2011 Sadalit Van Buren 82
Future Plans and Improvements
• Article series for SP Magazine
• Centralized system for receiving data
• Mapping to vendors – services and products
• Complete mapping to resourcing (with Veronique Palmer)
• Mapping to SP versions – Standard/Enterprise
– Cloud
• Operational steps to maturity in the competencies – (Torben Ellert has already done this for Search –
http://www.surfray.com/resources/tech-blog/459-boosting-your-sharepoint-search-maturity-level.html)
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 83
Call to Action
• Fill out the session evaluation (details on next slide)
• Fill out the SMM self-assessment!
• Send me your data to help build a data model for everyone (your name & company name will remain anonymous.)
• Contact me (contact info on next slide)
– With Questions
– With Feedback
– If you’d like help assessing your SP implementation and learning more about how to get to greater SharePoint Maturity.
85 8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren
Session Evaluation Please complete and turn in your Session Evaluation Form so we can improve future events.
Survey can be filled out at:
http://app.fluidsurveys.com/s/spstc2011-Sat-S2C-105
Presenter: Sadie Van Buren
Session Name: Assess Your SharePoint Maturity With The SharePoint Maturity Model
Session No.: S2C-105
Thank You!
Sadie Van Buren
• Twitter: @sadalit
• LinkedIn: http://www.linkedin.com/in/sadalit
SharePoint Maturity
• Twitter: @SPMaturity
• http://www.sharepointmaturity.com
– Tools, templates, and resources
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren 88