If you work in project management, you understand the importance of an effective project management strategy or methodology.
We’ve already delved into other aspects of project management, like how to make use of Gantt charts and the pros and cons of different project management methodologies. But it’s worth it to take a deeper look at other methodologies and understand how they could have an impact on your team.
PERT stands for program evaluation review technique. Other names for PERT charts are network diagram and precedence diagram. This technique aims to break down the various project tasks so they may be analyzed.
This time around, let’s get ready to discuss PERT charts.
PERT is an acronym which stands for program evaluation review technique. This methodology originated from the US Navy in the 1950s and is still being utilized by many teams for project management today.
The PERT method is similar to CPM or the critical path method in that they both aim to schedule and direct projects.
PERT charts are typically used before a project begins so administrators can understand the duration of the project as a whole. While they don’t have to operate off of specific dates like a Gantt chart would, they should still be just as accurate in their estimates of task duration.
Tip: Check out the easiest-to-use project management solutions as ranked by verified users.
The chart, or network diagram, itself is a schematic or visual diagram of a project’s schedule. PERT charts make use of network diagrams to represent the schedule. They are made up of two parts: nodes and vectors.
The nodes represent tasks while the vectors represent the order in which the tasks are completed.
In the sample image below, the circles are nodes and the lines are the vectors. So the circles represent tasks one, two, and three whereas the lines represent the order of steps, as well as the time taken to completion.
In this example, it takes two days to advance from step one to two, and three days to advance from step two to three.
PERT charts are also known as “precedence diagrams” because they show both the order in which tasks must be completed, and they communicate dependencies.
Consider the example above. Because steps two and three are only dependent on step one, they can be accomplished at the same time. These are referred to as parallel or concurrent tasks. Tasks that have to be completed in a certain order are called dependent or serial tasks.
In the Gantt chart example below, you can see there are dependent tasks.
PERT charts help users develop a realistic idea of the project’s timetable. Administrators accomplish this by assigning three possible timelines to each task: optimistic, pessimistic, and most likely.
The optimistic estimate is your best case scenario, assuming all goes well. Your pessimistic estimate is the maximum amount of time it could take to accomplish one activity, or your worst case scenario. Typically only the “most likely” estimate is delivered to members of upper management.
In order to create a PERT chart, you need to remember two simple guidelines. First, you should represent tasks as arrows. Second, you should represent milestone dates as nodes, which are typically visualized as circles or rectangles.
If you look at a PERT chart in relation to one activity, you can see how simple they are to understand. Let’s do this using the sample image below.
The node on the far left labeled “one” indicates the first task in a series. Because we’re looking at a single activity, I’ve gone ahead and labeled the names of the tasks on the chart.
The design of your PERT chart will depend entirely on you and your team’s preference. Some choose to keep the chart very minimal and label tasks elsewhere, such as in a spreadsheet or list. Others use what is called an activity-on-node design wherein more detailed descriptions of tasks are included in the chart.
Lucidchart provides a helpful PERT chart example of the activity-on-nodes type of PERT chart, should that be your preference.
Step 1 in this example is researching a topic. I’ve indicated that this research will take one day. PERT charts will always feature the numerical duration of a task on top of the line/arrow connecting the two tasks. Your chart should feature a key denoting how you are measuring time (ie hours, days, weeks, etc).
Task two is dependent on task one. The creator in this scenario cannot move onto their outline until they have completed topic research.
When you add more tasks to the mix, PERT charts begin looking more complex and the brain can find them difficult to interpret.
That’s why we started small, so seeing a larger example wouldn’t completely fry us. Now that we understand how to interpret one activity, let’s move on to a more in-depth example.
In this example, we have five tasks. Task four is dependent on the completion of tasks two and three, while task five is independent of all tasks except for the first one. Once you’ve completed task four and five, you arrive at the finish line.
I’ve given you a few generic examples of PERT charts, but there’s still so much to know! In this section, I’ll outline some commonly understood best practices of PERT charts to help you get the most out of this strategy.
As I stated in PERT chart best practices, you should create PERT charts within a solution you understand how to operate.
For many, this tool might be Microsoft Excel, as it’s frequently used regarding other business functions and wouldn’t take too much getting used to.
For those who have never used Excel and would like to make a PERT chart specifically, there are other solutions to consider. Many project management solutions will also offer chart creation features.
Another option you have is to consider specific chart-making tools such as LucidChart or WBS Schedule Pro.
If PERT charts are new for you, don’t worry! They’re an effective scheduling and project management tool that, through time and practice, will become second nature for you to create and for your colleagues to understand.
And if you’re looking for more information to help with your project strategies, I’d recommend reading more on project milestones and why they matter.
Grace Pinegar is a lifelong storyteller with an extensive background in various forms such as acting, journalism, improv, research, and content marketing. She was raised in Texas, educated in Missouri, worked in Chicago, and is now a proud New Yorker. (she/her/hers)
Subscribe to keep your fingers on the tech pulse.