The SharePoint Maturity Model - as presented 2 June 2011 at SPTechCon Boston

©2011 Sadalit Van Buren 1

The SharePoint Maturity Model

Presented at SPTechCon2 June 2011

6/2/2011 - #SPTechCon #spmaturity @sadalit


Agenda

• Logistics• What’s in it for me?• About Me• About My Company• About the SharePoint Maturity Model• About Microsoft’s SP Competencies• SMM Competency Definitions• SMM Maturity Level Definitions• The SharePoint Maturity Model - overview• Self Evaluation Matrix• The SharePoint Maturity Model – detail & case studies• Credits & Resources6/2/2011 - #SPTechCon #spmaturity @sadalit


Logistics

• Questions• If you’re tweeting / live blogging, please

include:– #SPMaturity – @sadalit

• BASPUG – tonight – 7-9 pm• SharePint – [location TBD]



What’s In It For Me?

• The Maturity Model can help you 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.



Data Model Examples


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 Technology Specialist

6

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.

6/2/2011 - #SPTechCon #spmaturity @sadalit ©2011 Sadalit Van Buren 7

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.

• 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.


About Microsoft’s SP CompetenciesRibbon UISharePoint WorkspaceSharePoint MobileOffice Client & 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

Source: Microsoft Corp.

About Customizations in SharePoint

• For the purposes of the Maturity Model, Customizations are defined as anything that touches the SharePoint server – i.e. the 12 hive, inetpub, or GAC (thanks Mark Miller!)

• Called “Development” by some • Represented with a red line in the matrix – above

the line, customization may be needed.


http://www.sharepointdevwiki.com/display/SharePointPlaybook/Defining+SharePoint+Development


Area Description

PublicationPresentation 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.

CollaborationMultiple 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.

SearchThe 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



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.

IntegrationLine 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.

InsightThe 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



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.

CustomizationsCustom 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



SharePoint Level Description

500Optimizing

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

400Predictable

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

300Defined

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.

200Managed

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.

100Initial

The starting point of SharePoint use.

Mat

urati

onMaturity Level Definitions



The SharePoint Maturity Model – 1 – Core Concepts


Level Publication Collaboration Business Process Search

500Optimizing

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.

400Predictable

Content is monitored, maintained, some is 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. Results are customized to specific needs, may be actionable.

300Defined

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.

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.

200Managed

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.

100Initial

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

urati

on

Maturation also occurs along this vector


The SharePoint Maturity Model – 2 – Advanced Concepts


Mat

urati

on

Level People and Communities

Composites and Applications Integration Insight

500Optimizing

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.

400Predictable

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.

300Defined

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.

200Managed

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.

100Initial

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.



The SharePoint Maturity Model – 3 – Readiness Concepts


Mat

urati

on

Level Infrastructure and Administration Staffing & Training Customizations

500Optimizing

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.

400Predictable

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.

300Defined

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.

200Managed

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.

100Initial

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.



Self Evaluation Matrix


Date of AssessmentYears the organization has used SharePointCurrent 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


Integration Insight Infrastructure & Admin.

Staffing & Training

Customizations

500Optimizing

400Predictable

300Defined

200Managed

100Initial

100

199200

299300

399400

499500

599


Self Evaluation Matrix – Filled-in ExamplePublication Collaboration Business

ProcessSearch People &

CommunitiesComposites & Applications

Integration Insight Infrastructure & Admin.

Staffing & Training

Customizations

500Optimizing

400Predictable

300Defined

200Managed

100Initial

Date of Assessment 1/29/11Years the organization has used SharePoint 7Current 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

199200

299300

399400

499500

599



Excel Template Available

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


http://www.sharepointmaturity.com/


Publication

Level Maturity Level Definition Competency

500Optimizing


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.

400Predictable


Content is monitored, maintained, some is 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.

300Defined

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.

200Managed

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.

100Initial

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.



Maturity per Years of Use


1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

236

254

258

300

278

350

Publication

Average Maturity Level

Year

s of S

hare

Poin

t Use


Publication – 100-level example


Source: S. Van Buren


Publication – 500-level example


Source: Microsoft


Collaboration


500Optimizing


