Critical Path Analysis (Leaving Cert Applied Maths): Revision Notes
Critical Path Analysis
What is critical path analysis?
Critical Path Analysis (CPA) is a powerful project management technique used to plan and organise large, complex projects. When you have multiple tasks that need to be completed in a specific order, CPA helps you work out the most efficient sequence to follow.
Think of Critical Path Analysis like planning a complex recipe - you need to identify which ingredients must be prepared before others, and which steps can happen simultaneously without affecting the final outcome.
The main purpose of CPA is to identify which activities must be finished before others can begin. This prevents delays and ensures your project runs smoothly from start to finish. The technique is particularly valuable in construction, software development, event planning, and any project where timing and dependencies are crucial.
Key components of critical path analysis
Precedence tables
A precedence table is your starting point for any CPA. It's a simple two-column table that systematically lists:
- All the activities that need to be completed in your project
- Which activities depend on others being finished first
Activities that can start immediately are marked with a dash (-) in the dependencies column. These are your starter activities that don't need to wait for anything else.
Example: School Event Planning
For a school fundraising event, your precedence table might look like:
| Activity | Dependencies |
|---|---|
| Book venue | - |
| Design posters | - |
| Design tickets | - |
| Print tickets | Design tickets |
| Print posters | Design posters |
| Set up venue | Book venue |
Activity networks
An activity network is a visual diagram that shows how all your project activities connect together. This powerful visualisation tool uses:
- Numbered circles (nodes) to represent project milestones or stages
- Arrows to show the flow and direction between activities
- Letters or labels on the arrows to identify which specific activity is taking place
Activity networks transform complex project information from tables into clear visual diagrams that make it much easier to spot potential bottlenecks, parallel activities, and the overall project timeline.
Source and sink nodes
Every activity network has two special nodes that define the project boundaries:
- Source node: The starting point where your entire project begins
- Sink node: The final point where your project ends
You can identify the sink node from your precedence table by looking for activities that don't appear as dependencies for any other activities - these are your "finishing" activities that conclude the project.
Building activity networks from precedence tables
Converting a precedence table into an activity network requires patience and systematic thinking. The process often involves trial and error to get the structure right, and this is completely normal - even experienced project managers need several attempts to create the perfect network.
Key Strategy: Work Systematically
Don't try to draw the entire network at once. Instead:
- Start with activities that have no dependencies (source activities)
- Work through the table step by step, adding dependent activities
- Continuously check that every connection makes logical sense
- End with activities that nothing else depends on (sink activities)
The systematic approach involves identifying patterns in your precedence table first, then translating these relationships into a visual network that maintains all the logical dependencies while avoiding unnecessary complexity.
Understanding dummy variables
Sometimes you'll encounter situations where normal arrows aren't sufficient to show all the relationships between activities correctly. This is where dummy variables become essential tools in your CPA toolkit.
Dummy variables are special connections shown as dashed lines in your network diagram. They don't represent actual work or time-consuming activities - instead, they show logical relationships that need to exist to maintain correct project flow.
When Dummy Variables Are Essential
You'll need dummy variables when:
- An activity depends on multiple previous activities, but direct connections would create confusion
- Multiple activities depend on the same completed task in complex ways
- You need to avoid having double arrows between the same two nodes
- The logical flow requires a connection that doesn't represent actual work
Think of dummy variables as "invisible helpers" that keep your network mathematically correct and logically sound without adding extra work or time to your project timeline.
Practical examples
Worked Example 1: Basic Project Network
Consider a project with six activities: P, Q, R, S, T, and U.
Precedence Table:
- P, Q, and T can start immediately (no dependencies)
- R must wait for Q to finish
- S must wait for P to finish
- U must wait for both R and T to be completed
Network Construction: When drawn as a network, this creates a clear path from the source node through various numbered nodes to the final sink node. Each arrow represents one specific activity, and the numbered nodes show decision points or milestones in the project timeline.
Worked Example 2: Complex Engineering Project
A larger engineering project with activities A through N demonstrates how dummy variables work in practice.
Key Construction Tips:
- Draw nodes first, then number them when the overall structure is complete
- Use dummy variables (dashed lines) to handle complex interdependencies
- Multiple activities may converge at single nodes, requiring careful planning
This example shows that as projects become more complex, the visual representation becomes increasingly valuable for understanding the overall project flow and identifying potential scheduling conflicts.
Exam tips and strategies
When tackling Critical Path Analysis questions in exams, follow these proven strategies:
- Start with the precedence table: Always create and double-check this foundation before attempting the network diagram
- Embrace trial and error: Don't expect perfection on your first attempt - even professionals revise their networks multiple times
- Systematic checking: Ensure every activity from your table appears exactly once in your network
- Clear identification: Mark your source and sink nodes clearly - these should be obvious from your precedence relationships
- Master dummy variables: These frequently appear in exam questions, so practice identifying when and why they're needed
Key Points to Remember:
- Critical Path Analysis organises complex projects by mapping dependencies between activities
- Precedence tables are your foundation - they systematically list what must be finished before each activity begins
- Activity networks provide visual clarity showing the complete flow from source (start) to sink (finish) nodes
- Trial and error is normal and expected when converting precedence tables into network diagrams
- Dummy variables solve complex dependencies appearing as dashed lines to maintain mathematically correct network structure
- Practice makes perfect - the more networks you draw, the more intuitive the process becomes