Project Management

---

Core Concepts and Terminology: Project and Project Management

• Project: A temporary endeavor undertaken to create a unique product, service, or result, characterized by a defined beginning and end, specific scope boundaries, and allocated financial and human resources.
• Project Management: The application of knowledge, skills, tools, and specialized techniques to project activities to meet or exceed project requirements and stakeholder expectations.
• Triple Constraints (Iron Triangle): The foundational triad of competing project parameters: Scope (deliverables and specifications), Time (schedule and milestone deadlines), and Cost (budget and resource expenditures), bound together by Quality. Changing any one parameter inevitably forces compromises in the other two.
• Temporary Endeavor: A defining characteristic signifying that every project has a definite start date and a definitive completion milestone (upon objective achievement or project termination). It does not mean the project deliverable is temporary.
• Progressive Elaboration: The iterative process of continuously refining, detailing, and improving project plans as more granular information and clearer specifications become available over time.
• Project Deliverable: Any unique, verifiable, and measurable product, capability, or result produced to complete a project phase or final deliverable.
• Project Stakeholder: Any individual, group, or organization that may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project.

---

1. Distinctive Characteristics of Projects

Projects are distinguished from standard organizational activities by seven core attributes:

1. Uniqueness: Every project creates a novel deliverable (e.g., constructing the Upper Tamakoshi Hydroelectric Dam or deploying a banking core software upgrade). Even if identical housing blueprints are used, site topography, geotechnical conditions, and labor teams differ.
2. Defined Life Cycle: Possesses clear chronological stages from conceptual initiation to formal handover and closure.
3. Interdisciplinary Cross-Functional Teamwork: Assembles specialists from diverse disciplines (civil engineers, financial analysts, legal experts, environmental scientists, software architects) who collaborate temporarily.
4. Single Point of Responsibility: The Project Manager holds ultimate operational and fiduciary accountability for project execution and milestone delivery.
5. Inherent Uncertainty and Risk: Because projects introduce novel solutions in dynamic environments, they operate under assumptions, external dependencies, and unpredictability.
6. Subcontracting and External Procurement: Major physical works and specialized services are contracted out to third-party vendors, demanding rigorous contract administration.
7. Customer or Client Specificity: Projects are executed to satisfy explicit requirements defined by a specific client (internal executive sponsor or external government ministry).

2. Projects vs Routine Operational Work

---

3. The Project Life Cycle Architecture

The project progresses through four universal sequential phases:

The Four Phases of the Project Life Cycle
[ Phase 1: Initiation ]  --> Project charter formulation, feasibility analysis, stakeholder identification
[ Phase 2: Planning ]    --> WBS creation, network diagrams (CPM), budget baseline, risk register
[ Phase 3: Execution ]   --> Deliverable production, team coordination, quality assurance, procurement
[ Phase 4: Closure ]     --> Final handover, client sign-off, contract settlement, lessons learned

1. Initiation Phase:
   • High conceptual uncertainty; resource consumption and staffing are low (typically 5% of total budget).
   • Core Activities: Formulating the Project Charter, conducting pre-feasibility and financial appraisal, appointing the Project Manager, and identifying primary stakeholders.
   • Milestone: Formal approval and signing of the Project Charter by the executive sponsor.
2. Planning Phase:
   • Effort ramps up as the team details the operational blueprint.
   • Core Activities: Decomposing scope via Work Breakdown Structure (WBS), developing critical path schedules (PERT/CPM), establishing the cost baseline, drafting the risk response plan, and defining quality metrics.
   • Milestone: Executive approval of the Project Management Plan and Performance Measurement Baseline (PMB).
3. Execution, Monitoring & Controlling Phase:
   • The peak expenditure and staffing period (consuming 70% to 85% of total project budget and labor hours).
   • Core Activities: Physical construction, procurement of machinery, software coding, executing quality audits, managing change requests, tracking progress via Earned Value Management (EVM), and managing team conflict.
   • Milestone: Completion of verified, tested project deliverables ready for customer commissioning.
