Skip to main content

How to Plan Your SharePoint Projects

Because I have always looked at SharePoint as a platform for building your organisations solutions that help improve business productivity, I thought I could write about a few simple project management steps that can aid when building these business solutions, classified as SharePoint Projects.

Step 1: Set the Direction

Before you start out, set the direction for the SharePoint project. Do this by clearly identifying the SharePoint project vision, goals and deliverables. State the overall timeframes for delivery and clarify the amount of resource available. Determine what is "in scope" and "out of scope". Identify the benefits and costs in delivering the SharePoint project and any milestones and constraints. Only once this is agreed with your SharePoint project Sponsor will you know what it is that you have to achieve.

Step 2: Task Selection

You're now ready to start planning. Identify the groups of tasks that need to be completed to build your SharePoint project deliverables. Then for each group of tasks, breakdown those tasks into sub-tasks to create what is known as a "Work Breakdown Structure" (WBS). Your WBS is essentially a hierarchical list of tasks, in order. Assign start and end dates to each task, as well as task durations. Always add a little extra time (e.g. 10%) to your durations, providing you with contingency. Next add Milestones to your plan. These are tasks that represent major achievements along the way.

Step 3: Inter-linking

The next step is to add links (or dependencies) between SharePoint project tasks. While there are a variety of link types, most SharePoint project Managers add "finish-to-start" links so that one task cannot start until another one finishes. To make your SharePoint project achievable, only add links between tasks if there is a critical dependency between them. Remember, when one task slips, all tasks linked to it may slip as well. So use links wisely.

Step 4: Resource Assignment

Now comes the fun part, assigning resources. A "resource" may be a person, equipment, location or materials. Against each task in your plan, assign one or more resources required to complete it. As you assign resources, watch your resource utilization. In other words, make sure you don't over-assign a specific resource to multiple tasks, so that it’s impossible for that resource to complete everything assigned to it.

Step 5: Baseline, Actuals and Reporting

With a fully completed SharePoint project plan, you're now ready to save it as a "baseline", so that you can later compare your progress against it. Then start recording your actual progress against the plan. Every day, record the amount of time you've spent against each task. Also record the new planned start and finish dates, and monitor the overall SharePoint project completion date. Report on progress as you go. By regularly updating the SharePoint project plan with your progress, you can control the delivery of your SharePoint project and meet those critical goals set.

Comments

Popular posts from this blog

Zambia's first Helpdesk System on SharePoint

For my 25th birthday today 3rd March, 2009, allow me to present to you another first of its kind in Zambia. Yes we have done it again, having been Project manager, I present to you Zambia's first Helpdesk System which Masialeti and I have developed on Microsoft Office SharePoint Server 2007. The system also implements SharePoint designer workflows, Infopath forms, SharePoint document library and sends email notifications to the relevant personnel. When a user logs in a call, the user automatically receives a mail from the system, telling them that their call has been received and is being attended to, IT section will also receive a notification and the helpdesk manager will assign the call to the right IT guy who will also automatically receive a mail notification from the system. When the call is resolved, the user again automatically gets notified by the system with a mail giving them description of the problem they logged and also how it has been resolved. The user also has an

Zambia's first K2 BlackPoint roll-out

Reporting to you live from Code|Influence... My colleague and I have been managing our organization's SharePoint infrastructure for some time now and we have just rolled out the first K2 BlackPoint in the country, intended mostly for SharePoint workflow developments.

How to implement a SharePoint "Change Management Process"

Not so much from the technical point of view, SharePoint Change Management is the process of monitoring and controlling changes within a SharePoint project. By managing the implementation of change, you can: • Reduce the impact of changes to the SharePoint project • Identify new issues and risks as a result of changes raised • Ensure that changes do not affect the SharePoint project's ability to achieve its desired objectives • Control the cost of change within the SharePoint project Change Management is comprised of the following processes: Step 1: Identify Change: The first step in the change process is to identify the need for change. Any team member can suggest a change to the SharePoint project, if he or she believes it is needed to keep the SharePoint project producing deliverables to the customer's specified requirements. After identifying a need for change, the team member records relevant information on a Change Request Form (commonly called a CRF), describing the chan