Now that you know what SharePoint is, what it does, and what it needs, it's time to consider how to implement it successfully. Plans for SharePoint go awry when the implementer designs based on what it can do, and wraps what the customer will get based on what the technology does. That is a recipe for failure. To plan for a successful SharePoint implementation—it starts with the customer. What do they do? What do they need?
- [Instructor] In order to have a plan concerning…implementing a SharePoint deployment,…you need to know what the organization requires…from SharePoint.…When planning for SharePoint, there are some points…to keep in mind.…Some organizations simply don't need SharePoint.…They'll ask for it.…They'll bring you in to give them information about it…and design an implementation for them.…If during the interview process,…you discover that they do not need SharePoint,…that's the time to stop.…Most organizations do not need everything…that SharePoint can do.…The members of the organization are not the ones who need…to know what SharePoint can do and they don't know the names…of features and services that SharePoint offers.…
They only know the business functions that they require.…We are the ones that are supposed to map those requirements…to what SharePoint can do.…In other words, do not plan SharePoint…so that the business can use those features,…instead look at what the business requires…and enable only the features that they require.…
- What is SharePoint?
- Establishing SharePoint hardware and software requirements
- Collecting user and business requirements
- Designing the SharePoint architecture
- Planning for governance