4. Closure Phase:
   • Rapid demobilization of project resources; staffing drops to zero.
   • Core Activities: Resolving the punch/snag list, conducting formal handover to operations, closing vendor contracts, archiving project documentation, and writing the post-project lessons-learned evaluation.
   • Milestone: Formal client sign-off and release of project team.

---

4. Project Selection Models: Financial Appraisal Frameworks

Organizations have limited capital and must choose projects delivering optimal strategic and financial value:

1. Payback Period (PBP):
   • Measures the time required for cumulative net cash inflows to recover the initial capital investment outlay:

     Swipe to see the full formula↔

     $$PBP = \frac{\text{Initial Investment Outlay}}{\text{Annual Constant Cash Inflow}}$$
   • Limitation: Ignores the time value of money and cash flows generated after the payback period.
2. Net Present Value (NPV):
   • The discounted cash flow benchmark that discounts all future expected net cash flows to the present value using the firm’s required cost of capital ($k$):

     Swipe to see the full formula↔

     $$NPV = \sum_{t=1}^{n} \frac{CF_t}{(1 + k)^t} - CF_0$$
   • Decision Rule: Accept projects where $NPV > 0$; when choosing mutually exclusive projects, select the project with the highest positive NPV.
3. Internal Rate of Return (IRR):
   • The discount rate that equates the present value of expected future cash inflows exactly to the initial capital outlay ($NPV = 0$):

     Swipe to see the full formula↔

     $$\sum_{t=1}^{n} \frac{CF_t}{(1 + IRR)^t} - CF_0 = 0$$
   • Decision Rule: Accept the project if $IRR > k$ (where $k$ is the hurdle cost of capital).
4. Benefit-Cost Ratio (BCR / Profitability Index):
   • The ratio of the present value of future economic benefits to the present value of initial investment costs:

     Swipe to see the full formula↔

     $$BCR = \frac{\text{PV of Cash Inflows}}{\text{PV of Cash Outflows}}$$
   • Decision Rule: Accept projects where $BCR > 1.0$. Essential in public infrastructure projects evaluating socio-economic externalities.

---

5. Stakeholder Identification and Management: Mendelow’s Power-Interest Matrix

Project success depends on managing competing stakeholder interests using Mendelow’s matrix:

• High Power, High Interest (Key Players): Must be managed closely with frequent personal engagement and collaborative decision-making (e.g., project executive sponsor, primary funding donor like ADB/World Bank, affected local landowners demanding compensation).
• High Power, Low Interest (Keep Satisfied): Must be kept satisfied through formal compliance reporting without overwhelming them with operational trivia (e.g., regulatory government bodies like Ministry of Finance, environmental inspection departments).
• Low Power, High Interest (Keep Informed): Must be kept continuously informed through regular public townhalls and digital newsletters to maintain goodwill and prevent community opposition (e.g., local community members, environmental NGOs).
• Low Power, Low Interest (Monitor): Monitored through standard periodic public disclosures with minimal effort.

---

Non-Financial and Scoring Models for Project Selection

In corporate and public sector environments, financial return is not the sole criterion. Project managers evaluate initiatives using multi-criteria frameworks:

1. Non-Numeric (Qualitative) Selection Models:
   • The Sacred Cow: A project suggested by a powerful, high-ranking executive (e.g., the CEO or board chairman). The project is initiated based on personal conviction or corporate vanity rather than formal empirical feasibility.
   • The Operating Necessity: A project required to keep the facility or system operating (e.g., replacing a flooded drainage pump or damaged electrical substation). Financial payback is irrelevant because refusal to execute shuts down the entire enterprise.
   • The Competitive Necessity: A project required to maintain competitive parity in the marketplace (e.g., a commercial bank launching mobile banking app features because every competing Class ‘A’ bank offers them).
   • Comparative Benefit Model: Selecting projects through subjective panel ranking (e.g., Q-sort methodology).
2. The Weighted Scoring Model (Multi-Attribute Decision Matrix):
   • A structured quantitative model that assigns percentage weights ($w_i$) to multiple strategic criteria ($\sum w_i = 1.0$ or $100\%$) and scores candidate projects ($s_{ij}$) on a standardized scale (e.g., 1 to 10).

