A: There is usually not one single cause or agreement on why a project failed.
From our experience and observations, it's likely that the project did not have "company buy-in", was too complicated, project deliveries, if present at all, were not defined clearly enough, and/or other projects had a greater priority.
It doesn't have to be this way. Here are some observations that keep a SharePoint implementation project on track:
SharePoint deployment is not about technology, but about business's processes. The first step in any SharePoint implementation must be to find out how things are really being done in a department and not what the training manual describes as the process. This is discussed in Chapter 8, Managing your First SharePoint Project.
SharePoint adoption requires that users alter the way they have always done things. This means leaving their comfort zone and people don't like change. They tend to resist,...