Project Management Basics: Definitions, Types, and Core Concepts

TAKEAWAYS:

• A project is a temporary endeavor with a defined start and end, aimed at creating a unique product, service, or result.
• Projects differ from operations in their temporary nature, uniqueness, and progressive elaboration.
• The project life cycle consists of five phases: initiation, planning, execution, monitoring/control, and closure.
• Project management involves applying knowledge, skills, tools, and techniques to meet project requirements and satisfy stakeholders.
• Types of projects (e.g., product, service, construction) and modes of execution (e.g., BOOT, bilateral) vary based on funding, ownership, and scope.
• Real-world examples like Khimti-I Hydropower (BOOT model) and eSewa’s digital service rollout demonstrate how project management principles are applied in Nepal.

1. What is a Project?

A project is a temporary effort undertaken to create a unique product, service, or result. It has:

• A defined beginning and end.
• Progressive elaboration (details emerge as the project evolves).
• Resources (time, money, people) allocated to achieve specific objectives.

Key Characteristics of a Project

mindmap
  root((Project Characteristics))
    Temporary
    Unique Purpose
    Progressive Elaboration
    Constraints (Scope, Time, Cost, Quality, Risk)
    Stakeholders

IMAGE: "project management triangle (iron triangle)" | A visual representation of the trade-offs between scope, time, and cost in project management.

2. Project vs. Operations

Why the distinction matters?

• Projects are one-time efforts (e.g., launching a new app like Pathao’s bike-sharing service).
• Operations are continuous (e.g., NTC’s daily electricity distribution).

3. The Project Life Cycle

Every project follows a predictable life cycle with five phases:

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

Phase Breakdown

1. Initiation

   • Define project goals, stakeholders, and feasibility.
   • Example: Nepal Government’s "Provincial Road Network Expansion" starts with a feasibility study.

2. Planning

   • Develop a project management plan (scope, schedule, budget, risks).
   • Example: Daraz’s "Prime Delivery Service" plans logistics, marketing, and tech infrastructure.

3. Execution

   • Carry out the project plan (tasks, resource allocation).
   • Example: Himalayan Java’s new coffee plantation involves land prep, planting, and training.

4. Monitoring & Control

   • Track progress, manage changes, and ensure quality.
   • Example: Nabil Bank’s loan disbursement project monitors repayment rates and adjusts terms.

5. Closure

   • Finalize deliverables, document lessons learned, and handover.
   • Example: BOOT projects like Khimti-I transfer ownership to the government after 25 years.

4. Types of Projects

Projects can be classified based on objectives, funding, and execution mode:

A. By Nature of Work

B. By Execution Mode

## In the Real World

1. eSewa’s Digital Payment Rollout

   • Idea Used: Project Life Cycle (Planning → Execution → Monitoring)
   • How? eSewa’s expansion from Kathmandu to provinces required:
     • Planning: Partnering with banks (Nabil, Global IME) and tech firms.
     • Execution: App development, merchant onboarding, and marketing.
     • Monitoring: Tracking transaction volumes and fraud rates.

2. Khimti-I Hydropower (BOOT Model)

   • Idea Used: BOOT Project Structure
   • How? The $250 million project was funded by GMR Energy (India). The private sector:
     • Built the plant (24 MW capacity).
     • Operated it for 25 years.
     • Transferred ownership to the Nepal Government.
   • Challenge: Delays in land acquisition and regulatory approvals caused cost overruns.

3. Pathao’s Bike-Sharing Service

   • Idea Used: Fast-Track Project Execution
   • How? Pathao launched its bike-sharing pilot in Kathmandu in 6 months by:
     • Phased rollout (started with 500 bikes in Thapathali).
     • Partnerships with bike manufacturers (local Nepalese firms).
     • Agile monitoring (real-time app feedback to adjust routes).

5. Project Management: Roles and Responsibilities

Project management involves planning, executing, and closing projects efficiently. Key roles:

classDiagram
  class ProjectManager {
    +Defines scope, budget, timeline
    +Leads team and stakeholders
    +Monitors progress
  }
  class ProjectTeam {
    +Executes tasks
    +Reports to PM
  }
  class Stakeholders {
    +Provides input/feedback
    +Includes clients, sponsors, government
  }
  ProjectManager --> ProjectTeam : Manages
  ProjectManager --> Stakeholders : Communicates

Key Responsibilities of a Project Manager

• Scope Management: Ensuring the project delivers what was promised (e.g., NTC’s smart meter installation must cover all households).
• Time Management: Meeting deadlines (e.g., Daraz’s Black Friday sale prep).
• Cost Management: Staying within budget (e.g., Nepal Railway’s electrification project).
• Quality Management: Meeting standards (e.g., ISO-certified products at Himalayan Java).
• Risk Management: Identifying threats (e.g., supply chain disruptions for Pathao bikes).

6. Project Constraints (The Triple Constraint)

Every project operates under three key constraints:

pie
  title Project Constraints
  "Scope" : 33
  "Time" : 33
  "Cost" : 33

Trade-offs:

• Increase scope → May require more time/cost (e.g., adding solar panels to Khimti-I).
• Reduce time → May increase cost (e.g., hiring overtime labor for Daraz’s Black Friday).

7. Fast-Track vs. Traditional Projects

When to use fast-track?

• Urgent needs (e.g., COVID-19 vaccine distribution).
• Competitive advantage (e.g., Daraz beating Amazon in Nepal).

8. Case Study: Nepal’s Melamchi Drinking Water Project

Project Type: Infrastructure (BOOT Model) Funding: $250 million (ADB + Nepal Government) Challenges:

• Environmental concerns (ecological impact on Melamchi Lake).
• Political delays (land acquisition disputes).
• Technical hurdles (tunnel construction in Himalayas).

Lessons Learned:

• Stakeholder engagement is critical (involving local communities).
• Risk management must account for geopolitical factors (India-China relations affecting supply chains).
• Fast-tracking some phases (e.g., tunnel boring) helped meet deadlines.

## Exam Tip

1. Define Clearly

   • For questions like "What is a project?", use the PMBOK (Project Management Body of Knowledge) definition:

     "A project is a temporary endeavor undertaken to create a unique product, service, or result."

2. Compare and Contrast

   • For "Project vs. Operations", use a table (as shown above) to highlight differences.

3. Real-World Applications

   • Always tie theory to Nepal:
     • BOOT projects → Khimti-I, Melamchi.
     • Fast-track → Pathao, eSewa.
     • Constraints → NTC’s smart meter delays (cost vs. time).

4. Case Study Approach

   • If asked about project delays in Nepal, analyze:
     • Political instability (frequent government changes).
     • Bureaucracy (slow approvals).
     • Infrastructure gaps (poor road networks for supply chains).
   • Example Answer:

     "Projects in Nepal often face delays due to political interference (e.g., Melamchi’s land disputes) and bureaucratic hurdles (e.g., NTC’s slow procurement). Unlike global firms (e.g., Toyota’s just-in-time supply chain), Nepali projects lack streamlined processes, leading to cost overruns."

5. Diagrams Save Marks

   • Draw project life cycle, constraints triangle, or BOOT model to visually support answers.

Summary Checklist for Full Marks

✅ Define project, operations, and project management. ✅ Explain the 5-phase life cycle with examples. ✅ Differentiate BOOT, bilateral, and multilateral projects. ✅ Discuss fast-track vs. traditional with a Nepali case (Pathao/Daraz). ✅ Analyze constraints (scope, time, cost) with trade-offs. ✅ Critique why Nepali projects delay (politics, bureaucracy, infrastructure). ✅ Use visuals (tables, flowcharts, mindmaps) to explain concepts.