Showing posts with label evaluation. Show all posts
Showing posts with label evaluation. Show all posts

Wednesday, February 13, 2008

An Introduction to CPM, PERT and GERT

How do project teams determine a project's duration? Is it an exact science? The answer is no, it is not an exact science. It is more a process of estimating activity durations, which can be made easier by utilizing mathematical analysis.

Mathematical analysis is used in project schedule development to determine early and late start dates, as well as early and late finish dates for all project activities. The outcome indicates the time period in which the activity should be scheduled. Note that this analysis phase does not take into account any resource pool limitations or constraints.

The most widely known mathematical techniques used by project management teams are the: Critical Path Method (CPM), Program Evaluation and Review Technique (PERT), and Graphical Evaluation and Review Technique (GERT).

Critical Path Method (CPM)
The most common mathematical technique is the Critical Path Method (CPM). The CPM is used to predict project duration by analyzing which sequence of activities, or path, has the least amount of scheduling flexibility.

Once you have determined the early and late start and finish dates, you can determine float. Float is equal to the difference between the late finish and early finish dates, or the difference between the late start and early start dates.

The next step in the CPM is to determine the critical path (CP), which is the longest path for the project that has little or no float. To determine the critical path, you begin with the first activity in the network. Look at its successors, compare the successors' float values, and select the one with zero float. This is the second activity on the critical path.

Next, you would continue from the second activity on the critical path and compare float for its successors, selecting the activity that has zero float and including it in the critical path.

You continue this process to the final activity for a complete critical path. The project can finish no sooner than the time it takes to complete the activities on the critical path.

To calculate an activity's duration, you subtract the early start from the early finish or the late start from the late finish. In example that follows, the numbers indicate days.
  • activity A - 1 day
  • activity B - 2 days
  • activity C - 3 days
  • activity D - 2 days
Adding the total of the activity durations will give you the duration of the critical path. In this example, the duration of the critical path would be 8 days.
Critical Path activities are, indeed, critical to a project's success. They need management's careful attention. The order and duration of these activities are important because any delays will result in the project going over the anticipated completion date. In addition, project improvements are most effective when made along the critical path.

Program Evaluation and Review Technique (PERT)
Have you ever performed activity duration estimates, then questioned your findings? There is a technique available for checking your findings.

Program Evaluation and Review Technique (PERT) is used when there is a high level of uncertainty about how long it will take to perform a given task.

PERT uses network logic—the collection of activity dependencies that make up a project network diagram—to determine duration. In PERT, network logic is used by applying the critical path method to a weighted average duration estimate.

Although very similar, there is one significant difference between PERT and CPM. CPM uses the most likely estimate instead of the expected value of the estimate that PERT uses.

PERT time estimating requires the following three estimates for each activity.
  • TM = most likely time
  • TO = optimistic time
  • TP = pessimistic time
To determine the expected activity time you must insert the previous estimates into the PERT weighted average formula, which is optimistic (TO) + 4 x most likely (TM) + pessimistic (TP) all divided by 6.
Once you have calculated the estimated times for your project you can plot those values on an s-curve. The s-curve allows you to easily see all three times—optimistic, most likely, and pessimistic.

Graphical Evaluation and Review Technique (GERT)
There is one additional mathematical analysis method that is rarely used today because it has been proven to be less accurate than PERT and CPM. This method is the graphical evaluation and review technique (GERT). GERT allows for probabilistic treatment of both network logic and activity duration estimates. GERT is mainly used on project activities that are only performed in part, as well as those activities that may be performed more than once (loop). The above graphic illustrates a GERT diagram with a simple loop.

For example, on a high-rise development project, the electrical outlets for each floor may be installed as each floor is completed instead of waiting for the completion of the entire building. Since this activity will be performed more than once, using GERT will enable you to calculate the entire duration of this activity.

Regardless of the type of mathematical analysis you apply to your projects, the ultimate objective is to produce a schedule with realistic start and finish dates.

Saturday, June 30, 2007

Evaluating an IT Project

To ensure your IT project is on track, and to prevent serious performance issues, you should evaluate the project at the end of each of the six project stages. Usually, the end of a stage is identified by the completion of a project deliverable. An evaluation process can help your team determine whether changes need to be made to the process or plan before moving to the next stage.

After working diligently to reach the end of each stage of the project, it is important for all team members to meet to discuss the negative and positive aspects encountered up to this point. The focus of this meeting is to evaluate the activities and variables for each particular stage in the current project's development.

For example, during the evaluation, the team may determine that the project scope has changed, the team has not been as productive as planned, or necessary tasks have been left out. These are all variables that can lead to missed deadlines.

During the evaluation of an IT project's development, it is essential to consider two main business activities. The two business activities that should be the focus of the project evaluation are described below.

1. Estimate schedule performance.
Processes that should work harmoniously together sometimes do not. Your team may find that these unforeseen circumstances can dramatically slow down development. You then have to stop and reevaluate the process. This can sometimes be very time consuming.

Your team can estimate schedule performance by comparing the schedule estimates with the actual work completed. A formula for measuring schedule efficiency is the schedule performance index (SPI).

SPI is the schedule efficiency ratio of earned value (EV) accomplished against planned value (PV). The formula is SPI = EV ÷ PV x 100. In this formula, EV answers the question, "How much work has actually been completed at this point?" PV answers the question, "How much work was scheduled to be completed by now?" To round the SPI, look at the digit to the right of the place to which you are rounding. If that digit is less than 5, round down (6.45 = 6). If that digit is equal to or more than 5, round up (6.51 = 7).

When analyzing SPI for a project, you must consider the results from the calculation. A result equal to 100 indicates that the project is performing as estimated. A result that is greater than 100 indicates that the project is performing ahead of estimates. A result of less than 100 indicates the project is behind estimates.

Managers prefer to see the schedule hit within an acceptable range, where 85 or 90 out of 100 is considered acceptable. When the result varies significantly below 100, risk analysis will be necessary.

2. Evaluate team member performance.
Another business activity to evaluate is team member performance. The wrap-up at each stage of the project is an ideal time to evaluate whether the team has met the goals of the project plan.
It's important to evaluate the performance of team members to ensure they meet completion dates for each task, as documented in the project plan. Valuable time can be lost when even one member of the team does not meet individual goals. With each task set up to flow smoothly into another, a deviance from the established plan can cause major problems.

How can you determine whether team members have met project goals? You can establish a performance expectation for each task prior to beginning the project. The completion time for each task is normally estimated using an average work week of an eight-hour day and 40 hours. The equation you can use to determine completion time for a task is: number of estimated hours for completion ÷ 8-hour day = time allowance in days.

For example, if the task is estimated at 20 hours, then it should be completed in 2.5 days (20 ÷ 8 = 2.5) to be on schedule. If a task is estimated to take 2.5 days and it actually takes three days to complete, then the task has missed the deadline. If the task is completed in less than 2.5 days, it is ahead of schedule.

Do not underestimate the importance of evaluating your project's development. An evaluation at the end of each stage of your project can prevent serious performance issues as the project progresses.