Collaboration occurs outside the firewall – i.e. with external contributors. Automated processes exist for de-provisioning and archiving sites.

400Predictable


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.

300Defined


Collaboration efforts extend sporadically to discussion threads, wikis, blogs, and doc libs with versioning. Site templates are developed for specific needs.

200Managed


Mechanism is in place for new site requests. Collaboration efforts are collected in document libraries (links emailed rather than documents)

100Initial

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





1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

226

261

333

180

336

400

Collaboration


Year

s of S

hare

Poin

t Use


Collaboration – 100-level example


Source: S. Van Buren:


Collaboration– 400-level example


Source: Nielsen Norman Intranet Design Annual 2010

30

Business Process


500Optimizing


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.

400Predictable


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”).

300Defined


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.

200Managed


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

100Initial

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.

6/2/2011 - #SPTechCon #spmaturity @sadalit ©2011 Sadalit Van Buren


Business Process – End User PerspectiveLevel End User Perspective

500Optimizing

Managers have a business process dashboard that allows them to see all work in progress as well as trends in business demand. Processes are goal-driven with associated service level agreements and productivity expectations. Within the dashboard, managers can reassign work or workers on-the-fly to adjust to changing business demands. Knowledge workers also have access to personal performance metrics allowing them to optimize their own performance. Operational data about the process execution is examined regularly by business analysts for potential improvements.

400Predictable

We have modeled our end-to-end business process. We monitor business activities to understand what’s happening and identify potential hot spots; we recognize the need to re-engineer and improve existing processes to maintain competitiveness. The application has allowed us to consolidate many different legacy apps and data from various enterprise applications into one common view of my work; I went from using 7 different applications to a single one in order to get my work done. I can access my work from any browser-based environment, including those on mobile devices.

300Defined

We understand the need to automate processes to improve how work gets done. The workflow can recognize me or my role, and fill in information about me (“my manager”). Process work is assigned to roles, not people. We use an application that helps us get work done; we don’t recognize the application as SharePoint, it is our Accounts Payable, Employee Onboarding, Claims Processing, Learning Gateway, or XXX app. The work may be complex and span many departments. The application understands rules and routing specific to our business process.

200Managed

We use simple workflows for tasks like approvals within our department. I initiate tasks or report their completion in SharePoint.

100Initial

There are workflows in SharePoint? What is a workflow? I know how to route a document for approval within SharePoint





1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

216

219

217

275

273

340

Business Process


Year

s of S

hare

Poin

t Use


Business Process – 100-level example




Business Process – 500-level example

Source: Global3606/2/2011 - #SPTechCon #spmaturity @sadalit


Search


500Optimizing


Users understand relationship of tagging to search results. Automated tagging may be used. High volumes can be handled.

400Predictable


Content types and custom properties are leveraged in Advanced Search. Results customized to specific needs, may be actionable.

300Defined


Search results are analyzed. Best bets and metadata properties are leveraged to aid the search experience.

200Managed


Custom scopes and iFilters employed to aid the search experience. Content may be federated.

100Initial

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.





1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

206

179

175

275

199

150

Search


Year

s of S

hare

Poin

t Use


Search – 100-level example




Search – 400-level example (query)

Source: Nielsen Norman Intranet Design Annual 20106/2/2011 - #SPTechCon #spmaturity @sadalit


Search – 400-level example (results)

Source: S. Van Buren6/2/2011 - #SPTechCon #spmaturity @sadalit


People and Communities


500Optimizing

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.

400Predictable


Profile fields may integrate with LOB data. MySites are centralized (only one instance). Communities flourish under governance.

300Defined


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.

200Managed


MySites rolled out to pilot groups or users. Out-of-box profiiles implemented. Community spaces may be piloted.

100Initial

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





1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

280

148

312

200

252

350

People & Communities


Year

s of S

hare

Poin

t Use


People and Communities – 100-level example




People and Communities – 500-level example

Source: Nielsen Norman Intranet Design Annual 2010



Composites and Applications


500Optimizing


Forms connect with LOB data. New capabilities & requirements are surfaced & integrated into downstream capabilities.

400Predictable


InfoPath forms improve the user experience. Mobile functionality is supported.

