The Anatomy of a SharePoint Strategy

Transcription

1 The Anatomy of a SharePoint Strategy Ian McNeice, Director at Morgan & Wolfe Co-Author of SALEM for SharePoint

2 Anatomy, SharePoint & Strategy? Anatomy, a word meaning to cut up, or cut open SharePoint is the appliance of comprehensive technology services to meet a wide range of business information requirements Strategy, a word of military origin, refers to a plan of action designed to achieve a particular goal or goals.

3 Historical Health Chart During 2010, AIIM released a report on their findings regarding the current state of play in terms of their client s approach to SharePoint. The survey was taken by 624 individual members of the AIIM community between May 6th and June 5th, 2010 (Source: AIIM Industry Watch report, State of the ECM Industry 2010 available for free download at

4 Surgeon s Health Check A third of implementing organizations have NO plans as to where and where not to use SharePoint, suggesting a lack of management direction. 26% reported that the IT department is driving the project with NO input from information management professionals. 50% of SharePoint implementations went ahead with NO business case being made to justify the investment. Only 23% were required to make a financial justification.

5 Surgeon s Health Check SharePoint is no passing fad. (500% market growth between November 2010 and April 2011 and 500% annual growth in SharePoint Online to 2014) statistics demonstrate over 75% of major corporations rely on SharePoint and over 75% of Fortune 500 organisations use SharePoint. Two-thirds of SharePoint users have existing ECM, DM or RM suites. For many organisations, there is considerable confusion regarding their future strategy for using and integrating SharePoint.

6 Surgeon s Health Check Longer-term deployment history demonstrates that SharePoint must be considered as an enterprise-wide program. It therefore requires a sufficient degree of planning, training and policy setting to ensure infrastructure integration, metadata standardization and above all, employee acceptance. Third-party additions have a strong role to play in extending and reinforcing healthy SharePoint functionality, and building a rich and robust ECM capability.

7 Surgeon s Health Check Most SharePoint deployments are still being driven by IT or devolved to individual departments. As a result, traditional information governance and compliance issues are largely being ignored. This is likely to replicate the content chaos of the file share inside of SharePoint, and it will hamper efforts to improve legal discovery and long-term records management. Even if it starts out small, SharePoint is likely to turn into an enterprise programme. Plan accordingly.

8 SharePoint Autopsy Summary Today around 50% of all organisations trying to use SharePoint have no demonstrable SharePoint strategy Forrester, Gartner, Ovum and many other independent bodies report that organisations continue to fail to gain business adoption with SharePoint in 2014 due to a lack of strategy. Between 2010 and 2014 the number of organisations with a lack of business strategy for SharePoint has actually increased.

9 The Anatomy Dissected 1. Executive Sponsorship 2. A Service-Line Roadmap 3. Organisation-aligned Prioritization 4. The Requirements to Scale 5. Timeline Expectations 6. Programmatic Design and Planning 7. Budgeting 8. Resourcing and Skills 9. Adoption Strategy 10. Success Criteria & Metrics 11. Governance and Policy 12. The End Game Fit for Purpose 13. Technology Considerations

10 1: Executive Sponsorship SharePoint requires business leadership & direction SharePoint requires continuity SharePoint requires time, budget, dedication and organisational business alignment SharePoint requires a wide range of business skills SharePoint requires adoption to be driven top down SharePoint requires governance and policy to drive adoption SharePoint will change the way the organisation presents and processes its information SharePoint may create executive turf wars

11 2: Service-Line Roadmap Be clear on the key organisational priorities this year, next year and then the year after Find out what the organisation desires or needs to do or do better Discover what services are currently simply not provided at all or are adjudged currently ineffective Define a SharePoint service roadmap based on organisational objectives Define who will own the programme Define how the programme will be paid for and by whom

12 My Organisation Doesn t Know What it Needs to be Fit for Purpose From a business perspective yes it does but the thinking may not yet be joined up We must present a SharePoint service-line roadmap and then evolve it annually We must join up the thinking for the organisation using a businessorientated roadmap We can then match the organisational priorities to sequential service delivery We can influence sponsorship & adoption by aligning the roadmap with the organisational strategy We can create a process for agile service delivery We can formalise the approach underpinned by organisational and IT governance We can use an adoption strategy to underpin effective training

13 The Medicine: Apply The Business Service Framework

14 3: Organisation-Aligned Prioritization SharePoint Service delivery should match specific business priorities and underpin them Logic should be applied to which services are delivered in parallel and in sequence A clear roadmap should be communicated via awareness sessions to allow the business to understand what comes next An ad hoc request system will be required to facilitate creative requests Priorities will change and the ability to re-budget may be required IT and business priorities can sometimes conflict

16 4: The Requirements to Scale A planned service release mechanism caters for scale Organic growth cannot cater for scale One service delivered in isolation may hinder another future service Early technology decisions must be made to enable growth The design decisions of one service will impact other services and should be anticipated Agility of service provisioning creates growth & underpins adoption Devolution of administration is a key factor for growth Platform design must be made with scale in mind Your staff WILL become creative with SharePoint

17 6: Programme Design and Planning SharePoint should be approached as a unified business programme not an IT project The primary purpose of SharePoint should be to solve successive organisational business information problems A SharePoint programme: Unifies information and collaborative working techniques and info sources gradually Builds layer upon layer of rich services following a progressive path Defines clear budget requirements over multiple years Defines resourcing requirements well in advance Requires specific knowledge and skills Sweats the IT assets but provides far greater return on investment when business-driven

18 7: Strategic Budgeting You cannot budget for the unknown but you can anticipate by using a business-aligned roadmap Early technology decisions will affect budgeting later in the cycle Do not budget for SharePoint until a defined business-aligned strategy has been agreed You must budget for adoption and training to be successful Effective budgeting requires executive sponsorship Skilled resources cost money Adoption and training must be budgeted for Budget on a service by service basis as part of the roadmap

20 8: Resourcing and Skill Requirements There are at least 16 technical skilled roles in SharePoint, not three (i.e. architect, administrator, developer) One single person cannot perform all SharePoint skilled roles effectively Developers are not an early SharePoint requirement in most instances Understand the range of organisational roles required well in advance and plan for them The vast majority of resources required are not IT-based (communication, early adopters etc.) Plan for the wide range of roles you will need to resource Skilled resources are in high demand

21 9: Adoption Strategy Strategy Types Methods Timeline Audiences Plan Costs

22 10: Governance and Policy Clear governance and policy leads to effective SharePoint adoption and training If a user doesn t know the rules of engagement they will not adopt the technology Establish an organisationally-representative governance board from day one to define policy IT governance compliments business governance Governance will be required throughout the entire programme lifecycle plan for the impact on business time

23 11: Success Criteria & Metrics You will need a method of defining success You will need a method of quantifying success By proving success you will be able to budget more effectively Many aspects of collaborative success are difficult to quantify The success criteria should be defined by a steering committee Success in adoption is as much a business issue as an IT issue

24 12: The End Game Fit for Purpose Meet organisational objectives progressively Meet organisational priorities timely Meet organisational requirements methodically User SharePoint to be a business service facilitator easily Drive down the cost of IT efficiently Increase and enhance IT services dramatically Integrate and enhance access to information effectively Unify information through a single window cohesively Reduce eclectic and expensive IT skills pragmatically Drive your organisation forward successfully

25 13: Technology Considerations SharePoint architecture and infrastructure best practices are already clearly defined by Microsoft To build and configure a SharePoint environment requires explicit expertise It takes time to learn to administer SharePoint effectively use an expert Microsoft Partner for cross skilling Deliver out of the box services long before taking a development route Commodity application solutions are readily available for many business scenarios Define your IT governance and policy framework from the outset Do NOT treat SharePoint like any other application Employ a SharePoint Project Manager from the outset Organic growth has been proven not to work

26 Is this Really the Picture of Your Technological Health Today?

27 Wouldn t You Rather Feel Like You ve Got it Together Tomorrow?

28 The Surgeon s Notes Many IT-driven SharePoint projects fail as they are not aligned with business objectives seen as technology for technology sake Business-driven SharePoint programmes have a high success rate Technology exists primarily to service business requirements. Define those requirements in advance SharePoint programmes require planning and reliable budgets in place from the start A business service delivery plan drives governance Governance drives effective policy Policy drives effective adoption Adoption drives effective training Training drives effective administration Most of the thinking has already been done so why start with a blank sheet of paper?

29 The Anatomy of a SharePoint Strategy Health Check Summary Executive Sponsorship An organisation-aligned Roadmap Organisation-aligned Prioritization Service-Line The Requirements to Scale Timeline Expectations Programmatic Design and Planning Realistic Budgeting Resourcing and Skills Adoption Strategy Success Criteria and Metrics Governance and Policy The End Game Technology Considerations

30 The General Rule to Stay Healthy & Fit with SharePoint Always begin with the end in mind. Call: (UK)