SharePoint Reviews

• Visual web parts
• Document libraries
• FBA
• Document templates

It simplifies development of portal and document management. Also, by using Office 365, we got good integration with office tools.

When we develop portals, we need to develop a lot of web parts that eventually go to a number of pages. These pages must be created manually. There should be some easy way to develop pages automatically via programing.

I am working on SharePoint since 2011. I have worked (with my team) on Microsoft SharePoint 2010 and 2013. We have developed enterprise web portals of government entities and large private organizations.

We have not had any stability issues.

Actually, the scaling is very simple. One of my customers needs their portal in three languages (English, Arabic and Urdu). SharePoint doesn’t have the Urdu language package, hence we had to work hard for it.

Most of time we got support from forum and that is good enough.

We did not use a previous solution.

Setup was simple.

I recommend using Office 365.

We did not look at other solutions.

if you have a .NET team, the SharePoint is right solution for you.

Meeting workspaces, version history, bulk tagging.

It has helped us collapse all our versions into a single file. It has also improved our meetings.

Setting up permissions can be overwhelming. If this can be improved it would be great. Also Sharepoint search out-of-the-box needs improvement.

Five years. Started out with Sharepoint 2007.

Most issues are from the change management part.

The solution appeared unstable at deployment but it's been more stable since then.

We implemented through a vendor team.

Used as a site for staff to add records. It is integrated with RecordPoint in the back-end, so the staff did not have to work within an EDRMS.

SharePoint enabled the staff to share documents and work on a document simultaneously. Our staff found it simpler, as they did not have to work within a classification system (it was all done in the background).

Sharing of information is much easier within an organisation and staff training is reduced because learning basic SharePoint is not as complicated as an EDRMS.

Integration with Outlook would be a major improvement. Staff also commented that it does not integrate despite being part of the Microsoft family.

Less than one year.

I have used SharePoint as an integrated solution with Team Foundation Server.

The most valuable features are the SharePoint lists and the documents feature.

SharePoint integrates well with the Team Foundation Server and provides collaboration features for team members on a TFS Team Project. This has helped developers and project stakeholders in the organization to collaborate better and share information in the form of documents/updates.

Migrating SharePoint sites can be a cumbersome process and it usually results in the incomplete migration of SharePoint sites and data.

I have used SharePoint for three years, mostly as an integrated solution with the Team Foundation Server.

The product is quite stable.

The product is scalable.

We were not using any other solution.

The setup and installation are straightforward. Microsoft provides a good installation wizard for the same.

I was not involved in the pricing and licensing activities.

As both the Team Foundation Server and SharePoint are Microsoft products, they can be easily integrated. Thus, we did not evaluate other options.

SharePoint works very well within a Microsoft ecosystem. Hence, SharePoint would be a good choice if the organization uses the Microsoft technology stack extensively.

The valuable features are:

• MS-Office integration
• Workflow and approval process
• Security

We use this solution as central repository for all the corporate information systems. It is a point of reference in our organization.

Administration is still very complex.

We have been using this solution since 2005.

I did not encounter any issues with stability.

I did not encounter any issues with scalability, although our installation is a small one and doesn't have that problem.

The solution is a strategic product for Microsoft, and the technical support is very good.

Prior to this solution, we used shared files provided by the operating system.

The installation was very complex. Since our initial implementation, that process has been improved dramatically.

We considered open source products like Alfresco. We decided to purchase a commercially supported product.

It is a complex product that should be implemented carefully. Take into account the organization’s details.

Feedback workflows ensure we don't miss someone when documents need reviewing and approval workflows make sure the right people are approving it, especially when there are new or temporary staff involved. They don't have to ask who is next in line. They just pick the appropriate workflow and it's all sorted.

We automated task workflows for document review and gathering feedback.

No additional features are needed at the moment, except bringing some of the alerting functionality from the on-premise to the online version.

I have used this for four years.

We did not have any stability problems.

We did not have any scalability problems.

We were using SharePoint 2007. We changed due to the product lifecycle.

Setup was complex. We needed to design governance and implementation architecture before deployment.

Get help. Pricing and licensing is tricky.

We didn’t look at any alternatives.

Consider SharePoint Online unless you have customisations. If you have customisations, try and get rid of them. They cause problems when upgrading.

Valuable features in this product are:

• Easy customization with MS .NET and related tools
• Stability
• Performance in a medium size environment (100-200 users)
• Full support by MS

We implemented custom approval workflows (for approving Opex items) using Windows Workflow Foundation which simplified and helped in speeding up the process of approving HW and SW licenses.

Performance: The web page was sometimes not as fast as we'd like to see.

Application of custom CSS/visual styles was cumbersome and usually required a complete re-write of out-of-the box SharePoint site pages.

I have used this product for three years.

Stability was usually good.

I have not encountered any scalability issues.

It's standard MS-quality support. We got the help level we expected as an MS Gold partner.

Previously, we used custom ASP.NET application. We wanted to use SharePoint because it is easy to deploy in a new environment and has out-of-the box functionalities like AD authentication, file versioning, wiki pages, .NET extensible, etc.

The installation of SharePoint server was easy and had no issues.

I cannot make any specific recommendations.

SharePoint didn't have a direct competition at the time of our evaluation, mainly due to its deep integration with .NET Framework technologies like Windows Workflow Foundation. Thus, it was our only choice to try.

Consider what level of SharePoint Web customization you are looking for. If you would be okay with some basic color changes, adding your logo and other small visual changes, it would be easy for you to build what you want. However, if you are looking to build a custom look and feel website and consider using SharePoint, you will end up building a completely new product using some SharePoint components that may lead into technology/customization limitations.

We use it for collaboration and document management in the process of developing proposal responses.

SharePoint has made it easier to collaborate across the company during the process of developing proposals.

• The collaboration is incredibly helpful. 
• The ability to have version control and co-editing is vital to our workflows.

SharePoint sometimes cannot handle the amount of co-editing that we do. Of course, this could be the user, not the tool.

Three to five years.