Project Management: Planning, Execution & Control

TAKEAWAYS:

• Project management is the application of knowledge, skills, tools, and techniques to deliver a unique product/service within constraints of time, cost, and scope.
• Work Breakdown Structure (WBS) and Gantt charts are critical tools for breaking down projects into manageable tasks and timelines.
• Critical Path Method (CPM) and Program Evaluation and Review Technique (PERT) help identify the longest path of activities to optimize project scheduling.
• Risk management involves identifying, analyzing, and mitigating risks to ensure project success.
• Agile vs. Waterfall methodologies differ in flexibility, with Agile being iterative and Waterfall being linear.
• Earned Value Management (EVM) integrates scope, schedule, and cost to measure project performance.

1. Introduction to Project Management

Project management is the discipline of planning, organizing, securing, and managing resources to achieve specific goals within a defined timeline and budget. It is widely used in engineering, construction, IT, and business sectors.

Key Characteristics of a Project

• Unique: Projects produce one-time deliverables (e.g., building a bridge, developing software).
• Temporary: Projects have a defined beginning and end.
• Progressive Elaboration: Requirements and solutions evolve as the project progresses.
• Constraints: Must balance scope, time, cost, and quality.

Project Lifecycle

Most projects follow a phased approach:

1. Initiation: Define objectives, stakeholders, and feasibility.
2. Planning: Develop a project plan (scope, schedule, budget, risks).
3. Execution: Carry out the project plan.
4. Monitoring & Controlling: Track progress and adjust as needed.
5. Closure: Formalize acceptance and lessons learned.

flowchart TD
    A["Initiation"] --> B["Planning"]
    B --> C["Execution"]
    C --> D["Monitoring & Controlling"]
    D --> E["Closure"]

In the Real World

• eSewa (Nepal): Uses Agile project management to develop and update its digital payment platform iteratively, ensuring quick bug fixes and feature updates.
• Daraz (Alibaba Group): Employs CPM/PERT for logistics and inventory management to optimize delivery timelines across Nepal.
• NTC (Nepal Telecom): Uses risk management to handle network outages and cybersecurity threats in telecom projects.

2. Project Planning Techniques

Effective planning ensures projects stay on track. Key techniques include:

A. Work Breakdown Structure (WBS)

A hierarchical decomposition of a project into smaller, manageable components. Example: Building a smart traffic management system for Kathmandu:

1. System Design
   1.1 Hardware Selection
   1.2 Software Development
2. Implementation
   2.1 Sensor Installation
   2.2 AI Algorithm Training
3. Testing & Deployment
   3.1 Pilot Testing
   3.2 Full Rollout

B. Gantt Charts

A bar chart that visualizes project schedules, dependencies, and progress. Example: Software development timeline for a banking app (Nabil Bank):

Task               | Duration | Start Date | End Date
-------------------|----------|------------|---------
Requirements Gathering | 2 weeks  | 1-Jan-2024 | 15-Jan-2024
Design Phase        | 3 weeks  | 16-Jan-2024| 5-Feb-2024
Development         | 8 weeks  | 6-Feb-2024 | 25-Mar-2024
Testing             | 2 weeks  | 26-Mar-2024| 8-Apr-2024
Deployment          | 1 week   | 9-Apr-2024 | 15-Apr-2024

C. Critical Path Method (CPM) vs. PERT

Example (CPM for a Bridge Construction Project):

Task               | Duration (days) | Predecessor
-------------------|-----------------|-------------
Site Preparation   | 10              | -
Foundation Work    | 15              | Site Preparation
Steel Framework     | 20              | Foundation Work
Concrete Pouring    | 12              | Steel Framework
Roadwork            | 8               | Concrete Pouring

Critical Path: Site Preparation → Foundation Work → Steel Framework → Concrete Pouring → Roadwork (Total: 65 days).

3. Resource Allocation & Scheduling

Efficient resource allocation ensures cost-effectiveness and timely delivery.

A. Resource Leveling

Adjusts resource usage to avoid over-allocation (e.g., assigning too many engineers to one task while others are idle).

B. Resource Loading

Determines the amount of resources required over time (e.g., number of workers needed per week).

Example (Pathao’s Ride-Hailing App Development):

4. Risk Management in Projects

Risk management involves identifying, analyzing, and responding to risks.

Risk Management Process

1. Risk Identification: List potential risks (e.g., delays, budget overruns).
2. Risk Analysis: Assess probability and impact (qualitative/quantitative).
3. Risk Response Planning: Mitigate, transfer, avoid, or accept risks.
4. Risk Monitoring: Track and control risks throughout the project.

Example (Nepal Electricity Authority - NEA Power Plant Project):

5. Project Management Methodologies

A. Waterfall Model

• Linear and sequential approach.
• Phases: Requirements → Design → Implementation → Testing → Deployment.
• Best for: Projects with clear, unchanging requirements (e.g., construction, manufacturing).

B. Agile Methodology

• Iterative and incremental development.
• Phases: Sprints (2-4 weeks), continuous feedback.
• Best for: Software development, R&D (e.g., Khalti’s digital wallet updates).

Comparison Table:

6. Earned Value Management (EVM)

EVM integrates scope, schedule, and cost to measure project performance.

Key Metrics

1. Planned Value (PV): Budgeted cost of work scheduled.
2. Earned Value (EV): Budgeted cost of work completed.
3. Actual Cost (AC): Real cost incurred.
4. Cost Variance (CV): EV - AC (Positive = under budget).
5. Schedule Variance (SV): EV - PV (Positive = ahead of schedule).

Example (NTC Fiber Optic Cable Laying Project):

7. Case Study: Daraz Nepal’s Logistics Optimization

Problem: Daraz faced delivery delays due to inefficient route planning in Kathmandu. Solution: Applied CPM and Agile methodologies:

1. WBS: Breakdown of logistics into warehouse management, last-mile delivery, and customer support.
2. Gantt Chart: Scheduled deliveries in 24-hour windows.
3. Risk Management: Identified traffic jams and weather risks; used backup drivers.
4. EVM: Tracked cost vs. delivery time to optimize routes.

Result: 30% faster deliveries and 20% cost reduction.

Exam Tip

• For theoretical questions, explain concepts with real-world examples (e.g., eSewa’s Agile updates, Daraz’s CPM).
• For numerical problems, always show step-by-step calculations (e.g., CPM critical path, EVM metrics).
• Diagrams are worth marks! Draw Gantt charts, WBS, and risk matrices clearly.
• Compare methodologies (Waterfall vs. Agile) with pros/cons in tables.
• Case studies (e.g., NTC, Daraz) are common—link theories to practical scenarios.

A sample Gantt chart for project scheduling (Image: HarryTruinkers, CC BY-SA 4.0, via Wikimedia Commons)