Welcome to Task 8: Plan and Manage Schedule!
Hello, future PMP! Welcome to one of the most important parts of your project management journey. Think of the Project Schedule as the heartbeat of your project. Without it, you wouldn't know when to start, when you’ll finish, or if you are running late.
In this chapter, we are going to learn how to turn a list of things to do into a logical, timed plan. Don’t worry if math or complex charts sound intimidating—we are going to break it down into simple, everyday concepts that anyone can master. Let’s get started!
1. Understanding the Two "Flavors" of Scheduling
Before we dive into the details, remember that how you manage a schedule depends on the type of project you are running:
• Predictive (Waterfall): This is like building a house. You plan everything out in detail at the beginning. You have a fixed start and end date for every task.
• Agile (Adaptive): This is like a cooking show where you decide what to make based on the ingredients you have every 2 weeks. You use Timeboxes (Sprints) and Backlogs to manage work. The schedule is flexible and changes based on feedback.
2. Step 1: Defining and Sequencing Activities
You can't build a schedule until you know what tasks you have and what order they go in. This is called Sequencing.
Relationship Types:
Think of these as the "rules" of the project:
1. Finish-to-Start (FS): This is the most common. You must finish Task A before you can start Task B. (Example: You must finish baking the cake before you can put the frosting on.)
2. Start-to-Start (SS): You can start Task B as soon as Task A starts. (Example: You start recording a meeting at the same time the meeting starts.)
3. Finish-to-Finish (FF): Task B can’t finish until Task A finishes. (Example: You can't finish the documentation until the programming is finished.)
4. Start-to-Finish (SF): This is rare! Task B can’t finish until Task A starts.
Leads and Lags
Sometimes you need a gap or a head start:
• Lag: An intentional delay. (Example: You finish painting the wall, but you must wait 24 hours for it to dry before hanging a picture.)
• Lead: Starting a task before the previous one is fully done. (Example: You start writing the introduction of a book while the final chapter is still being drafted.)
3. Step 2: Estimating Durations
How long will a task take? Here are the four ways the PMP exam expects you to know:
1. Analogous Estimating: Using a "Top-Down" approach. You look at a similar project from the past and guess. It’s fast but less accurate. (Analogy: "Last time I painted a room it took 4 hours, so this room will take 4 hours.")
2. Parametric Estimating: Using math and data. (Analogy: "It takes 1 hour to paint 100 square feet. This room is 400 square feet, so it will take 4 hours.")
3. Bottom-Up Estimating: The most accurate. You break a task into tiny pieces, estimate each piece, and add them all up. It takes a lot of time but is very precise.
4. Three-Point Estimating (PERT): This uses three numbers to find a weighted average. This helps account for risk.
The PERT Formula (Beta Distribution)
If you see a question asking for a "weighted" average or the "PERT" estimate, use this formula:
\( E = (O + 4M + P) / 6 \)
O = Optimistic (Best case scenario)
M = Most Likely (What usually happens)
P = Pessimistic (Worst case scenario)
Quick Review: Remember A-P-T-B (Analogous, Parametric, Three-Point, Bottom-Up). Analogous is the fastest/cheapest; Bottom-Up is the most accurate/expensive.
4. Step 3: Finding the Critical Path
The Critical Path is the "Longest Path" through your project. It represents the shortest possible time to complete the project. Any delay on the critical path will delay the entire project.
What is Float (Slack)?
Float is the "wiggle room." Tasks on the Critical Path have Zero Float. If a task has 2 days of float, it means you can be 2 days late on that specific task without ruining the whole project finish date.
Real-world Analogy: Think of traveling to the airport. The "Check-in" and "Security" tasks are on your critical path. "Buying a magazine" might have float—if you take too long, it won't matter as long as you make it to the gate on time!
5. Step 4: Schedule Compression (When you are running late!)
What do you do when your boss says, "You need to finish this 2 weeks earlier"? You use these two techniques:
1. Crashing: Adding more resources (people or money) to speed things up.
Pros: Faster. Cons: Costs more money and increases risk.
2. Fast Tracking: Doing tasks in parallel (at the same time) that were originally planned to happen one after the other.
Pros: Doesn't cost extra money. Cons: High risk of rework because you might make mistakes by rushing.
6. Managing the Schedule in Agile
Agile projects don't use Gantt charts the same way Waterfall projects do. Instead, they use:
• Release Planning: The high-level plan for when new features will be "shipped" to the customer.
• Sprint/Iteration Planning: Planning the work for the next 1-4 weeks.
• Burndown Charts: A graph showing how much work is left versus time. If the line is dropping, you are making progress!
• Velocity: The average amount of work a team can finish in one Sprint. We use this to predict future finish dates.
7. Resource Optimization
Sometimes your schedule looks great on paper, but you realize your Lead Designer is scheduled to work 80 hours in one week! You need to fix this using:
• Resource Leveling: You balance the workload, but it often changes the project end date. (Priority: Keeping the team from burning out).
• Resource Smoothing: You balance the workload only within the "float" time. The end date does NOT change. (Priority: Keeping the deadline).
Common Mistakes to Avoid
• Mistake: Thinking the Critical Path is the "easiest" path. Correction: It's the longest sequence of activities and actually the most difficult to manage!
• Mistake: Using Crashing for every delay. Correction: Only crash tasks that are on the Critical Path. Adding more people to a task with float doesn't help the project finish any faster!
• Mistake: Confusing Lead and Lag. Correction: Lead is a "head start" (negative time), Lag is a "waiting period" (positive time).
Key Takeaways for Task 8
• Schedule Management Plan: The "rule book" for how time will be managed.
• PERT Formula: \( (O + 4M + P) / 6 \).
• Critical Path: Longest path, zero float.
• Compression: Crashing (More $) vs. Fast Tracking (More risk).
• Agile: Uses Velocity and Burndown charts to track the "schedule."
Don't worry if this seems tricky at first! Scheduling is a skill that takes practice. Just remember that every project schedule is just a series of guesses until the work actually starts. Your job as a PM is to make those guesses as smart as possible!