SharePoint in all its flavors and variations can be implemented in any number of ways - each approach with its own business requirements, staffing needs, challenges and idiosyncrasies. So where do you start? What does your organization's SharePoint roadmap look like? What staff and skills do you need to get started? In this session we'll identify some of the more common implementation scenarios and how core skills and requirements align with them. Â Â
The topics in this session can be applied to most versions of SharePoint on premises, hosted or ‘in the cloud’ – though my examples will most likely talk about 2010. SharePoint Governance – a term that has extremely popular the last few years, to the point of losing some of it’s value. When we started hearing about governance, we were talking about planning and operational responsibilities. The first implementations of ‘governance plans’ were overthought, over documented plans that seldom were followed of kept up to date. Crawl, Walk, and Run – an approach used in many SharePoint (and other) implementations to get work out more quickly and more successfully. Think big, but start small.
What kinds of roles are represented in the room? Are you Devs? Business folks? IT Pros? What kinds of implementations do you have? 2007? 2010?
Who remembers the original ‘Choose your own adventure’ books? Good, I can use card catalogues as an illustration for Search indexing as well…This is the idea behind our conversation today – the path you go depends on the choices you make along the way.The next iteration of this deck will be more interactive – similar to the book concepts
It was difficult to put this topic together – what I wanted to communicate and have you take away
But hold on a minute – we’re already jumping to technical solutions (even if at a high level…)Any of these high level topics could have lots of variations within them.
If your needs don’t mesh with what SharePoint has to offer or there is no gap to fill, you might not need SharePoint In addition to ‘governance’, ‘user adoption’ is another SharePoint buzzword. If more organizations understood their users’ needs and were able to align the needs with organizational priorities effectively, SharePoint solution deployments wouldn’t need to worry about user adoption. Users would be clamoring for their solutions to be built and jump on board. Gathering requirements is a session or more in itself and something we’re not going to go into detail on todayIf you’re not starting from scratch with SharePoint or other platforms that overlap in functionality, where you start may vary.Ex. If there is an existing Document Management system, you’ll likely spend time on integration and less on content mgmt in SharePointIf SharePoint is new – or there is the possibility of bringing on additional farms/environments, the decision/approach needs to be determined as to whether they will be built with internal servers, on a hosted environment or even a ‘cloud’ solution like Office 365/SharePoint OnlineThere are pros and cons to each of these scenarios with a hybrid approach also an option.Licensing: Foundation (free), Standard, Enterprise, SP Online…Governance: Who will be responsible for the platform and governing policy decisions…All the other IT stuff:HardwareVirtualizationOperations and ManagementDisaster RecoveryMonitoringEtc.
Just a quick review of terms and definitions. Do you know what these mean?There are likely more in your organization – some will likely play multiple roles.
Prioritizing identified needsAvailable resource and time managementAvailable hardware, storage, etc.Crawl, Walk, Run: You can get initial functionality out more quickly and then re-visit that area later to make it deeper and richer functionality. Sometimes just getting something out there for users (or mgmt) will satisfy needs enough to move to the next thing for a while.
You don’t have to have timelines and details for each implementation phase/piece. Project management should be looking out a ways and know when to start ramping up planning on upcoming phases.
Single site collection – easier for rollupsSeparate site collections – larger capacity and better data management
It was difficult to put this topic together – what I wanted to communicate and have you take away