How to Programme Your Projects

Every Project Director demands a crystal-clear plan for their project. How should you develop this programme? Should it be made in the same way each time? At what phase will dependencies, baselines and actuals be recorded? To show the answers to these usually asked questions, read on…

How to Programme Your Projects

It doesn’t matter which industry you’re into or project you’re taken with, these 5 procedures must be acquired every moment to rightly plan your project:

Step 1: Set the Direction

Before you start out, determine the focus for the project. Do this by understandably distinguishing the project sight, goals and deliverables

  • State the overall timeframes for delivery and clear up the sum of resource available.
  • Specify what is “in scope” and “out of range”.
  • Distinguish the gains and costs in presenting the project and whatsoever milestones and constraints.

Only once this is integrated with your Project Supporter will you recognise what it is that you make to achieve.

Step 2: Task Choice

You’re now developed to begin planning. Discover the groups of undertakings that require to be realized to form your project deliverables.

Work Breakdown Construction
Project Plan – Work Breakdown Structure

Then for each team of jobs, breakdown those undertakings into sub-tasks to produce what is acknowledges as a “Work Breakdown Construction” (WBS). Your WBS is essentially a hierarchical list of chores, in order

  • Assign start and closing dates to all job, as well as undertakings lengths.
  • Forever add a little excess moment (e.g. 10%) to your durations, supplying you with contingency.
  • Next add Milestones to your programme.

These are undertakings that correspond leading achievements along the road.

Step 3: Inter-connecting

The following measure is to supply associates (or dependencies) between project jobs. While there are a variety of link types, most Project Managers add “finish-to-start” connections so that one task cannot start until another one finishes. To have your project feasible, just add links between undertakings if there is a crucial dependency between them. Remember, when one job slips, all tasks joined to it might slip too. So use links wisely.

Step 4: Resource Assignment

Now comes up the fun role, assigning resources. A “resource” may be an individual, machines, location or stuffs. Against all task in your plan, assign one or more resources involved to finished it. As you designate resources, check your resource utilization. In other words, make sure you don’t over-assign a specific resource to three-fold tasks, so that it’s unattainable for that resource to finished everything specified to it.

Step 5: Baseline, Actuals and Reporting

With a fully finished project plan, you’re at present set to save it as a “baseline”, so that you can afterwards compare your progression against it. Then start entering your real progress against the plan. Every day, record the measure of time you have expended against each undertaking. Also show the other planned start and end dates, and oversee the whole project completion date. Report on progress as you move. By weekly updating the project design with your advancement, you can control the delivery of your project and meet those crucial aims fix.

4 thoughts on “How to Programme Your Projects

  1. Jane Campyn says:

    Getting the WBS done right it where I find most projects work. If I can nail that, then the rest are ok. How do you do resources? Do you do it by man days or by the hour.

    • Ivan Walsh says:

      I price & schedule the project by man days. I find that works better for IT projects, esp when I need to factor in overtime and the scope creep.

  2. Margaret says:

    How do you account for scope creep?
    I mean do you allow for 10% to be added to the project and/or assume that that’s enough to cover you?
    How much contingency should I allow for?

    • Ivan Walsh says:

      I schedule the project by man days and allow 10%~ for scope creep.
      Usually it is not this high but I find it better to err on the side of caution rather than be over-optimistic.
      Things often change on IT projects! Without any warning.

Comments are closed.