Assess Your SharePoint Maturity with the Maturity Model

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

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


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.


About Me

• Project Manager and Business
Analyst focusing on SharePoint
• Working with SharePoint since
beta 2003 version
• 50 SharePoint
implementations
• Microsoft Certified IT Pro

Senior Software Engineer,
BlueMetal Architects
8/13/2011 - #spmaturity @sadalit
©2011 Sadalit Van Buren 5
#spstcdc

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.


Stops on the Road
to SharePoint Maturity


#spstcdc

FAIRY DUST

#spstcdc

GREAT
DEPRESSION
#spstcdc

#spstcdc

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.

Competency Definitions - Core

Area Description

Presentation of content in SharePoint for consumption by a varied audience of
authenticated users. Areas of focus include navigation, presentation of content
Publication (static vs. personalized), content organization and storage, customizations to the
template, and approvals and workflow.

Multiple individuals working jointly within SharePoint. Areas of focus include
provisioning & de-provisioning, templates, organization (finding a site),
Collaboration archiving, using SP’s capabilities (i.e. versioning & doc mgmt, task mgmt,
calendar mgmt, discussion thread, surveys, workflow).

Linked business activities with a defined trigger and outcome, standardized by
SharePoint and/or custom automated workflow processes. Areas of focus
Business Process include data (unstructured/structured), workflow, user security / roles, reporting
and analytics, tracking / auditing, process modeling and simulation, and process
optimization.

The ability to query indexed content and return results that are ranked in order
Search of relevance to the search query. Areas of focus include scopes, display of
results, optimization, integration and connectors, and performance.


Competency Definitions - Advanced

Area Description

The human capital of the organization as represented in SharePoint by profiles,
People &
MySites, and community spaces (the virtual spaces that support particular areas
Communities of interest that may span or fall outside the organizational structure).

Custom solutions specific to the needs of the business (traditionally served by
Composites &
paper forms, Excel spreadsheets and/or Access databases) which may be
Applications accomplished by multiple technologies working together.

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
Integration proceeds through integration with single system, multiple systems, Data
Warehouse, and external (partner/supplier or industry) data.

The means of viewing business data in the system. Maturity proceeds through
Insight aggregation of views, drill-down and charting, actionability, and analytics and
trending.


Competency Definitions - Readiness

Area Description

The hardware and processes that support the system. Areas of focus include
Infrastructure &
farm planning, server configuration, storage, backup/restore, monitoring, and
Administration updates.

The human resources that support the system and the level of training with
Staffing & Training which they are provided.

Custom development and/or third-party products that extend the out-of-box
functionality of the system. Areas of focus include development environment,
Customizations management of source code, method of build and deployment, testing, and
development tier.


Maturity Level Definitions

SharePoint
Description
Level

500 The particular area is functioning optimally and continuous improvement
Optimizing occurs based on defined and monitored metrics.

400 The particular area is centrally supported, standardized, and in use across
Predictable the entire organization. Governance is defined and followed.
Maturation

The way the particular area is leveraged is defined and/or standardized,
300 but not in use across the entire organization. Governance is defined but
Defined may not be widely understood/followed.

200 The particular area is managed by a central group (often IT), but the focus
Managed and definition varies by functional area, or is limited to a single area.

100 The starting point of SharePoint use.
Initial


The SharePoint Maturity Model – 1 alongCore Concepts
Maturation also occurs
– this vector
Level Publication Collaboration Business Process Search
Power users can edit existing
workflows to adapt them to changing
business needs on the fly. Users
Content is personalized to the user. Users understand relationship of
Collaboration occurs outside the leverage data from BPM to optimize
Content is shared across multiple functions tagging to search results.
500 and systems without duplication. Feedback
firewall – i.e. with external
contributors. Automated processes
process, simulate on real data, clear
bottlenecks, balance work across
Process exists to create content

RUN
mechanism is in place for pages and w/no results. Automated
exist for de-provisioning and workloads. Users have visibility into
Optimizing taxonomy. Automated tagging may be
present.
archiving sites. the process and can provide
tagging may be used. High
volumes can be handled.
feedback to process improvements.
Business processes extend to
external users.

