subject: Sharepoint Consultants Pinpoint 5 Aspects To Be Avoided In Creating Sharepoint Intranet [print this page] Sharepoint consultants are aware that SharePoint is an apt platform for an enterprise since it covers a bit of everything such as workflows, document management, social features, basic task management, calendars etc. Hence, at times it can become difficult to understand which parts of sharepoint application development should one use. At times intranet based projects on sharepoint application development can turn into large scale projects thereby confusing the end user. Hence, it is important that Sharepoint consultants point out to organizations what are the five aspects they would need to avoid in order to ensure the Intranet based SharePoint application development is being understood and used properly by everyone.
Sharepoint consultants point out a couple of aspects that one needs to be careful about:
Workflows:
A number of Intranet projects try and use Sharepoint application development workflows. Some even try and add platforms that help build powerful workflows. However, most Sharepoint consultants advise that workflows should be avoided simply because it is difficult to get right all the time. The intranet project will definitely not be successful if a workflow is not thought out in a proper manner. Instead, to ensure successful sharepoint application development, it is a good idea to keep the Intranet simple and stick to the basic features.
Create InfoPath forms:
InfoPath is quite like a workflow and is in fact quite a complex tool. But usually most people think that any kind of business can go online and what they get in return are difficult to understand forms and its not at all easy to fill them up. Sharepoint consultants point out that it is definitely not a benefit if an Intranet is launched, which includes substandard functionality. Instead of trying InfoPath, it is much better to keep the forms in Word document format while making sure that the masters are stored on the Intranet. It is better to keep things simple at the beginning so that people can get used to the system.
Creating a customized graphic design:
With SharePoint 2010, most Sharepoint consultants advise not to touch the user interface and unnecessarily waste time. It is definitely not worth it waste time on trying to match website or corporate branding with Sharepoint Intranet. Instead it is worthwhile to spend time and effort on functionality, training etc. What is a good idea is to add the logo on the Sharepoint application development master page and create themes through color palette.
Replacing fileshares:
As part of Sharepoint development, Sharepoint consultants advise that even though Sharepoint is perfect at document management, it is not a good idea to migrate all documents to the SharePoint Intranet and thereby remove or delete the existing fileshares. What can be done is to make fileshares read only so that it will not be possible for anyone to add or change anything. Users will be able to upload new files and still be assured that the old files also exist in a secure location.
Its not the end:
Most sharepoint consultants pinpoint that things dont end with Sharepoint Intranet being launched. In fact the real test starts here because the users have to be encouraged to use SharePoint Intranet.
