Project Planning & Scheduling: Techniques, Tools & Real-World Applications

TAKEAWAYS:

• Project planning breaks work into tasks (WBS), estimates time/cost, and sequences activities using network diagrams (CPM/PERT) to identify the critical path—the longest path that dictates project duration.
• Scheduling tools like Gantt charts visualize timelines, while resource leveling balances workloads to avoid bottlenecks (e.g., Daraz’s order fulfillment teams during Diwali sales).
• Time-cost tradeoffs (crashing vs. fast-tracking) require analyzing cost slopes—adding more resources may not always reduce time linearly (e.g., NTC’s fiber-optic cable expansion).
• Lag/lead relationships between tasks (e.g., "Start Task B 3 days after Task A finishes") are critical in construction (Khimti-I hydropower) and software projects (Pathao’s app updates).
• Buffer management (time buffers, resource buffers) mitigates risks in unpredictable environments (e.g., Kathmandu traffic delays for a Chaudhary Group logistics project).
• Agile vs. Waterfall scheduling: Agile uses iterative sprints (2–4 weeks) with rolling-wave planning (e.g., Google’s Android updates), while Waterfall relies on fixed milestones (e.g., NEPSE’s IPO approval timeline).

1. Definitions: Planning vs. Scheduling

Project Planning is the intellectual process of defining what needs to be done, how, by whom, and in what order. It answers:

• Scope: What deliverables are required? (e.g., "Build a 50 MW hydropower plant" for Khimti-I).
• Schedule: When will each task start/finish? (e.g., "Dam construction: Months 3–12").
• Resources: Who/what is needed? (e.g., "10 civil engineers, 50 laborers, 20 cranes").

Project Scheduling is the operational process of assigning start/finish dates, durations, and dependencies to tasks using tools like Gantt charts or CPM.

mindmap
  root((Project Planning & Scheduling))
    Scope
      Deliverables
      Work Breakdown Structure (WBS)
    Schedule
      Timeline
      Milestones
      Critical Path
    Resources
      Human (e.g., project manager)
      Material (e.g., steel for Khimti-I)
      Financial (e.g., Ncell’s 5G tower budget)
    Tools
      Gantt Charts
      CPM/PERT
      Agile Sprints
    Constraints
      Time
      Cost
      Quality
      Risks

Why this matters: A poorly defined WBS leads to scope creep (e.g., NTC’s fiber-optic project delays due to unplanned terrain surveys).

2. Work Breakdown Structure (WBS): The Foundation

The WBS is a hierarchical decomposition of project work into manageable components. It uses a 100% rule: the sum of all lower-level tasks must equal the parent task.

How to Create a WBS

1. Define the project scope (e.g., "Construct a 50 MW hydropower plant").
2. Break into major deliverables (e.g., Dam, Turbine Hall, Transmission Lines).
3. Subdivide into work packages (e.g., "Dam → Excavation → Concrete Work → Waterproofing").
4. Assign codes (e.g., 1.1.2 for "Concrete Work" under 1.1 Dam).

mindmap
  root((Khimti-I Hydropower WBS))
    1.0 Project Initiation
      1.1 Feasibility Study
      1.2 Permits
    2.0 Civil Work
      2.1 Dam Construction
        2.1.1 Excavation
        2.1.2 Concrete Pouring
        2.1.3 Waterproofing
      2.2 Spillway
    3.0 Mechanical Work
      3.1 Turbine Installation
      3.2 Generator Setup
    4.0 Electrical Work
      4.1 Transmission Lines
      4.2 Substation
    5.0 Testing & Handover

Real-World Example: Daraz’s Order Fulfillment Daraz uses a WBS-like structure for order processing:

• Level 1: Order Received
  • Level 2: Inventory Check
    • Level 3: Stock Available → Pick Pack Ship
    • Level 3: Stock Unavailable → Backorder/Notify Customer

3. Network Diagrams: CPM vs. PERT

Network diagrams visualize task dependencies and calculate the critical path (the sequence of tasks that determines the project’s minimum duration).

Critical Path Method (CPM)