Workflow is a component of SP-
Content is monitored, maintained, targeted Collaboration tools are used across based composite applications with Content types and custom
to specific groups. Usage is analyzed. the entire organization. Email is connectivity to LOB systems. Users properties are leveraged in
400 Digital assets are managed appropriately.
If more than one doc mgmt system is
captured & leveraged. The system
supports promotion of content from
have access to process analytics and
audit trails. Collaboration happens in
Advanced Search and/or
refiners. Results are
Predictable present, governance is defined. Mobile
access considered.
WIP to final. Mobile access
considered.
the context of a work item as part of
a dynamic, nonlinear business
customized to specific needs,
may be actionable.
process (the “case”).

WALK
Process is considered as a whole,
Maturation

Site Columns/ Managed Metadata Collaboration efforts extend rather than as automating functional
standardize the taxonomy. Custom content sporadically to discussion threads, tasks. Transition from procedural
Search results are analyzed.
300 Types are created. Custom page layouts &
site templates are configured. Approval
wikis, blogs, and doc libs with
versioning. Site templates are
document workflow to orchestration
of dynamic business process.
Best bets and metadata
properties are leveraged to aid
process is implemented. Incoming email developed for specific needs. SharePoint is becoming the BP
Defined activated for some lists/libs. Site Map is Incoming email activated for some platform, w/the introduction of 3rd
the search experience.
present. Some content targeted to groups. lists/libs. party BPM tool to support more
complex business rules.

Business processes are designed;
Custom metadata is applied to content. Mechanism is in place for new site some custom, departmental “no- Custom scopes employed to aid
200 Templates standardized across sites. Lists
used rather than static HTML. Multiple
requests. Collaboration efforts are
collected in document libraries
code” workflows (SP Designer, Visio,
or third-party tool) may be
the search experience. More
complex iFilters may be applied.
document mgmt systems may be present (links emailed rather than implemented to handle simple Content may be federated.
Managed

CRAWL
w/out governance around purpose. documents). business rules (decision-based Search Center created.
routing). .

Business process is loosely defined.
Navigation & taxonomy not formally
Out of the box SharePoint workflows Out of box functionality for
considered. Little to no checks on content. Out of box collaboration sites set up
100 Folder structure re-created from shared
drives. Content that could be in lists is
as needed without structure or
organization. No formal process
(approval, collect feedback)
leveraged sporadically. A doclib or list
query, results, and scopes; PDF
iFilter installed; some additional
provides a central base of operations. content sources may be
Initial posted in Content Editor WP. Out of box site
templates / layouts are used.
exists for requesting a new site.
Any workflow is document- vs. indexed.
application-centric.

The SharePoint Maturity Model – 2 – Advanced Concepts
Maturation also occurs along this vector

People and Composites and
Level Integration Insight
Communities Applications
Users can edit certain profile Forms connect with LOB
External data
data that writes back to AD or data. New capabilities &
500 HRIS. MySites template is requirements are surfaced
(partner/supplier or Analytics and trending are
industry) is integrated with employed.
Optimizing customized. Communities & integrated into
SP.
extend to external participants. downstream capabilities.

Profile fields may integrate with Most of the systems that are
LOB data. MySites are InfoPath forms improve the desired to be integrated,
400 centralized (only one instance user experience. Mobile are integrated. A data Items are actionable.
Predictable per user). Communities flourish functionality is supported. warehouse may be
under governance. integrated with SP.

Custom profile fields reflect
company culture; photos are
Maturation

updated from central source. Most critical business forms
300 MySites rolled out to all users, are online; some involve
Multiple systems are Reports allow drill-down and
integrated with SP. charting.
Defined supported, trained. Community automated workflows.
spaces connect a particular set
of users.

MySites rolled out to pilot Increasing use of SP lists to
A single system is integrated
groups or users. Out-of-box replace Excel spreadsheets
200 profiiles implemented. and paper forms.
with SP (Line-of-business, Reports are aggregated
document management, through customization.
Managed Community spaces may be Applications are opened up
etc.).
piloted. to a larger group of users.

