Toggle search

Close search

close

Developing and Implementing Your SharePoint 2013 and/or Office 365 Roadmap

Posted by Errin O'Connor on May, 07, 2015 12:05

Developing and Implementing Your SharePoint 2013 and/or Office 365 Roadmap


EPC Group cannot stress enough the importance of addressing mobilityscalabilitycompliance, and governance as soon as possible in your organization’s SharePoint 2013 and/or Office 365 | SharePoint Online initiative.

SharePoint will more than likely grow in content and user requests at a much faster pace than planned. It is critical to have your SharePoint 2013 support model and defined processes in place for managing end-user requests in the early stages of your SharePoint initiative.

Initial Roadmap Questions – Examples of Sample Questions from EPC Group

By thinking in terms of SharePoint as a Service (SPaaS) or SharePoint as a Platform (SPaaP) that will grow in size and importance over time, will help instill the strategy of SharePoint offering “services” to your organization and will open up the hybrid SharePoint implementation mindset. For example, some initial questions for any SharePoint 2013 implementation may start with:

  1. What technologies are the organization currently using?
  2. Are you already utilizing a previous version of Microsoft SharePoint? (Is SharePoint already installed, etc.?)
  3. If SharePoint is not currently utilized, what other technologies or line-of-business (LOB) systems are you trying to move away from in going to SharePoint 2013?
  4. What is the organization’s stance on the cloud and will you possibly be implementing only Office 365 or both SharePoint Server 2013 on-premises as well as Office 365?
  5. What are the initial goals you are trying to accomplish by implementing SharePoint 2013 and what are some other functionality offerings that SharePoint 2013 brings to the table that you may see possibly being utilized in the future?

Note: This question is key because 90% of all SharePoint and/or Office 365 implementations end up being morphing into a hybrid environment to meet multiple organizational needs.

 Is a main goal of SharePoint 2013 and/or Office 365 (SharePoint Online) to be a:

  • Intranet and\or collaboration platform for the organization?
  • Enterprise content management (ECM) \ records management (RM) Platform
  • Collaboration service for departments or team members to work together on to increase productivity?
  • A business intelligence (BI) or reporting service to offer things like dashboards, KPIs, and scorecards?
  • Workflow service or business process automation platform to help take existing paper-based processes and turn them into online forms with specific workflows?
  • An extranet that will allow your company to work more collaboratively with external partners, customers, or other approved audiences?
  • Internet facing SharePoint service to replace your company’s current website
  • Social and\or professional networking platform
  • Central platform to house or host your organization’s existing applications or custom applications?
  • Mobile or “edge device” type service to answer the BYOD questions?
  • Replacement of an existing system like Documentum, LiveLink, eRoom, ApplicationXtender, SAP, FileNet, DocuWare, eDocs, etc.
  • Learning Management Service (LMS) or training platform to reduce travel costs of staff or to provide a central location to increase or streamline organizational training needs?
  • Platform to allow you to migrate your existing network file share content to increase security as well as putting structure around currently unstructured content?
  • Are there AD groups around specific departments or are there also other custom AD and SharePoint security groups that were created to meet cross-functional projects or user security requirements?
  • What is your current virtualization strategy?
  • What type of storage are you utilizing and do you have any metrics around content growth?
  • Do you have more than one data center or possibly globally dispersed data centers or DR sites?
  • Are you currently utilizing or planning to utilize cloud-based or SharePoint online / Office 365 solutions?

– What does your organization’s currently Active Directory (AD) infrastructure look like and how is  it managed?

– What is your current hardware situation and\or strategy?

– What is the organization’s current mobile or BYOD strategy?

– What has worked well in the past to train your organization’s staff?

– Are there content owners or staff members that have been identified as possible SharePoint  Power Users?

– Is the organization looking at the Azure platform or other possible external hosting options like  Amazon Web Services (AWS)?

These are just a few initial questions but this helps set the stage around developing a SharePoint 2013 roadmap and implementation strategy that is forward thinking and addresses possible future needs

In your organization’s initial SharePoint 2013 envisioning and requirements gathering sessions, the goal should be to get as many stakeholders from different departments and/or divisions within the organization as involved as possible in the project so that they understand its overall proposed lifecycle and what may be expected of them.

Inevitably, there will be differing opinions from project team members on things such as the overall site structure, taxonomy, hierarchy, and even the security model around permissions strategies. The SharePoint 2013 and/or Office 365 project will likely be one of the most high profile efforts taking place in the organization and with that there is also the realization that many of the questions that need to answered or tasks that need to be accomplished will be assigned to staff with existing work already scheduled on other efforts and meetings already scheduled on their calendar.

This is an area where setting the initial tone of what is expected from the project team by its key stakeholders or project sponsor is very important. A SharePoint 2013 effort requires many elements to be done in parallel and if certain questions are not being answered or team members are left in limbo about the direction on a specific project task or milestone, it can cause major delays and team member frustrations.

There is also an intangible element around the creation of a SharePoint 2013 cultural adoption and change management strategy as part of the overall project effort that will drastically increase user buy-in on both the initial and long-term usage of SharePoint. Power users, sometimes referred to as super users, tend to not be included in initial SharePoint 2013 design sessions which is a mistake.

Identifying and Teaming Up with SharePoint and/or Office 365 Power Users

Identifying staff members who are excited about technology and are willing to be a SharePoint Power Users will provide a return on investment (ROI) in three or four major areas and the development of a Power User strategy is critical to the long-term success of your SharePoint 2013 and/or Office 365 implementation.

Power Users should be given initial training and SharePoint 2013 introductory materials very early on in a SharePoint initiative. These users may not have extensive I.T. backgrounds but they will be your “first line of defense” for championing SharePoint as well as assisting users in their departments or specified areas by providing answers to initial questions and getting the overall organization comfortable with using this game changing platform.

A best practices Power User strategy will not only will reduce the number of SharePoint support calls or Help Desk tickets by up to 50% but will also provide invaluable feedback as well as ideas about “quick wins” that I.T. may not have even considered.

From the very beginning of a SharePoint 2013 initiative, a large amount of SharePoint specific technical terms will be used and with the wide array of team members from different departments attending specific meetings, so setting up a SharePoint 2013 introductory training site is extremely valuable. Having a video library available for project members to access with short one to five minute topic-driven SharePoint 2013 videos and as well as a “common set of SharePoint 2013 terms” will ensure every project member is on the same page.

SharePoint training sites, frequently asked questions (FAQs), and related materials are typically designed and delivered near the end of a SharePoint project before going live into production, but a scaled down version of these with some core technical overview videos and documents, as described above, should be made available as soon as possible in your initiative.

Your project meetings and discussions with team members will be much more productive with a reference or specific example of what you are describing in terms of SharePoint 2013 rather than speaking in terms of an abstract technology. This is something that is guaranteed to kick-start your project and get some real momentum going very early on in your initiative.

EPC Group’s SharePoint 2013 & Office 365 Roadmap and Implementation Strategies “From the Consulting Trenches”

EPC Group will continue our blog posts on SharePoint 2013 & Office 365 Roadmap and Implementation Strategy development in the days and weeks to come to touch on the real-world “from the consulting trenches” approach that EPC Group has successfully implemented for hundreds of organizations throughout North America.

These strategies are also detailed in EPC Group’s latest publications, “SharePoint 2013 Field Guide: Advice From the Consulting Trenches