300Defined


Most critical business forms are online; some involve automated workflows.

200Managed


Increasing use of SP lists to replace Excel spreadsheets and paper forms. Applications are opened up to a larger group of users.

100Initial

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.





1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

262

258

292

363

268

300



Year

s of S

hare

Poin

t Use

©2011 Sadalit Van Buren

Composites & Applications – 100-level example




Composites & Applications – 400-level example

Source: Nielsen Norman Intranet Annual 20106/2/2011 - #SPTechCon #spmaturity @sadalit


Integration


500Optimizing


External data (partner/supplier or industry) is integrated with SP.

400Predictable


Most of the systems that are desired to be integrated, are integrated. A data warehouse may be integrated with SP.

300Defined


Multiple systems are integrated.

200Managed


A single system is integrated with SP.

100Initial

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.



Integration – 100-level example




Integration – 400-level example


Source: Nielsen Norman Intranet Annual 2010




1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

212

221

247

338

255

300

Integration


Year

s of S

hare

Poin

t Use


Insight


500Optimizing


Analytics and trending are employed.

400Predictable


Items are actionable.

300Defined


Reports allow drill-down and charting.

200Managed


Reports are aggregated through customization.

100Initial

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.





1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

212

191

183

338

247

300

Insight


Year

s of S

hare

Poin

t Use


Insight – 100-level example



Insight – 500-level example


Source:


Infrastructure


500Optimizing


System health & error logs monitored. Processes for archiving & de-provisioning are in place. Disaster Recovery plan is in place.

400Predictable

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.

300Defined

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.

200Managed


Multiple server installlation or single-server is backed up on a regular basis.

100Initial

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.





1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

342

244

408

338

362

450

Infrastructure


Year

s of S

hare

Poin

t Use


Staffing and Training


500Optimizing


Top-down support in place; dedicated IT business analyst, server admin, helpdesk, training staff; empowered user community. Multiple training offerings exist.

400Predictable


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.

300Defined


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.

200Managed


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.

100Initial

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.





1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

342

244

408

338

362

450

Staffing & Training


Year

s of S

hare

Poin

t Use


Customizations


500Optimizing


Deployment is fully automated via features . Source code is managed centrally as IP, re-usable and shareable.

400Predictable


Deployment is fully automated – solution package and scripts. Total Cost of Ownership is considered.

300Defined


Mixed automated \ manual deployment process - some artifacts deployed via scripts, others by following list of manual steps. Source control is centralized.

200Managed


Changes are deployed from one environment to another using backup/restore. Source control is simple file storage.

100Initial

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.





1

3

4

6

7

9

100 150 200 250 300 350 400 450 500 550

255

289

200

288

373

350

Customizations


Year

s of S

hare

Poin

t Use


Future Plans and Improvements

• Centralized system for receiving data• Mapping to vendors – services and products• Business Process considerations (in conjunction

with Global360)• Mapping to resourcing• Mapping to SP versions

– Standard/Enterprise– Cloud

• Operational steps to maturity in the competencies (shoutout to Torben Ellert for tackling Search)



Call to Action

• 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.



Upcoming Events

• June 7 – Enterprise Enablement Virtual Conference – Business Process & SP Maturity– https://

msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032486583

• June 20-23: Enterprise 2.0 Boston – Social Strategies for SP with Shawn Shell & Unni Loland– http://www.e2conf.com/boston/

• July 30 – SharePoint Saturday NYC– The SP Maturity Model– http://www.sharepointsaturday.org/ny/default.aspx


https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032486583




http://www.e2conf.com/boston/

http://www.sharepointsaturday.org/ny/default.aspx




Contact Information

Sadie Van Buren• Twitter: @sadalit• LinkedIn: http://www.linkedin.com/in/sadalit

SharePoint Maturity• Twitter: @SPMaturity• http://www.sharepointmaturity.com– Tools, templates, and resources


http://www.linkedin.com/in/sadalit



http://www.sharepointmaturity.com/


Thank you!


The SharePoint Maturity Model - as presented 2 June 2011 at SPTechCon Boston

Technology

Transcript of The SharePoint Maturity Model - as presented 2 June 2011 at SPTechCon Boston