Some paper forms
Links to enterprise systems
converted to SP list forms.
Basic profile data imported posted on SP site. Printed or Existing reports are used;
100 from AD or other source.
Many Excel spreadsheets,
exported business data is data is brought together
Access databases, paper
Initial MySites host not created. stored in doc libs. AD manually.
forms still stored in / linked
integrated with SP profiles.
to from SharePoint.


The SharePoint Maturity Model – 3 – Readiness Concepts
Maturation also occurs along this vector

Infrastructure and
Level Staffing & Training Customizations
Administration
Top-down support in place; Deployment is fully automated
System health & error logs dedicated IT business analyst, via features . Source code is
500 monitored. Processes for server admin, helpdesk, training managed centrally as IP, re-
archiving & de-provisioning are staff; empowered user usable and shareable. Content
Optimizing in place. community. Multiple training owners understand the
offerings exist. importance of QA testing.

Backup/restore has been tested.
Dev and QA environments are IT has more than one resource
Deployment is fully automated
present. Administration may be knowledgeable on the system.
400 improved via third-party tools. Requests for new functionality
– solution package and scripts.
Total Cost of Ownership is
Predictable BLOB integration may be are tracked and prioritized. An
considered.
present. Performance end-user training plan is in place.
considered.
Maturation

SP evangelized around the
Number of servers is appropriate Mixed automated manual
organization by individual or small
to demands and scalable for deployment process - some
group. Content owners from
300 future growth. Dev
some functional areas are trained
artifacts deployed via scripts,
environment is present. Service others by following list of
Defined and using the system. One IT
Packs tested in QA and installed manual steps. Source control
resource knowledgeable on the
in a timely fashion. is centralized.
system.

SP evangelized to a subset of
Changes are deployed from
Multiple server installlation or depts or functional areas by an
200 single-server is backed up on a individual; work mainly done by
one environment to another
using backup/restore. Source
Managed regular basis. individual or small group.
control is simple file storage.
Training is informal, ad-hoc.

No development, or
Single-server installation, development is done in
100 sometimes rogue . No plan for
One pioneer or small group pilots
Production. No QA /
the product.
Initial availability / disaster recovery. development environments.
No source control.

Self Evaluation Matrix
Publication Collaboration Business Search People & Composites & Integration Insight Infrastructure Staffing & Customizations
Process Communities Applications & Admin. Training
599
500
Optimizing
500
499
400
Predictable
400
399

300
Defined
300
299
200
200
Managed
199
100
Initial
100

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


Self Evaluation Matrix – Filled-in Example
Publication Collaboration Business Search People & Composites & Integration Insight Infrastructure Staffing & Customizations
Process Communities Applications & Admin. Training
599
500
Optimizing
500
499
400
Predictable
400
399

300
Defined
300
299
200
200
Managed
199
100
Initial
100

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 & 2.5
include vendors if they are a regular part of your team)
Organization’s Industry Professional Services


Data Model Examples


Excel Template Available

Go to http://www.sharepointmaturity.com to get your own!
#spstcdc

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.

Level Maturity Level Definition Competency
The particular area is functioning optimally Content is personalized to the user. Content is shared across
500 and continuous improvement occurs based on
multiple functions and systems without duplication.
Optimizing defined and monitored metrics.
Dynamic and personalized
Feedback mechanism is in place for pages and taxonomy.
Automated tagging may be present.

The particular area is centrally supported, Content is monitored, maintained, targeted to specific
400 standardized, and in use across the entire groups. Usage is analyzed. Digital assets are managed
organization. Governance is defined and appropriately. If more than one doc mgmt system is present,
Predictable governance is defined. Mobile access considered.
followed.
Site Columns/ Managed Metadata standardize the
The way the particular area is leveraged is taxonomy. Custom content Types are created. Custom page
300 Standardized
defined and/or standardized, but not in use and Targeted
layouts & site templates are configured. Approval process is
Defined across the entire organization. implemented. Incoming email activated for some lists/libs.
Site Map is present. Some content targeted to groups.

The particular area is managed by a central Custom metadata is applied to content. Templates
200 group (often IT), but the focus and definition
standardized across sites. Lists used rather than static HTML.
Multiple document mgmt systems may be present w/out
Managed varies by functional area. governance around purpose.

