INTRODUCTION

In this opportunity I would like to share with you on why Sharepoint development projects failed. This will be based purely on my knowledge and experience therefore I would love to hear your comments and sharings, too.

TARGET AUDIENCE

The target audience of this series are developers, BDMs and project managers.

WHY FAILED 1: INADEQUATE KNOWLEDGE ON SHAREPOINT

The first reason why Sharepoint projects failed is because of inadequate knowledge on Sharepoint. When I say "failed" it means that the project either doesn't meet client requirements at all or it does meet client requirements but then it's gone over budget and over the given deadlines and time frames.

A lot of project managers, BDMs and sales people are offering Sharepoint to clients simply because they buy into the hype. Just because Microsoft says that Sharepoint can do this and that (be it document management, internet or intranet applications) it doesn't mean that you have to use it as a solution. A lot of people just haven't realised how complicated Sharepoint is - or I should restructure the words better - a lot of people don't realise what it takes to customise Sharepoint yet they have started to offer it to clients. At the end of the day the project either goes over budget or meeting a brick wall (ie. can't find an easy way out to find a solution for particular client requirements) or it doesn't meet the client expectations at all.

I've tried to build my own custom solution on top of Windows Sharepoint Services 3.0 called CompleteSharepoint.NET and it's a simple web content management system as a replacement of MOSS. Since I developed it, I get to understand Sharepoint more and more and now I know what it takes to customise Sharepoint. Yes, it's a development platform more than just a product, yes you can build custom applications on top of it but you also need to know what it takes to make it happen.

When Sharepoint project failed people then blame it for its complexity. I never know such thing is complicated if you have a solid understanding on what it does and I feel sorry for Sharepoint (and Microsoft) because they get blamed so many times yet it's not their fault. Every product has its own advantages and disadvantages, strengths and weaknesses. Sharepoint is also the same, you will only benefit from it if you can maximise the strengths and cope with the weaknesses.

My personal recommendation is (before you even select Sharepoint as a solution offering), get to know the product first. Make sure you've consulted with a Sharepoint expert and make sure that what you want can be achieved with Sharepoint. For example, a BDM may have a lot of experience in document management system. He of course knows what DMS system should have (ie. the features). He should then consult to a Sharepoint expert whether these features either come out-of-the-box with Sharepoint or can be developed on top of easily.

When you have a quiet solid understanding of how Sharepoint works and what the features are, you can then be more comfortable offering it to clients. I always like this phrase, "It's better not to start anything rather than starting something and not finishing it well". A good leader is someone who finish what he has started and he finishes it well.

CONCLUSION

A good salesman will know his product. I can't tell you how good Carbonara Pasta is if I never try it myself. I can't tell clients how good Sharepoint is if I don't even have an adequate knowledge of what it does and what it can do.