Solved Illustrative Problem: Weighted Scoring Model

An infrastructure investment conglomerate in Kathmandu is evaluating three candidate project proposals with an authorized investment fund of NPR 500,000,000:

• Project Alpha: Solar photovoltaic energy generation park.
• Project Beta: Cold-storage warehouse logistics facility.
• Project Gamma: Commercial business hotel and convention center.

The executive selection committee establishes four strategic evaluation criteria with assigned weights:

• Alignment with National Infrastructure Priorities ($w_1 = 0.35$)
• Expected Financial Return and Payback ($w_2 = 0.30$)
• Environmental and Social Sustainability ($w_3 = 0.20$)
• Operational and Technical Implementation Feasibility ($w_4 = 0.15$)

The evaluation committee evaluates and scores the three projects on a 1–10 scale:

Weighted Score Calculation ($\sum w_i \times s_{ij}$):

• Project Alpha:

  Swipe to see the full formula↔

  $$\text{Score} = (0.35 \times 9.0) + (0.30 \times 6.0) + (0.20 \times 9.5) + (0.15 \times 8.0) = 3.15 + 1.80 + 1.90 + 1.20 = \mathbf{8.05}$$
• Project Beta:

  Swipe to see the full formula↔

  $$\text{Score} = (0.35 \times 7.0) + (0.30 \times 8.0) + (0.20 \times 7.5) + (0.15 \times 8.5) = 2.45 + 2.40 + 1.50 + 1.275 = \mathbf{7.625}$$
• Project Gamma:

  Swipe to see the full formula↔

  $$\text{Score} = (0.35 \times 6.0) + (0.30 \times 9.0) + (0.20 \times 4.0) + (0.15 \times 7.0) = 2.10 + 2.70 + 0.80 + 1.05 = \mathbf{6.65}$$

Decision: Project Alpha achieves the highest aggregate weighted score (8.05), driven by strong national policy alignment and environmental sustainability, making it the recommended capital commitment.

Organizational Project Management Maturity: OPM3 and CMMI Frameworks

Enterprises do not develop sophisticated project execution capabilities overnight. They progress through standardized maturity levels:

1. Level 1 (Initial / Ad-Hoc): Disorganized, chaotic workflows. Project success depends entirely on heroic individual efforts rather than organizational systems; budgets and schedules are routinely exceeded.
2. Level 2 (Repeatable / Managed): Basic project management processes (cost estimating, scheduling, baseline tracking) are established and practiced across major projects.
3. Level 3 (Defined / Standardized): Organization-wide standard operating procedures, documentation templates, and WBS guidelines are formalized and integrated into a centralized Project Management Office (PMO).
4. Level 4 (Quantitatively Managed): Detailed empirical project performance metrics are collected, analyzed via statistical process control, and monitored through digital dashboards.
5. Level 5 (Optimizing / Continuous Improvement): The organization continuously optimizes project processes through automated lessons-learned repositories, agile experimentation, and predictive analytics.

Comparative Analysis and Structural Distinctions: Project and Project Management

Project Management & Analytical Focus: In TU examinations, candidates often describe project management purely as “general management applied to building things” without defining the Triple Constraints, fail to explain why the Project Life Cycle expenditure peaks during the Execution phase rather than Planning, confuse Payback Period with Net Present Value, or omit stakeholder classification frameworks, costing up to 5 marks on foundational 10-mark questions.#### Regulatory and Practical Application Context in Nepal In the contemporary Nepalese corporate landscape, applying the principles of Project and Project Management requires continuous adherence to statutory mandates issued by regulatory authorities such as Nepal Rastra Bank, the Securities Board of Nepal (SEBON), and the Inland Revenue Department. Enterprises that establish disciplined internal control systems, transparent documentation, and periodic compliance reviews successfully safeguard organizational solvency while driving sustainable commercial expansion.

---

Paper Khoj independent study notes — unreviewed draft, not affiliated with Tribhuvan University.