The SharePoint Maturity Model

Transcription

1 The SharePoint Maturity Model Presented as a Live Broadcast for Nothing But SharePoint 1 March 2011 Hosted By 1

2 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 & Resources 2

3 Logistics If you re tweeting or live blogging, please include #EUSP Download and Print the Self Evaluation Matrix: 3

4 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 reevaluating 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

5 Data Model Examples 5

6 About Me Project Manager and Business Analyst focusing on SharePoint Working with SharePoint since beta 2003 version 50 SharePoint implementations Microsoft Certified Technology Specialist Consulting Manager, Burntsand 6

7 About My Company Leading systems integration firm founded in January 1996 Microsoft partner with 2 gold competencies, 3 silver More than 350 blue chip clients Subsidiary of Open Text, local office in Waltham, MA Publicly traded on Toronto Stock Exchange (OTEX) Have delivered solutions built on the SharePoint and.net platforms since their inception in

8 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 Does NOT cover: Public-facing websites Compliance and regulatory issues Visual design and branding Version 1 published 5 November

9 About Microsoft s SP Competencies Business Connectivity Services InfoPath Form Services External Lists Workflow SharePoint Designer Visual Studio API Enhancements REST/ATOM/RSS PerformancePoint Services Excel Services Chart Web Part Visio Services Web Analytics SQL Server Integration PowerPivot Social Relevance Phonetic Search Navigation FAST Integration Enhanced Pipeline Ribbon UI SharePoint Workspace SharePoint Mobile Office Client & Web App Integration Standards Support Tagging, Tag Cloud, Ratings Social Bookmarking Blogs and Wikis My Sites Activity Feeds Profiles and Expertise Org Browser Enterprise Content Types Metadata and Navigation Document Sets Multi-stage Disposition Audio and Video Content Types Remote Blob Storage List Enhancements

10 Competency Definitions - Core 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 Search 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, tracking / auditing. 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. 10

11 Competency Definitions - Advanced 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. 11

12 Competency Definitions - Readiness Area Description Infrastructure 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, and development tier. 12

13 Maturation Maturity Level Definitions SharePoint Level 500 Optimizing 400 Predictable Description The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. 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. 200 Managed The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. 100 Initial The starting point of SharePoint use. 13

14 Maturation The SharePoint Maturity Model 1 Core Concepts Maturation also occurs along this vector 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 on taxonomy is in place. 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. Users have visibility into process efficiency & can provide feedback into process improvements. Workflows incorporate external users. Users understand relationship of tagging to search results. Automated tagging may be used. High volumes can be handled. 400 Predictable 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. Collaboration tools are used across the entire organization. is captured & leveraged. Work is promoted from WIP to Final which is leverageable. The majority of business processes are represented in the system and have audit trails. Mobile functionality is supported. Workflow scope is enterprise-level. Content types and custom properties are leveraged in Advanced Search. Results customized to specific needs, may be actionable. 300 Defined Site Columns/ Managed Metadata standardize the taxonomy. Page layouts & site templates are customized. Approval process is implemented. Collaboration efforts extend sporadically to discussion threads, wikis, blogs, and doc libs with versioning. Site templates are developed for specific needs. Workflows can recognize the user (i.e. knows my manager ). Content types are leveraged. Workflow scope spans departments or sites. 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 ed rather than documents) Business process is defined; some custom SP Designer workflows (or third-party tool) may be implemented. Workflow scope is at departmental level. Custom scopes and ifilters employed to aid the search experience. 100 Initial Navigation & taxonomy not formally considered. Little to no checks on content. Folder structure is 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 box workflows (approval, collect feedback) leveraged sporadically. A doc lib or list provides a central base of operations. Out of box functionality for query, results, and scopes; some additional content sources may be indexed. 14

15 Maturation The SharePoint Maturity Model 2 Advanced Concepts Maturation also occurs along this vector 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). 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. 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. 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. Existing reports are used; data is brought together manually. 15