Navigation & taxonomy not formally considered. Little to no
100 Static and unorganized Folder structure re-created from shared
The starting point of SharePoint use.
checks on content.
drives. Content that could be in lists is posted in Content
Initial Editor WP. Out of box site templates / layouts are used.


Maturity per Years of Use

Publication
550
500
450
Maturity Level

400
350
350
300
300
250 272 266
278
236 243
200
150
100
1 2 3 4 6 7 9
Years of SharePoint Use


Publication – 100-level example

Source: S. Van Buren


Publication – 500-level example

Source: Microsoft


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).
The particular area is functioning
Collaboration occurs outside the firewall – i.e. with external
500 optimally and continuous improvement
Outsidecontributors. Automated processes exist for de-provisioning
the firewall
Optimizing occurs based on defined and monitored and archiving sites.
metrics.
The particular area is centrally supported,
Collaboration tools are used across the entire organization.
400 standardized, and in use across the entire
Email is captured & leveraged. Work is promoted from WIP to
Predictable organization. Governance is defined and Final which is leverageable. Mobile access considered.
followed.

The way the particular area is leveraged
Cross-enterprise and fuller functionality to discussion threads,
Collaboration efforts extend sporadically
300 is defined and/or standardized, but not in wikis, blogs, and doc libs with versioning. Site templates are
Defined use across the entire organization. developed for specific needs.

The particular area is managed by a Mechanism is in place for new site requests. Collaboration
200 central group (often IT), but the focus and efforts are collected in document libraries (links emailed rather
Managed definition varies by functional area. than documents)

100 Team-centric, Out of box collaboration sites formalas needed without
The starting point of SharePoint use. mostly organization. No set up process exists for
structure or
doc storage
Initial requesting a new site.



Collaboration

550
500
450
Maturity Level

400
350
300
250
200
150
100
1 2 3 4 6 7 9


Collaboration – 100-level example

Source: S. Van Buren:

Collaboration– 400-level example

Source: Nielsen Norman Intranet Design Annual 2010


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.

Power users can edit existing workflows to adapt them to
changing business needs on the fly. Users leverage data
The particular area is functioning optimally from BPM to optimize process, simulate on real data, clear
500 Analytics drive continuous
and continuous improvement occurs based
improvements
bottlenecks, balance work across workloads. Users have
Optimizing on defined and monitored metrics. visibility into the process and can provide feedback to
process improvements. Business processes extend to
external users.

The particular area is centrally supported, 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
Predictable organization. Governance is defined and the context of a work item as part of a dynamic, nonlinear
followed. business process (the “case”).

Process is considered as a whole, rather than as automating
Applications consolidated, processes automated document
The way the particular area is leveraged is functional tasks. Transition from procedural
300 defined and/or standardized, but not in use workflow to orchestration of dynamic business process.
SharePoint is becoming the BP platform, w/the introduction
Defined across the entire organization. of 3rd party BPM tool to support more complex business
rules.

The particular area is managed by a central Business processes are designed; some custom,
200 group (often IT), but the focus and definition departmental “no-code” workflows (SP Designer, Visio, or
third-party tool) may be implemented to handle simple
Managed varies by functional area. business rules (decision-based routing). .

Business process is loosely defined. Out of the box
100 There are workflows in SharePoint?
SharePoint workflows (approval, collect feedback) leveraged
The starting point of SharePoint use. sporadically. A doclib or list provides a central base of
Initial operations. Any workflow is document- vs. application- 48
centric.
8/13/2011 - #spmaturity @sadalit #spstcdc ©2011 Sadalit Van Buren


Business Process
550
500
450
Maturity Level

400
350
300
250
200
150
100
1 2 3 4 6 7 9



Business Process – 100-level example



Business Process – 500-level example

Source: Global360

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.

The particular area is functioning optimally Users understand relationship of tagging to search
500 Content finds me based on the preferencesmay be used. High
and continuous improvement occurs based results. Automated tagging I set
Optimizing on defined and monitored metrics. volumes can be handled.

