Project planning - Advanced Planning and Control

Planning Techniques and Tools Activity Network Diagrams When planning a project, one of the most important tasks is understanding how different work activities relate to each other. An activity network diagram is a visual representation that shows the logical dependencies between tasks—that is, which tasks must be completed before others can begin. Think of it this way: before you can paint a wall, you need to first prepare it (clean it, patch holes, and sand it). The preparation is a prerequisite for painting. The activity network diagram captures these dependencies so that you can see the flow of work throughout the project. One of the key benefits of creating an activity network diagram is that it allows you to identify the critical path, which we'll explore in detail below. Without mapping out these dependencies, it's impossible to determine which tasks are truly time-critical for your project. Estimating Task Durations Every task in a project takes some amount of time to complete. However, estimating this time is rarely straightforward—there's usually uncertainty. A task that seems like it should take three days might take two days if everything goes smoothly, or it might take five days if unexpected problems arise. Rather than guessing a single number, project managers often estimate task durations using three scenarios: Optimistic time (O): The shortest time the task could reasonably take if everything goes perfectly Most likely time (M): Your best estimate of how long the task will actually take under normal circumstances Pessimistic time (P): The longest time the task might take if significant problems occur These three estimates are then combined into a single weighted-average estimate using the Program Evaluation and Review Technique (PERT) formula: $$TE = \frac{O + 4M + P}{6}$$ where $TE$ is the estimated duration. Notice that the most likely time is weighted four times more heavily than either the optimistic or pessimistic time. This reflects the reality that your most likely estimate is usually more reliable than the extreme scenarios. Example: Suppose you're estimating how long it will take to write project documentation. You think it could take as little as 2 days (optimistic), most likely 4 days (most likely), or as long as 10 days if you encounter major issues (pessimistic). Using PERT: $$TE = \frac{2 + 4(4) + 10}{6} = \frac{2 + 16 + 10}{6} = \frac{28}{6} = 4.67 \text{ days}$$ This gives you a more realistic estimate than simply guessing "about 4 days." Critical Chain Method Once you've estimated task durations and mapped out dependencies, you might create an initial schedule that chains these tasks together. However, projects often experience delays. The critical chain method addresses this reality by adding time buffers to the schedule. Rather than hoping that tasks finish on time, the critical chain method intentionally builds in cushion—additional time reserves that can absorb unexpected delays without pushing back the entire project deadline. These buffers act as a safety net, protecting your project schedule from the natural variation and uncertainties that arise during execution. Scheduling and Critical Path Understanding the Critical Path The critical path is the longest sequence of dependent tasks in your project. It's "critical" because it directly determines the minimum amount of time needed to complete your entire project. To understand why this matters, consider that some tasks might have flexibility in when they're scheduled (they don't affect the final deadline if they slip a bit), while other tasks have no flexibility at all. The critical path consists of those tasks with zero flexibility—if any task on the critical path is delayed, your entire project is delayed. Example: Imagine building a house with three major work streams: foundation work, framing, and painting. The foundation must be done first (3 weeks), then framing (2 weeks), then painting (1 week). That's a 6-week critical path. However, electrical work can happen during framing (2 weeks) and doesn't need to be completely done before painting starts. If electrical takes 3 weeks but can overlap with other work, it won't extend the project—it has slack time. The critical path remains the foundation → framing → painting sequence. Schedule Optimization Once you've identified the critical path, you might ask: "Can we do better?" Schedule optimization involves adjusting resource allocation and task sequencing to balance two competing goals: Reducing project duration: Finishing sooner means lower costs and faster delivery Smoothing resource usage: Using resources consistently throughout the project (rather than having some people idle while others are overwhelmed) These goals sometimes conflict. You might be able to compress the schedule by throwing more people at critical tasks, but this might create inefficiencies and increased costs. A well-optimized schedule represents the best balance between these competing objectives while meeting project goals. The Baseline Schedule After planning, estimating, and optimizing, you eventually reach a schedule that reflects your best judgment of how the project will unfold. Once this schedule is formally approved and accepted by stakeholders, it becomes the baseline schedule. The baseline schedule is crucial because it serves as your reference point for the rest of the project. It's not just a rough plan—it's a commitment, and it's the yardstick against which all actual progress will be measured. Think of it as a photograph of what you expected to happen, taken before the project execution begins. Resource Allocation and Cost Management Estimating Resources Each task in your project requires resources to complete. These might be people (with different skills or roles), equipment, materials, or facilities. During the planning phase, you must estimate what resources each activity will need. This estimation is important for two reasons: first, it helps you determine whether you have enough resources available, and second, it's the foundation for calculating project costs. Assigning Costs Once you know what resources are needed for each activity, you can assign costs. Cost allocation is the process of determining how much each resource will cost, then summing these costs across all activities to get your total project cost. For example, if Task A requires 20 hours of a senior engineer (at $100/hour), that task is allocated $2,000 in labor cost. By doing this for every task and every resource type (labor, materials, equipment, etc.), you build up a comprehensive project budget. Earned Value Management What Is Earned Value Management? Once your project is underway, you need to track progress. Earned value management (EVM) is a systematic approach to measuring how much work has actually been completed and comparing it against what you planned and what you've spent. The core idea is elegant: you assign a budgeted cost to each task (based on your planning phase). As tasks are completed, you "earn" that value. By comparing the value you've earned against the value you planned to earn at this point in time, and against what you've actually spent, you gain powerful insights into project performance. Think of it this way: you budgeted $1,000 for a task. You planned to complete it by week 3. By week 3, you've actually spent $1,100, but the task is only 80% complete. EVM gives you a framework to quantify and understand what that means for your project. Performance Metrics EVM provides several key metrics that measure project performance: Planned Value (PV): This is how much work you planned to complete by a given date, measured in dollars. If you planned to complete 50% of a $10,000 project by week 2, your PV is $5,000. Actual Cost (AC): This is what you've actually spent. If you really spent $6,000 by week 2, that's your AC. Earned Value (EV): This is how much work you've actually completed, measured in dollars. If you've actually completed 60% of that $10,000 project, your EV is $6,000. These three numbers form the foundation for understanding performance. The gap between what you planned and what you've accomplished reveals problems early, before they become catastrophic. Variance Analysis Variance simply means the difference between what you expected and what actually happened. EVM uses two critical variances: Schedule Variance (SV) measures whether you're ahead of or behind schedule: $$SV = EV - PV$$ If your earned value ($6,000) exceeds your planned value ($5,000), your SV is positive (+$1,000), meaning you're ahead of schedule. A negative SV means you're behind. Cost Variance (CV) measures whether you're under or over budget: $$CV = EV - AC$$ If you've earned $6,000 of value but spent $6,500, your CV is -$500, meaning you're over budget. A positive CV means you're under budget. Why This Matters: Variance analysis provides early warning signals. A negative schedule variance might indicate that you need to accelerate work on the critical path. A negative cost variance might mean your tasks are more complex than expected, or there's inefficiency that needs correction. By catching these issues early, you can take corrective action before the entire project is in trouble. Note: Variance analysis compares earned value against the baseline schedule established during planning. Without that baseline, you have no reference point, which is why the baseline schedule is so important.