16 Maturation The SharePoint Maturity Model 3 Readiness Concepts Maturation also occurs along this vector Level Infrastructure 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, reusable and shareable. 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. 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. 16

17 Self Evaluation Matrix Publication Collaboration Business Process Search People & Communities Composites & Applications Integration Insight Infrastructure Staffing & Training Customizations Optimizing 400 Predictable 300 Defined 200 Managed 100 Initial 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 Go to for a quick way to graph this information! 17

18 Self Evaluation Matrix Filled-in Example Publication Collaboration Business Process Search People & Communities Composites & Applications Integration Insight Infrastructure Staffing & Training Customizations Optimizing 400 Predictable 300 Defined 200 Managed 100 Initial 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 Go to for a quick way to graph this information! 18

19 Excel Template Available Go to to get your own! 19

20 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 500 Optimizing 400 Predictable 300 Defined 200 Managed The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. Content is personalized to the user. Content is shared across multiple functions and systems without duplication. Feedback mechanism on taxonomy is in place. Automated tagging may be present. 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. Site Columns/ Managed Metadata standardize the taxonomy. Page layouts & site templates are customized. Approval process is implemented. 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 The starting point of SharePoint use. Initial Navigation & taxonomy not formally considered. Little to no checks on content. Folder structure is 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. 20

21 Publication 100-level example Source: Burntsand 21

22 Publication 500-level example Source: Burntsand 22

23 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). Level Maturity Level Definition Competency 500 Optimizing 400 Predictable 300 Defined 200 Managed 100 Initial The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. The starting point of SharePoint use. Collaboration occurs outside the firewall i.e. with external contributors. Automated processes exist for de-provisioning and archiving sites. Collaboration tools are used across the entire organization. is captured & leveraged. Work is promoted from WIP to Final which is leverageable. Collaboration efforts extend sporadically to discussion threads, wikis, blogs, and doc libs with versioning. Site templates are developed for specific needs. Mechanism is in place for new site requests. Collaboration efforts are collected in document libraries (links ed rather than documents) Out of box collaboration sites set up as needed without structure or organization. No formal process exists for requesting a new site. 23

24 Collaboration 100-level example Source: Burntsand 24

25 Collaboration 500-level example Source: Burntsand 25

26 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, tracking / auditing. Level Maturity Level Definition Competency 500 Optimizing 400 Predictable 300 Defined 200 Managed 100 Initial The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. The starting point of SharePoint use. Power users can edit existing workflows to adapt them to changing business needs. Users have visibility into process efficiency & can provide feedback into process improvements. Workflows incorporate external users. The majority of business processes are represented in the system and have audit trails. Mobile functionality is supported. Workflow scope is enterprise-level. Workflows can recognize the user (i.e. knows my manager ). Content types are leveraged. Workflow scope spans departments or sites. Business process is defined; some custom SP Designer workflows (or third-party tool) may be implemented. Workflow scope is at departmental level. Business process is loosely defined. Out of box workflows (approval, collect feedback) leveraged sporadically. A doc lib or list provides a central base of operations. 26

27 Business Process 100-level example Source: Burntsand 27

28 Business Process 500-level example Source: Nielsen Norman Group Intranet Design Annual 2010, Enbridge intranet, p

29 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. Level Maturity Level Definition Competency 500 Optimizing 400 Predictable 300 Defined 200 Managed The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. Users understand relationship of tagging to search results. Automated tagging may be used. High volumes can be handled. Content types and custom properties are leveraged in Advanced Search. Results customized to specific needs, may be actionable. Search results are analyzed. Best bets and metadata properties are leveraged to aid the search experience. Custom scopes and ifilters employed to aid the search experience. 100 Initial The starting point of SharePoint use. Out of box functionality for query, results, and scopes; some additional content sources may be indexed. 29

30 Search 100-level example Source: Burntsand 30

31 Search 500-level example Source: Burntsand 31