Content types and custom properties are leveraged
in Advanced Search and/or refiners. Results
Predictable organization. Governance is defined and
customized to specific needs, may be actionable.
followed.
The way the particular area is can filter queries and results
I leveraged is Search results are analyzed. Best bets and
300 defined and/or standardized, but not in use metadata properties are leveraged to aid the
Defined across the entire organization. search experience.
The particular area is managed by a central Custom scopes and iFilters employed to aid the
200 group (often IT), but the focus and search experience. Content may be federated.
Managed definition varies by functional area. Search Center created.
Out of box functionality for query, results, and
100 The starting point of SharePoint use. and don’t expect much from results. be
I use keyword search scopes; some additional content sources may
Initial indexed.


Search
550
500
450
Maturity Level

400
350
300
250
200
150
100
1 2 3 4 6 7 9



Search – 100-level example

#spstcdc

Search – 400-level example (query)


Search – 400-level example (results)


People and 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).

The particular area is functioning optimally
Users can edit certain profile data that writes back to AD or
500 and continuous improvement occurs based
Optimizing
Unified Community Experiencecustomized. Communities
on defined and monitored metrics. MySites
HRIS. MySites template is
extend to external participants.
may be allowed for external users.

Profile fields may integrate with LOB data. MySites are
centralized (only one instance). Communities flourish under
Predictable organization. Governance is defined and governance.
followed.
Custom profile fields reflect company culture; photos are
The way the particular area is leveragedof tools enterprise-wide
300 Availability is updated from central source.
defined and/or standardized, but not in use MySites rolled out to all users, supported, trained.
Defined across the entire organization. Community spaces connect a particular set of users.

The particular area is managed by a central
MySites rolled out to pilot groups or users. Out-of-box
Managed profiiles implemented. Community spaces may be piloted.
varies by functional area.

Individual Needs imported from AD or other source.
Basic profile data
Initial MySites host not created.



People & Communities

9 350

7 252

6 200

4 312

3 148

1 280

100 150 200 250 300 350 400 450 500 550
Average Maturity Level


People and Communities – 100-level example


People and Communities – 500-level example



Composites and 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.
The particular area is functioning optimally Forms connect with LOB data. New capabilities &
500
Optimizing
Seamless integration withare surfaced & integrated into
and continuous improvement occurs based requirements LOB data
on defined and monitored metrics. downstream capabilities.

400 standardized, and in use across the entire InfoPath forms improve the user experience. Mobile
Predictable organization. Governance is defined and functionality is supported.
followed.
The way the particular area is leveraged is
300 defined and/or standardized, butDepartmental Adoption
not in
Most critical business forms are online; some
Defined involve automated workflows.
use across the entire organization.

The particular area is managed by a central Increasing use of SP lists to replace Excel
200 group (often IT), but the focus and spreadsheets and paper forms. Applications are
Managed definition varies by functional area. opened up to a larger group of users.

Some paper forms converted to SP list forms. Many
100 Replacement Excel spreadsheets, Access databases, paper forms
The starting point of SharePoint use. of a few key apps
Initial still stored in / linked to from SharePoint.



Composites & Applications

9 300

7 268

6 363

4 292

3 258

1 262

100 150 200 250 300 350 400 450 500 550


Composites & Applications – 100-level example


Composites & Applications – 400-level example

Source: Nielsen Norman Intranet Annual 2010

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.
500 External data (partner/supplier or industry) is
Most systems integrated
and continuous improvement occurs based
Optimizing integrated with SP.
on defined and monitored metrics.

Most of the systems that are desired to be
integrated, are integrated. A data warehouse may
be integrated with SP.
followed.
The way the particular area is leveragedsystems integrated
is
Some use Multiple systems are integrated.
300 defined and/or standardized, but not in
Defined across the entire organization.
200 group (often IT), but the focus and definition A single system is integrated with SP.
Managed varies by functional area.

Links to enterprise systems posted on SP site.
100 Links
The starting point of SharePoint use. to other systems business data is stored in doc
Printed or exported
Initial libs.

Integration – 100-level example



Integration – 400-level example

Source: Nielsen Norman Intranet Annual 2010



Integration

9 300

7 255

6 338

4 247

3 221

1 212

