Now you are probably thinking where your first SharePoint project can be deployed. This section has some questions that you should be asking.
A: There's a learning curve in understanding the SharePoint Framework, knowing how to deploy solutions, and managing users' expectations.
A: This depends and this question is addressed in Chapter 1, Defining a SharePoint IT Strategy.
Tip
A good tip is to avoid the sales department or any business unit that is very busy and does not have the time to provide requirements, or be trained. Sales folks can be classified into this group. They are rarely in the office, often resistant to technology change if it requires an investment of their immediate time, and when they are vocal that sales targets are being jeopardized because of time spent on a SharePoint project, continued management support can be unlikely.
This could be the same in any department.
Another challenge that you should consider is working with a user base that works in the building so water-cooler talk is possible. Yes, this informed dialogue to understand what is going on is huge.
A: If you have started a project with OOB features of SharePoint, communicate to the business unit that this is the approach at the start of the project, so expectations are leveled. Explain the pros and cons of this approach:
- Pros: Costs less to develop because we are leveraging the SharePoint technology, quicker delivery of the solution
- Cons: We are working with a template (SharePoint) and there are going to be limits
If requirements do change, particularly during the last 10 percent of the project, try to make these requirements a phase-two activity, so the project is not delayed and the value of the technology is deployed to the business.