32 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). Level Maturity Level Definition Competency 500 Optimizing 400 Predictable 300 Defined The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. MySites may be allowed for external users. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. Users can edit certain profile data that writes back to AD or HRIS. MySites template is customized. Communities extend to external participants. Profile fields may integrate with LOB data. MySites are centralized (only one instance). Communities flourish under governance. 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 100 Initial The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. The starting point of SharePoint use. MySites rolled out to pilot groups or users. Out-of-box profiiles implemented. Community spaces may be piloted. Basic profile data imported from AD or other source. MySites host not created. 32

33 People and Communities 100-level example Source: Burntsand 33

34 People and Communities 500-level example Source: Burntsand 34

35 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. Level Maturity Level Definition Competency 500 Optimizing 400 Predictable 300 Defined 200 Managed The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. Forms connect with LOB data. New capabilities & requirements are surfaced & integrated into downstream capabilities. InfoPath forms improve the user experience. Mobile functionality is supported. Most critical business forms are online; some involve automated workflows. 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. 35

36 Composites & Applications 100-level example Source: Burntsand 36

37 Composites & Applications 500-level example Source: Burntsand 37

38 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. Level Maturity Level Definition Competency 500 Optimizing 400 Predictable 300 Defined 200 Managed The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. External data (partner/supplier or industry) is integrated with SP. Most of the systems that are desired to be integrated, are integrated. A data warehouse may be integrated with SP. Multiple systems are integrated. 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. 38

39 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. Level Maturity Level Definition Competency 500 Optimizing 400 Predictable 300 Defined 200 Managed 100 Initial The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. The starting point of SharePoint use. Analytics and trending are employed. Items are actionable. Reports allow drill-down and charting. Reports are aggregated through customization. Existing reports are used; data is brought together manually. 39

40 Insight 100-level example Source: Burntsand 40

41 Insight 500-level example Source: Burntsand 41

42 Infrastructure The hardware and processes that support the system. Areas of focus include farm planning, server configuration, storage, backup/restore, monitoring, and updates. Level Maturity Level Definition Competency 500 Optimizing 400 Predictable 300 Defined 200 Managed 100 Initial The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. Users trust the system. The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. Remote access is available. The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. The starting point of SharePoint use. System health & error logs monitored. Processes for archiving & de-provisioning are in 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. 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. Multiple server installlation or single-server is backed up on a regular basis. Single-server installation, sometimes rogue. No plan for availability / disaster recovery. 42

43 Staffing and Training The human resources that support the system and the level of training with which they are provided. Level Maturity Level Definition Competency 500 Optimizing 400 Predictable The particular area is functioning optimally and continuous improvement occurs based on defined and monitored metrics. The particular area is centrally supported, standardized, and in use across the entire organization. Governance is defined and followed. Top-down support in place; dedicated IT business analyst, server admin, helpdesk, training staff; empowered user community. Multiple training offerings exist. 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 200 Managed 100 Initial The way the particular area is leveraged is defined and/or standardized, but not in use across the entire organization. The particular area is managed by a central group (often IT), but the focus and definition varies by functional area. The starting point of SharePoint use. 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. 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. One pioneer or small group pilots the product. 43

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

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

46 Contact Information Sadie Van Buren LinkedIn: 46

47 Resources Self Evaluation Matrix: Excel Template for the Self-Assessment: 47

48 Credits SharePoint Maturity Model (Customizations) from Hugo Esperanca s blog. Rate Your Organization's SharePoint Collaboration Maturity, from Lee Reed on EUSP: Capability Maturity Model: 48

49 Acknowledgements Thanks to Mark Miller at End User SharePoint and the folks at for hosting this presentation. My gratitude to Vinnie Alwani, Harold Brenneman, John Francis, Sue Hanley, Richard Harbridge, Mike Landino, Chris McNulty, Mark Miller, Ed Podbelski, Ray Walters, and Derek Weeks for their input and support. 49

50 Thank you! 50