How To Make A SharePoint Project A Success

When you hit a software development project the key is always to ensure the time and budgets are met. You do not want the project to overrun, you do not want it to be unused and you do not want to have to tell the client you have over spent. So how do you control all of that and make sure the SharePoint project is a great success?

Think about the things that may trip you up along the way and then solve the problems. Things like; difficult users, lack of engagement, indecisiveness, unwilling users, stressed steam and unmanageable expectations. Not sure what Microsoft SharePoint is? Check this out http://en.wikipedia.org/wiki/Microsoft_SharePoint.

Following from that this SharePoint graphic gives us 10 tips to help make sure these points do not become problems;

1. Get into the mix with those hard to change, stubborn customers. Make them important and understand their needs. This will get them into the project and you may well find that the rest of the team follow. If you can show them you care and the solution can help them you are onto a good start.

2. Every team needs an owner and so does every project. Someone to take charge and lead the way. You want to get an enthusiastic person to take control and run with the project to keep things moving.

3. No one reads a training manual, or 99% of the world does not. They get on and try to figure it out. Once they are frustrated, annoyed and ready to walk away they might check out the manual but chances are they will just revert back to old processes. So be proactive with the training and get involved with the users. Show them before any frustration happens because all that happens is they link the frustration to the new solution and it is hard to then remove that barrier.

4. SharePoint is a business run solution. It allows the business to get a solution that meets their needs. So run it in that manner, do not expect the technical IT experts to know your processes and objectives, you have to tell them. It is the businesses system and they will use it.

5. Give it a name because it isn’t that “new SharePoint system” as SharePoint is just the name of the framework in which you build your solution on. What is your solution called? Having a meaningful name helps bring the project to life and people stop getting hung up on the technical barriers.

6. Do not expect an end as this is a live and running system that adapts with the business as it grows. You may have a new piece of functionality added or changed but the system and processes will be ever evolving.

7. Because the initial project could last a long time do not expect requirements to stay the same. Go with the flow and adapt, do not be ridged as it will all break down, making the solution unfit for purpose.

8. Get in front of the users and let them know what to expect, do not leave them wondering as wondering minds can lead to massive over expectation. Over expectation will lead to disappointment and thus appear like the solution is not as great as it actually is.

9. Have a group of people that can steer the project. This is not a group of directors this is a mixed group of people from the business that can help mould and drive this, including the users.

10. Rules are used to help keep structure but not to add stress. Do not have too many as after all there is a business to run while this is happening. And on top of that people have to learn new processes and take in lots of information. So have rules but do not have too many.

Check out the infographic at http://www.evokeit.com/sharepoint-blog/project-success-infographic. The best thing about Microsoft SharePoint is the community, everyone pulls together unlike anything else.

Author Jack Tailor. A Microsoft SharePoint developer loving everything technical in the world.