A Practical Guide to SharePoint 2013

A Practical Guide to SharePoint 2013
A Practical Guide to SharePoint 2013 - Book by Saifullah Shafiq

Thursday, November 10, 2011

More Thoughts on SharePoint Custom Development (Via Michael Porter)

Extracted from the original post

Mark Polly recently posted an overview on SharePoint custom development with some interesting views from Forrester about the risks of custom development. While I don’t completely disagree with what Forrester says, I think I’m a little less afraid of custom development than those at Forrester. Here’s what I believe regarding custom development on any platform:

1. When deciding on how to meet user requirements, you should first look at what the tool provides. If it has out of the box functionality then use it. If they have a blog that meets 90% of requirements then use it. You should also explain to the customer the implications of spending time to customize. It’s not bad but you need to prioritize those tasks.

2. If the functionality doesn’t exist, look for third party tools that provide at least 80% of the functionality. Most of the time their cost is cheaper than paying a developer for it.

3. When something else doesn’t exist, and this will happen more often than you hope or even expect, do the custom development.

For complete post click here