100 150 200 250 300 350 400 450 500 550


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.

500 I can see what’s Analyticsto happen. employed.
and continuous improvement occurs based going and trending are
Optimizing on defined and monitored metrics.

Items are actionable.
followed.
The way the particular area isIleveraged is what’s happening
can see
300 defined and/or standardized, but not in use Reports allow drill-down and charting.
Defined across the entire organization.
200 group (often IT), but the focus and definition Reports are aggregated through customization.
Managed varies by functional area.

100 I can
The starting point of SharePoint use. see what happened. used; data is brought together
Existing reports are
Initial manually.



Insight

9 300

7 247

6 338

4 183

3 191

1 212

100 150 200 250 300 350 400 450 500 550


Insight – 100-level example


Insight – 500-level example

Source:


Infrastructure
The hardware and processes that support the system. Areas of focus include farm
planning, server configuration, storage, backup/restore, monitoring, and updates.

The particular area is functioning optimally and System health & error logs monitored.
500 continuous improvement occurs based on Processes for archiving & de-provisioning are in
Optimizing defined and monitored metrics. place. Disaster Recovery plan is in place.

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
followed. Users trust the system.
considered.
The way the particular area is leveraged is Number of servers is appropriate to demands
300 defined and/or standardized, but not in use and scalable for future growth. Dev
Defined across the entire organization. Remote access is environment is present. Service Packs tested in
available. QA and installed in a timely fashion.
Multiple server installlation or single-server is
Managed backed up on a regular basis.
varies by functional area.

Single-server installation, sometimes rogue .
Initial No plan for availability / disaster recovery.



Infrastructure

9 450

7 362

6 338

4 408

3 244

1 342

100 150 200 250 300 350 400 450 500 550


Staffing and Training
The human resources that support the system and the level of training with which
they are provided.

The particular area is functioning optimally and Top-down support in place; dedicated IT business
500 continuous improvement occurs based on
analyst, server admin, helpdesk, training staff;
Optimizing empowered user community. Multiple training offerings
defined and monitored metrics. exist.

IT has more than one resource knowledgeable on the
system. Requests for new functionality are tracked and
Predictable organization. Governance is defined and prioritized. An end-user training plan is in place.
followed.

The way the particular area is leveraged is SP evangelized around the organization by individual or
300 defined and/or standardized, but not in use
small group. Content owners from some functional areas
Defined are trained and using the system. One IT resource
across the entire organization. knowledgeable on the system.

The particular area is managed by a central SP evangelized to a subset of depts or functional areas by
200 group (often IT), but the focus and definition an individual; work mainly done by individual or small
Managed varies by functional area. group. Training is informal, ad-hoc.

100 The starting point of SharePoint use. One pioneer or small group pilots the product.
Initial


Staffing & Training

9 450

7 362

6 338

4 408

3 244

1 342

100 150 200 250 300 350 400 450 500 550


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, and development
tier.
The particular area is functioning optimally Deployment is fully automated via features .
500 and continuous improvement occurs based Source code is managed centrally as IP, re-usable
Optimizing on defined and monitored metrics. and shareable.

Deployment is fully automated – solution package
and scripts. Total Cost of Ownership is
considered.
followed.
Mixed automated manual deployment process -
The way the particular area is leveraged is
300 defined and/or standardized, but not in use
some artifacts deployed via scripts, others by
Defined following list of manual steps. Source control is
across the entire organization.
centralized.
The particular area is managed by a central Changes are deployed from one environment to
200 group (often IT), but the focus and definition another using backup/restore. Source control is
Managed varies by functional area. simple file storage.
No development, or development is done in
100 The starting point of SharePoint use. Production. No QA / development environments.
Initial No source control.


Customizations

9 350

7 373

6 288

4 200

3 289

1 255

100 150 200 250 300 350 400 450 500 550


#spstcdc

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)


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.


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


Assess Your SharePoint Maturity with the Maturity Model

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Assess Your SharePoint Maturity with the Maturity Model

Similaire à Assess Your SharePoint Maturity with the Maturity Model (20)

Dernier

Dernier (20)

Assess Your SharePoint Maturity with the Maturity Model