|
|
此文章由 iceman 原创或转贴，不代表本站立场和观点，版权归 oursteps.com.au 和作者 iceman 所有！转贴必须注明作者、出处和本声明，并保持内容完整
Sharepoint
You tend to see it everywhere (at least in Denmark where I live), it is massively expensive to install and maintain.
But so far, I have not seen a single solution created in Sharepoint that has been a benefit to the users.
Oh, and it is buggy as hell.
Edit: When I first wrote this, I had difficult putting into writing why is Sharepoint not benefitial to the users. Seeing the response that this answer has received let me to think about how to put it. And seeing this other question being asked. I decided to try to ellaborate.
Any good IT system that really helps business users is designed from a business perspective. I.e. the designers of the IT system have analyzed the business and have tried to model the business' reality in the system. If they succeed, the system will be a success because the system is one that supports business processes. If not, then the system will dictate new business processes. And that is clearly the definition of a good IT system IMHO, it supports the business processes instead of dictating them. A typical approach that will lead to a poor IT system is when the designers, instead of thinking about the business processes, are thinking about the data that needs to be captured.
As to what I am about to write, it is purely speculation. I have no idea what MS were thinking when they designed Sharepoint.
Sharepoint is not designed by analyzing business processes. It has been designed from an architectural point of view. It has been designed from the point of view that you should be able to do anything. It should manage your data and your documents. So Sharepoint is a system designed by architects for business people. And that itself spells doom.
But no business is about handling documents. The real business is about selling your products. The documents are merely a necessity. E.g. you are not writing a product description because the product description itself is the product. It is because it can help selling the product. So an IT system that can handle you documents cannot be as effective as an IT system that helps the product development/life cycle.
An example of a poor Sharepoint solution: I once did a 3-month contract for a consultancy company that had build their own project management system in Sharepoint. The requirements and bug tracking were basically just tables of data. So the actual business process of handling a bug was left to be handled manually. The system only contained the data. And that company was supposed to be Sharepoint specialists.
Another example when Sharepoint has been counterproductive is when we are writing documentation of api/design/architecture for the software that we are creating. Those documents should be in the source control system where we have all our code anyway. So, e.g. creating a branch in the code, will also branch the documentation, allowing you to keep both updated. But some companies insist that these documents should reside in Sharepoint. Where they of course also need to be MS Word documents, instead of a plain text format, like markdown, or other, allowing for merge tools to help merge changes.
Oh yeah, and what about you need to check out or check in a document. We programmers know what check-out and check-in means, but business people simply do not. Checking out a document is simply not a business process.
So Sharepoint fails IMHO because it is not a system that supports business processes, it dictates new ones.
But you must give credit to the marketing people at MS, who did successfully convince virtually every CEO of every major company in Denmark that they need a Sharepoint installation.
[ 本帖最后由 iceman 于 2011-11-27 13:11 编辑 ] |
评分
-
查看全部评分
|
今天一次性通过了交规考试和HPT，趁热打铁，交作业！补上路考经验！ (2006-11-10) doulaimi 
万人期待的大片来啦！非诚勿扰前传--新足迹版 改编自《37岁男高调征婚贴》 (2013-4-20) steveking 
发表于 2011-11-27 12:11
发表于 2011-11-27 22:50
