Successful SharePoint implementations are less about the technology and more about the business functions that are delivered to the end users
Background I am writing this article (Article 1 of 4) as myself and my organization, EPC Group.net , has embarked on and completed our 653 successful SharePoint implementation. In the sections below, I am going to dissect how an Enterprise or Global SharePoint implementation project can become a success 99% of the time
1 Comment - no search term matches found in comments.
#SharePoint #implementation
I included it in the title of my presentation and Microsoft wanted me to change it because they thought it suggested that a SharePoint implementation could be chaotic
In the SMB market it's still hard to find a company that's pleased with their SharePoint implementation
I’d suggest that “work” is defined by resolving the problems outlined in the business requirements for the SharePoint implementation
However, applying this model to a SharePoint implementation that addresses dozens of business needs with dozens of capabilities and features is just not as easy as it looks
SharePoint branding and custom web parts are common development activities for almost every SharePoint implementation
In my last post, I emphasized the requirements development and planning activities that should precede a SharePoint implementation