Salem Ucisa Published


Published on

Slides from my reccent keynote at the UCISA SharePoint conference for Higher Education

1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • The wisdom of collective experience
  • Salem Ucisa Published

    1. 1. The Anatomy of a SharePoint Strategy<br />Ian McNeice<br />The Salem Consulting Group<br />
    2. 2. Anatomy, SharePoint & Strategy ?<br />Anatomy, a word meaning to cut up, or cut open<br />SharePoint is the appliance of comprehensive technology services to meet a wide range of business information requirements<br />Strategy, a word of military origin, refers to a plan of action designed to achieve a particular goal or goals.<br />
    3. 3. AIIM Report 2010<br />In the summer of 2010, AIIM released a report on their findings regarding the current state of play in terms of their client’s approach to SharePoint. <br />The survey was taken by 624 individual members of the AIIM community between May 6th and June 5th, 2010<br />(Source: AIIM Industry Watch report, “State of the ECM Industry 2010” available for free download at<br />
    4. 4. AIIM Health Check<br />A third of implementing organizations have NO plans as to where and where not to use SharePoint, suggesting a lack of management direction.<br />26% reported that the IT department is driving the project with NO input from information management professionals.<br />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.<br />
    5. 5. AIIM Health Check<br />SharePoint is no passing fad. It is in use in a majority of organizations and is being rapidly rolled out for universal employee access. (500% market growth between November 2010 and April 2011)<br />Two-thirds of SharePoint users have existing ECM, DM or RM suites. For many, there is considerable confusion regarding their future strategy for using and integrating SharePoint.<br />
    6. 6. AIIM Health Check<br />The deployment experience suggests that SharePoint must be considered as an enterprise-wide project. It therefore requires a sufficient degree of planning, training and policy setting to ensure infrastructure integration, metadata standardization and above all, employee acceptance.<br />Third-party additions have a strong role to play in extending and reinforcing SharePoint functionality, and building a rich and robust ECM capability.<br />
    7. 7. AIIM Health Check<br />Most SharePoint deployments are 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.<br />Even if it starts out small, SharePoint is likely to turn into an enterprise programme. Plan accordingly.<br />
    8. 8. AIIM Autopsy<br />“49% of all SharePoint clients have no SharePoint strategy”<br />
    9. 9. The Anatomy – dissected<br />Executive Sponsorship<br />An Institution-aligned Roadmap<br />Institution-aligned Prioritization<br />The Requirements to Scale<br />Timeline Expectations<br />Programmatic Design and Planning<br />Budgeting<br />Resourcing and Skills<br />Adoption Strategy<br />Success Criteria and Metrics<br />Governance and Policy<br />The End Game<br />Technology Considerations<br />
    10. 10. Executive Sponsorship<br />SharePoint requires business leadership & direction<br />SharePoint requires continuity<br />SharePoint requires time, budget, dedication and institutional business alignment<br />SharePoint requires a wide range of business skills<br />SharePoint requires adoption to be driven top down<br />SharePoint requires governance and policy to drive adoption<br />SharePoint will change the way the institution presents and processes its information<br />SharePoint may create ‘turf wars’<br />
    11. 11. Institution-aligned Roadmap<br />Be clear on the key institutional priorities this year and next year and the year after<br />Find out what the institution desires to do better<br />Discover what services are currently simply not provided at all or are adjudged currently ineffective<br />Define a SharePoint service roadmap based on institutional objectives<br />Define who will ‘own’ the programme<br />Define how the programme will be paid for and by whom<br />
    12. 12. Yes But My Institution Doesn’t Know What it Wants <br />From a business perspective yes it does but the thinking may not yet be joined up<br />We can present a SharePoint roadmap and then adapt it year on year<br />We can join up the thinking for the institution using a business-aligned roadmap<br />We can then match the institutional priorities to sequential service delivery<br />We can influence sponsorship & adoption by aligning the roadmap with the institutional strategy<br />We can create a process for agile service delivery<br />We can formalise the approach underpinned by institutional and IT governance<br />We can use an adoption strategy to underpin effective training<br />
    13. 13. Institution-aligned Prioritization<br />SharePoint Service delivery should match specific business priorities and underpin them<br />Logic should be applied to which services are delivered in parallel and in sequence<br />A clear roadmap should be communicated via awareness sessions to allow the business to understand what comes next<br />An ad hoc request system will be required to facilitate creative requests<br />Priorities will change and the ability to re-budget may be required<br />IT and business priorities sometimes conflict<br />
    14. 14. The Requirements to Scale<br />A planned service release mechanism caters for scale<br />Organic growth cannot cater for scale<br />One service delivered in isolation may hinder another future service<br />Early technology decisions must be made to enable growth<br />The design decisions of one service will impact other services and should be anticipated<br />Agility of service provisioning creates growth & underpins adoption<br />Devolution of administration is a key factor for growth<br />Platform design must be made with scale in mind<br />Your staff WILL become creative with SharePoint<br />
    15. 15. TimelineExpectations<br />Be realistic and pragmatic – the impact of the academic year will take precedence<br />Governance and policy definition takes time<br />End user adoption takes time<br />End user training takes time<br />Technical training takes time<br />A programme runs over years not months<br />Break each year into logical and sequential deliverables as projects<br />Define a three year logical map from the outset<br />Run an awareness campaign from the outset<br />Set realistic expectations from the outset<br />
    16. 16. Programme Design and Planning<br />SharePoint should be approached as a unified business programme not an IT project<br />The primary purpose of SharePoint should be to solve successive institutional business information problems<br />A SharePoint programme:<br />unifies information and collaborative working techniques and info sources gradually<br />builds layer upon layer of rich services following a progressive path<br />defines clear budget requirements over multiple years<br />defines resourcing requirements well in advance<br />requires specific knowledge and skills<br />sweats the IT assets and provides far greater return on investment <br />
    17. 17. Strategic Budgeting<br />You cannot budget for the unknown but you can anticipate by using a business-aligned roadmap<br />Early technology decisions will affect budgeting later in the cycle<br />Do not budget for SharePoint until a defined business-aligned strategy has been agreed<br />You must budget for adoption and training to be successful<br />Effective budgeting requires executive sponsorship<br />Skilled resources cost money<br />Adoption and training must be budgeted for<br />Budget on a service by service basis as part of the roadmap<br />
    18. 18. Budgeting and Ui<br />
    19. 19. Resourcing and Skill Requirements<br />There are at least 15 technical skilled roles in SharePoint, not three (e.g. architect, administrator, developer)<br />One single person cannot perform all SharePoint skilled roles effectively<br />Developers are not an early SharePoint requirement in most instances<br />Understand the range of institutional roles required well in advance and plan for them<br />The vast majority of resources required are not IT-based (communication, early adopters etc.)<br />Plan for the wide range of roles you will need to resource<br />Skilled resources are in high demand<br />
    20. 20. Governance and Policy<br />Clear governance and policy leads to effective SharePoint adoption and training<br />If a user doesn’t know the rules of engagement they will not adopt the technology<br />Establish an institutionally-representative governance board from day one to define policy<br />IT governance compliments business governance<br />Governance will be required throughout the entire programme lifecycle – plan for the impact on business time<br />
    21. 21. Success Criteria<br />You will need a method of defining success<br />You will need a method of quantifying success<br />By proving success you will be able to budget more effectively<br />Many aspects of collaborative success are difficult to quantify<br />The success criteria should be defined by a steering committee<br />Success in adoption is as much a business issue as an IT issue<br />
    22. 22. The End Game<br />Meet institutional objectives progressively<br />Meet institutional priorities timely<br />Meet institutional requirements methodically<br />User SharePoint to be a business service facilitator easily<br />Drive down the cost of IT efficiently<br />Increase and enhance IT services dramatically<br />Integrate and enhance access to information effectively<br />Unify information through a single window cohesively<br />Reduce eclectic and expensive IT skills pragmatically<br />Drive your institution forward successfully<br />
    23. 23. Technology Considerations<br />A medium server farm catering for up to 30,000 users is already clearly defined by Microsoft<br />To build and configure a SharePoint environment requires explicit expertise<br />It takes time to learn to administer SharePoint effectively – use an expert Microsoft Partner for cross skilling<br />Deliver out of the box services long before taking a development route (if at all)<br />Commodity application solutions are readily available for many business scenarios<br />Define your IT governance and policy framework from the outset<br />Do NOT treat SharePoint like any other application<br />Employ a SharePoint Project Manager from the outset<br />Organic growth has been proven not to work<br />
    24. 24. An Ideal World ?<br />No it’s the reality. Salem is contacted by companies every week who have hit a brick wall with SharePoint after attempting to deliver and scale with no sponsorship, no business alignment, no strategy, no roadmap or who took the DIY approach and failed to gain business adoption and sponsorship.<br />
    25. 25. The Surgeon’s Notes<br />Many IT-driven SharePoint projects fail as they are not aligned with business objectives – seen as technology for technology sake<br />Business-driven SharePoint programmes have a high success rate<br />Technology exists primarily to service business requirements. Define those requirements in advance<br />SharePoint programmes require planning and reliable budgets in place from the start<br />A business service delivery plan drives governance <br />Governance drives effective policy<br />Policy drives effective adoption<br />Adoption drives effective training<br />Training drives effective administration<br />…Most of the thinking has already been done<br />
    26. 26. The Anatomy of a SharePoint Strategy – complete<br />Executive Sponsorship<br />An Institution-aligned Roadmap<br />Institution-aligned Prioritization<br />The Requirements to Scale<br />Timeline Expectations<br />Programmatic Design and Planning<br />Budgeting<br />Resourcing and Skills<br />Adoption Strategy<br />Success Criteria and Metrics<br />Governance and Policy<br />The End Game<br />Technology Considerations<br />
    27. 27. A Final Thought on SharePoint Strategy<br />“Always begin with the end in mind”<br />
    28. 28. Contact Salem<br /><br /><br /><br />Email:<br />Tel: 0207 788 9445<br />London, United Kingdom<br />