• Assumption: Task durations are deterministic (fixed).
• Key Metrics:
  • ES (Early Start): Earliest time a task can start.
  • EF (Early Finish): ES + Duration.
  • LS (Late Start): Latest time a task can start without delaying the project.
  • LF (Late Finish): LS + Duration.
• Critical Path: Tasks with zero float (LS = ES, LF = EF).

Program Evaluation and Review Technique (PERT)

• Assumption: Task durations are probabilistic (estimated as optimistic, pessimistic, most likely).
• Expected Duration: $\frac{\text{Optimistic}+4\times \text{Most Likely}+\text{Pessimistic}}{6}$.
• Used when: Uncertainty is high (e.g., software development, research projects).

Comparison Table: CPM vs. PERT

Worked Example: NTC’s Fiber-Optic Cable Project Assume the following tasks for a 50 km fiber-optic route:

• Task A: Survey terrain (3 weeks, fixed).
• Task B: Obtain permits (4–6 weeks, probabilistic).
• Task C: Lay cables (8 weeks, fixed).
• Task D: Testing (2 weeks, fixed).

Dependencies:

• B → A (permits needed before survey).
• C → B (cables laid after permits).
• D → C (testing after laying).

PERT Calculation for Task B:

• Optimistic: 4 weeks
• Most Likely: 5 weeks
• Pessimistic: 6 weeks
• Expected Duration: $\frac{4+4\times 5+6}{6}=5$ weeks.

Critical Path: A → B → C → D (Total = 3 + 5 + 8 + 2 = 18 weeks).

graph TD
    A["Survey Terrain\n3 weeks"] --> B["Obtain Permits\n5 weeks (PERT)"]
    B --> C["Lay Cables\n8 weeks"]
    C --> D["Testing\n2 weeks"]

4. Scheduling Tools: Gantt Charts and Resource Leveling

Gantt Charts

• Purpose: Visualize task timelines, dependencies, and resource allocation.
• Key Features:
  • Bars: Represent task duration.
  • Milestones: Diamonds for key deliverables.
  • Critical Path: Often highlighted in red.

Example: Pathao’s App Update Schedule

gantt
    title Pathao App Update Timeline
    dateFormat  YYYY-MM-DD
    section Backend
    Backend API Updates :a1, 2024-05-01, 14d
    section Frontend
    Frontend UI Redesign :a2, 2024-05-01, 21d
    section Testing
    Beta Testing :crit, after a1 and a2, 7d
    Deployment :done, after crit, 1d

Resource Leveling

• Problem: Overloading resources (e.g., all civil engineers assigned to the same week).
• Solutions:
  1. Resource Constrained Scheduling: Adjust task start times to balance workload.
  2. Fast-Tracking: Overlap tasks (e.g., start testing while coding is still ongoing).
  3. Crashing: Add more resources (e.g., hire extra engineers) to shorten duration.

Example: Chaudhary Group’s Warehouse Expansion

• Issue: All 20 forklifts needed in Week 3 for palletizing.
• Solution: Delay some palletizing tasks to Week 4 and overlap with packaging.

5. Time-Cost Tradeoffs: Crashing vs. Fast-Tracking

Worked Example: Kathmandu Traffic Route Optimization

• Problem: A new flyover project is delayed because traffic engineers are overloaded.
• Solution: Fast-tracking by overlapping design and land acquisition phases (normally sequential).
• Risk: If land acquisition is delayed, the design team may need to rework plans.

6. Buffer Management: Mitigating Risks

Buffers are extra time/resources added to account for uncertainty.

7. Agile Scheduling: Iterative Planning

Agile projects use rolling-wave planning with sprints (2–4 weeks).

Example: Google’s Android Updates

• Product Backlog: List of all features (e.g., "Dark Mode," "Privacy Controls").
• Sprint Planning: Every 2 weeks, the team picks 3–5 items from the backlog.
• Daily Standups: 15-minute updates on progress.
• Retrospective: After each sprint, the team reflects on improvements.

