As SharePoint gains in popularity and adoption worldwide, an increasing number of resources is available to help organizations understand and navigate the different aspects of this platform. What’s missing is a cohesive way to analyze and understand the whole; yet most experts have observed that, although SharePoint implementations vary from organization to organization, there is a typical progression of implementation, upward through each functional area and across the areas together. The SharePoint Maturity Model applies a holistic view to a SharePoint implementation, and brings standardization to the conversation around functionality, best practices, and improvement.
The SharePoint Maturity Model - as presented at SP Saturday Hartford 1/29/11
1. The SharePoint Maturity Model Presented at SharePoint Saturday Hartford By Sadie Van Buren 29 January 2011
2. Agenda 1/29/2011 2 What’s in it for me? About the SharePoint Maturity Model About Me About Burntsand 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 Copyright 2011 Sadalit Van Buren
3. What’s In It For Me? If you are committed to maturing your SharePoint implementation, 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. 1/29/2011 3 Copyright 2011 Sadalit Van Buren
4. 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. What this model does NOT cover: Public-facing websites Compliance and regulatory issues. Version 1 published 5 November 2010. 1/29/2011 Copyright 2011 Sadalit Van Buren 4
14. Have delivered solutions built on the SharePoint and .NET platforms since their inception in 20011/29/2011 Copyright 2011 Sadalit Van Buren 6
15. Microsoft’s SP Competencies Ribbon UI SharePoint Workspace SharePoint Mobile Office Client & Web App Integration Standards Support Business Connectivity Services InfoPath Form Services External Lists Workflow SharePoint Designer Visual Studio API Enhancements REST/ATOM/RSS Sites Tagging, Tag Cloud, Ratings Social Bookmarking Blogs and Wikis My Sites Activity Feeds Profiles and Expertise Org Browser Communities Composites Content Insights PerformancePoint Services Excel Services Chart Web Part Visio Services Web Analytics SQL Server Integration PowerPivot Search Enterprise Content Types Metadata and Navigation Document Sets Multi-stage Disposition Audio and Video Content Types Remote Blob Storage List Enhancements Social Relevance Phonetic Search Navigation FAST Integration Enhanced Pipeline
20. The SharePoint Maturity Model – 1 – Core Concepts Maturation also occurs along this vector Maturation 1/29/2011 12 Copyright 2011 Sadalit Van Buren
21. The SharePoint Maturity Model – 2 – Advanced Concepts Maturation 1/29/2011 13 Maturation also occurs along this vector Copyright 2011 Sadalit Van Buren
22. The SharePoint Maturity Model – 3 – Readiness Concepts Maturation 1/29/2011 14 Maturation also occurs along this vector Copyright 2011 Sadalit Van Buren
23. Self Evaluation Matrix 1/29/2011 15 Go to http://bit.ly/SMMExcelTemplate for a quick way to graph this information! Copyright 2011 Sadalit Van Buren
24. Self Evaluation Matrix – Filled-in Example 1/29/2011 16 Go to http://bit.ly/SMMExcelTemplate for a quick way to graph this information! Copyright 2011 Sadalit Van Buren
25. Excel Template Available 1/29/2011 17 Go to http://bit.ly/SMMExcelTemplate to get your own! Copyright 2011 Sadalit Van Buren
26. Publication 1/29/2011 18 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. Copyright 2011 Sadalit Van Buren
27.
28. Collaboration 1/29/2011 20 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). Copyright 2011 Sadalit Van Buren
29.
30. Business Process 1/29/2011 22 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. Copyright 2011 Sadalit Van Buren
31.
32. Search 1/29/2011 24 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. Copyright 2011 Sadalit Van Buren
33.
34. People and Communities 1/29/2011 26 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). Copyright 2011 Sadalit Van Buren
35.
36. Composites and Applications 1/29/2011 28 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. Copyright 2011 Sadalit Van Buren
37.
38. Integration 1/29/2011 30 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. Copyright 2011 Sadalit Van Buren
39. Insight 1/29/2011 31 The means of viewing business data in the system. Maturity proceeds through aggregation of views, drill-down and charting, actionability, and analytics and trending. Copyright 2011 Sadalit Van Buren
40.
41. Infrastructure 1/29/2011 33 The hardware and processes that support the system. Areas of focus include farm planning, server configuration, storage, backup/restore, monitoring, and updates. Copyright 2011 Sadalit Van Buren
42. Staffing and Training 1/29/2011 34 The human resources that support the system and the level of training with which they are provided. Copyright 2011 Sadalit Van Buren
43. Customizations 1/29/2011 35 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. Copyright 2011 Sadalit Van Buren
44. Call to Action Fill out the Session Evaluation Fill out the SMM self-assessment! Turn in your data to help build a data model for everyone. Contact me With Questions With Feedback If you’d like help assessing your SP implementation and learning more about how to get to greater SharePoint Maturity. 1/29/2011 36 Copyright 2011 Sadalit Van Buren
45. Resources Excel Template for the Self-Assessment: http://bit.ly/SMMExcelTemplate 1/29/2011 37 Copyright 2011 Sadalit Van Buren
46. Credits SharePoint Maturity Model (Customizations) from Hugo Esperanca’s blog. http://activeobjects.blogspot.com/2008/07/sharepoint-maturity-model-smm_20.html Rate Your Organization's SharePoint Collaboration Maturity, from Lee Reed on EUSP: http://www.endusersharepoint.com/2010/01/07/adoption-tip-4-of-8-rate-your-organizations-sharepoint-collaboration-maturity/ Capability Maturity Model: http://en.wikipedia.org/wiki/Capability_Maturity_Model 1/29/2011 38 Copyright 2011 Sadalit Van Buren
47. Acknowledgements 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. 1/29/2011 Copyright 2011 Sadalit Van Buren 39
Mention data model here.Point out – compliance, regulatory issues, and validation are not included here. Possibly change slide to include a section “what this model does NOT cover” – public-facing, regulatory & compliance, etc.Point out – not every competency has to be at the 500 level – you have to decide where to make the investments based on your business.If anyone has read the Checklist Manifesto – this model needs to be customizable to your business.Link to 1st publication - http://www.endusersharepoint.com/2010/11/05/the-sharepoint-maturity-model-version-1-0/
Write email address on the board!
As we go along – please rank yourself using the sheet that was on your chair!Russ Edelman – “Different maturity levels within an organization are not unusual.”
200 – light switch metaphor.Progression from Information Management to Knowledge Management.=> Mention accessibility issues. (Harbridge 1/29/11)
Not just collab around documents and files but all kinds of collaboration activities – nonlinear included.100 – SPRAWL. Other tools also being used as well as SP. Team site used (which creates problem – hundreds of empty Shared Document libraries)That notion of Progression from Information Management to Knowledge Management comes in here too – often there’s good info buried in collab sites which should be promoted to not only Final but example of work to leverage.Customizations here would be cross-site roll-up, information roll-up / aggregation, custom web parts.
No notes.Background - Workflow typesHuman to system – focus here.Scope – DepartmentCross site / cross departmentEnterprise – spans multiple applicationsExternal user integrationHuman to humanSystem to systemTools- OOB workflow – either true OOB or configured- SP Designer / Nintex-- Custom .NET workflow-- Integration to enterprise WF tool. K2, SkeltaAreas of focus:Auditing – on/off in SPMonitoring – build/buyReporting – oob / custom
No notes.Harbridge mentioned personalized search results on 1/29/11 – e.g. sales team gets sales-oriented results - I would make this 500 level but needs research if it will be added.Background - Search –Scope – OOB/customIntegration / connectors (ifilters) – OOB/customSEO – Y/NDisplay – facets / best bets / rankings / federation (separate or merged) / results – tabular, w/images, etc. / Actionability Integration w/automated taggingVolume – SP / Fast or other 3rd party tool.
No notes.Background:Profiles – maturity progresses through out of box, customization, LOB data, self-service.MysitesTemplate - - OOB / Customized Centralization / organization of mysite and profile (multiple MySites based on domain login etc. – ideal is single.)
Distinction between composites/dashboards – dashboards are read-only; composites are interactive.
Distinction between the two – represented by slash.
Lots to consider here.One audience member (Chris M.) pointed out to me on 1/29/11 – the infrastructure maturity is correlated to the degree that IT uses the system.Background - Infrastructure Server config considerations Farm planning - Availability (redundancy / failover)ScalabilityStorage – archiving/de-provisioningLeveraging low-cost storageBLOB integrationBackup & restoreManaged using OOB toolsDefined using 3rd party or custom toolsMonitoring Updates – manual or automatedVirus checking
Mention notion of Support – it is baked in to all the 500-levels – it doesn’t matter what the support system is, what matters is that users have a way to report a problem or make a suggestion, and that this is tracked and responded to in a timely fashion.Communications, Marketing, and Culture / Change Management not specifically called out here but they are also essential to adoption of the system.
Notion of total cost of ownership – costs $ to build, costs $$$ to maintain & update. Spend more up-front to make the application configurable – so that instead of code drop, change requires update to list, XML, or database table.CustomizationsEnvironment – Prod / Prod + Shared Dev QA / Full 3+ env.Source code – none / simple file storage / source code control system.Build – manual / mixed manual + automated / automatedDeployment & rollback – manual / backup & restore / solution package & scripts / feature creationDeployment – farmwide vs. sandboxed solution (impact on overall farm due to minimized priviliges)Tier – middle (Jquery) vs ? (.NET)
Filling out the self-assessment - for you, as an exercise to see how you’re doing. Like taking one of those “am I an alcoholic” quizzes.