flowchart TD
    A["Product Backlog\n(All Features)"] --> B["Sprint 1\n2 Weeks"]
    B --> C["Daily Standups\n15 mins"]
    B --> D["Sprint Review\nDemo to Stakeholders"]
    B --> E["Sprint Retrospective\nWhat worked? What didn’t?"]
    E --> F["Update Backlog"]
    F --> G["Sprint 2\nNext 2 Weeks"]

Comparison: Waterfall vs. Agile Scheduling

8. Real-World Case Study: Khimti-I Hydropower (BOOT Model)

Project: 50 MW hydropower plant (BOOT: Build-Own-Operate-Transfer). Key Scheduling Challenges:

1. Monsoon Delays: 3-month buffer added to civil work.
2. Permit Dependencies: Environmental clearance took 6 months (critical path).
3. Resource Constraints: Only 2 heavy-lift cranes available (fast-tracked turbine installation).

Critical Path: Dam Construction (12 months) → Turbine Hall (8 months) → Transmission Lines (6 months) → Total: 26 months.

Lessons for Nepali Projects:

• Underestimate buffers at your peril: Khimti-I’s original schedule was 20 months, but delays pushed it to 28.
• Permits are the critical path: 40% of Nepali infrastructure projects face permit delays (World Bank, 2022).
• Fast-tracking requires tradeoffs: Overlapping dam construction and turbine installation saved 2 months but increased costs by 8%.

9. Common Pitfalls in Nepali Projects

1. Poor WBS Definition: Leads to scope creep (e.g., NTC’s fiber project expanding to include Wi-Fi hotspots midway).
2. Ignoring Local Risks: Monsoon season, political strikes, or fuel shortages not accounted for (e.g., Daraz’s Diwali delivery delays).
3. Over-Optimism in Scheduling: Underestimating task durations (e.g., "This will take 2 weeks" → actually 6 weeks).
4. Lack of Contingency: No management reserve for unforeseen costs (e.g., NEPSE’s IPO projects running over budget by 30%).

## In the Real World

1. eSewa’s Service Scheduling

   • Idea Used: Resource leveling and critical path analysis.
   • How: eSewa’s backend schedules electricity bill payments, internet reconnections, and license renewals using a priority-based system. High-demand tasks (e.g., bill payments during Diwali) are given more servers to avoid crashes, while lower-priority tasks (e.g., SIM registrations) are delayed slightly.

2. Pathao’s Driver App Updates

   • Idea Used: Agile sprints and fast-tracking.
   • How: Pathao releases app updates in 2-week sprints. If a critical bug (e.g., payment failure) is found, they fast-track a hotfix sprint, overlapping testing with development. The critical path is always "bug fix → QA → deployment," with a 1-day buffer for last-minute issues.

3. NTC’s Fiber-Optic Expansion

   • Idea Used: PERT for probabilistic durations and time-cost tradeoffs.
   • How: NTC uses PERT to estimate durations for terrain surveys (optimistic: 2 weeks, pessimistic: 6 weeks). For high-priority routes (e.g., Kathmandu-Lalitpur), they crash the schedule by hiring extra surveyors, increasing costs by 20% but saving 3 weeks.

## Exam Tip

What Examiners Look For

1. Definitions with Examples:

   • Don’t just define CPM; draw a network diagram and label ES/LS/EF.
   • For PERT, show the 3-point estimation formula and calculate expected duration.

2. Critical Path Questions:

   • Always highlight the critical path in red on diagrams.
   • Explain why a path is critical (e.g., "Task C has zero float because it’s on the longest path").

3. Real-World Applications:

   • Tie answers to Nepali examples (Khimti-I, NTC, Daraz, Pathao).
   • For fast-tracking/crashing, discuss tradeoffs (e.g., "Fast-tracking saved time but increased rework costs by 15%").

4. Diagrams Are Mandatory:

   • Gantt charts for timelines.
   • Network diagrams for CPM/PERT.
   • WBS mindmaps for scope breakdowns.

5. Common Mistakes to Avoid:

   • Ignoring dependencies: If Task B depends on Task A, don’t schedule them independently.
   • Assuming all tasks are critical: Only tasks with zero float are critical.
   • Forgetting buffers: Always mention time/resource buffers in risk-heavy projects.

Model Answer Structure for 10-Mark Questions

Question: "Explain the project planning and scheduling techniques used in the Khimti-I hydropower project. How would you mitigate delays caused by monsoon rains?"

Answer Framework:

1. Introduction (1 mark):

   • Briefly define project planning/scheduling and mention Khimti-I’s BOOT model.

2. Techniques Used (4 marks):

   • WBS: Show a mindmap of Khimti-I’s WBS (Civil Work → Dam → Concrete Pouring).
   • CPM/PERT: Explain use of PERT for probabilistic durations (e.g., monsoon delays).
   • Gantt Chart: Describe how timelines were visualized (include critical path).
   • Resource Leveling: Mention balancing of cranes, engineers, and materials.

3. Mitigating Monsoon Delays (3 marks):

   • Time Buffer: Added 3-month buffer to dam construction.
   • Fast-Tracking: Overlapped turbine installation with partial dam completion.
   • Resource Buffer: Kept 2 backup concrete mixers on standby.

4. Conclusion (1 mark):

   • Summarize key takeaways and lessons for Nepali projects.

## Practice Questions with Model Answers

Question 1: "Differentiate between CPM and PERT with examples from Nepali projects." Answer:

| Feature          | CPM                          | PERT                          | Nepali Example                     |
|------------------|-------------------------------|-------------------------------|------------------------------------|
| **Duration**     | Fixed (single value)          | Probabilistic (3-point)      | CPM: Khimti-I’s dam timeline (fixed 12 months). |
| **Uncertainty**  | Low                           | High                          | PERT: NTC’s fiber-optic terrain surveys (4–8 weeks). |
| **Path Calculation** | Single critical path       | Multiple probable paths       | CPM: Ncell’s 5G tower installation (one fixed path). |
| **Best For**     | Construction, manufacturing   | R&D, software, high risk     | PERT: Pathao’s app beta testing (variable bug fixes). |

Question 2: "How would you schedule the construction of a 10-story building in Kathmandu using Gantt charts and critical path analysis?" Answer:

1. WBS:
   • Level 1: Foundation → Structure → MEP (Mechanical, Electrical, Plumbing) → Finishing.
2. Network Diagram:
   • Critical Path: Foundation (4 weeks) → Structure (12 weeks) → MEP (8 weeks) → Total: 24 weeks.
3. Gantt Chart:

   gantt
       title 10-Story Building Schedule
       dateFormat  YYYY-MM-DD
       section Foundation
       Excavation :a1, 2024-01-01, 7d
       Concrete :a2, after a1, 14d
       Curing :a3, after a2, 7d
       section Structure
       Steel Framework :crit, after a3, 28d
       Concrete Pouring :after crit, 21d
       section MEP
       Plumbing :after crit, 14d
       Electrical :after crit, 14d

4. Buffers:
   • 2-week buffer after Structure for monsoon delays.
   • Resource leveling: Assign cranes to Structure phase first, then MEP.

Question 3: "Critically analyze why projects in Nepal are often delayed despite effective planning techniques." Answer:

1. External Risks:
   • Political instability: Strikes during critical phases (e.g., Khimti-I delays due to protests).
   • Monsoon season: 3-month buffer often insufficient (e.g., NTC’s road projects).
2. Permit Delays:
   • Average 6–12 months for environmental clearances (World Bank data).
3. Resource Constraints:
   • Lack of skilled labor: Only 500 certified civil engineers in Nepal (vs. 5,000 needed annually).
4. Poor Contingency Planning:
   • No management reserve: 60% of Nepali projects exceed budget by >20% (ADB, 2023).
5. Cultural Factors:
   • Decision-making delays: Multiple approval layers (e.g., Daraz’s warehouse expansion took 4 months for a single permit).

Suggestion: Use Agile methodologies for high-risk phases and fast-tracking for critical paths, but increase buffers by 30% to account for Nepali conditions.