PROJECT MANAGEMENT

Complete Study Guide

All Five Modules • University Examination Level

Module I: Introduction | Module II: Planning & Scheduling

Module III: Appraisal & Financing | Module IV: Implementation & Control
Module V: Contemporary Issues & Case Studies

Comprehensive • Illustrated • Formula-Rich • Case Study Enhanced

Project Management — Complete Study Guide Page 1

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

■ Table of Contents
Module Topics Covered Key Learning

Concept & Characteristics of Projects Project Life Cycle Phases

Remembering
I Introduction Feasibility Analysis (Market, Technical, Financial, Environmental)
Understanding
SCBA · Project Manager Role · Org Structures

II Planning & WBS · Gantt Charts · Network Analysis PERT & CPM · Time-Cost
Applying Analyzing
Scheduling Trade-off Crashing · Resource Optimization

III Appraisal ROI · NPV · IRR · Payback · PI Sensitivity Analysis · Sources of

Applying Evaluating
& Financing Finance WACC · Capital Budgeting

IV Implement
EVM · Scope Creep · Risk Management Quality Management ·
ation & Analyzing Evaluating
Project Closure Project MIS · Project Audit
Control

V Contempor Waterfall · Agile · Lean Sustainable PM · Software Tools Case

Creating Evaluating
ary Issues Studies from IT, Construction, Govt.

Project Management — Complete Study Guide Page 2

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

■ MODULE I

Introduction to Project Management (8 Lectures)

1. Concept and Characteristics of Projects

A project is a temporary, unique, goal-oriented endeavor undertaken to create a specific product, service, or
result within defined constraints of time, cost, scope, and quality. Every project has a definite beginning and a
definite end. When objectives are achieved — or when it is determined they cannot be achieved — the project
ends.

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

ISO 21500: "A project consists of a unique set of processes consisting of coordinated and controlled activities
with start and finish dates, undertaken to achieve a project objective."

Key Characteristics of Projects:

Characteristic Detailed Explanation

Every project has a definite start and end. 'Temporary' does not mean short —
Temporariness
some projects span decades (metro rail, dams), but they all conclude.

Each project produces a unique deliverable. Even similar projects (two bridges)
Uniqueness
differ in location, team, materials, and environment.

Projects are undertaken to achieve specific, measurable objectives — a product,

Goal-Oriented
system, building, or policy. Without a clear goal, a project has no direction.

Projects must be completed within defined constraints: Time, Cost, and Scope
Resource Constrained (the Triple Constraint). Quality, Risk, and Resources are additional modern
constraints.

Projects are developed in steps. Initially the scope may be broadly defined; as
Progressive Elaboration
the project progresses more details are elaborated and refined.

Projects draw expertise from multiple departments — Engineering, Finance, HR,

Cross-Functional
Marketing — forming temporary cross-functional teams.

Because projects are unique and involve future activities, they inherently carry
Risk and Uncertainty
uncertainty. Risk is highest at the start and decreases as unknowns are resolved.

Interdependency of Project activities are interconnected — completion of one task may depend on
Tasks another. These dependencies must be managed carefully.

Projects are change agents — they transform a current state into a desired future
Involves Change
state. Change management is therefore integral to project management.

Every project involves multiple stakeholders — individuals or groups who are

Has Stakeholders
affected by or can affect the project outcome.

Project vs. Operations:

Project Management — Complete Study Guide Page 3

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Aspect Project Operations

Nature Temporary, finite Ongoing, continuous

Output Unique product/service Repetitive, standardized

Goal Achieve objective then close Sustain and improve business

Team Temporary, assembled Permanent, stable

Funding One-time capital budget Operational budget

Measurement Success vs. project objectives Efficiency, throughput, quality

Examples Building a bridge, ERP implementation Manufacturing, payroll processing

2. Project Life Cycle Phases

The Project Life Cycle (PLC) is the sequence of phases through which a project passes from initiation to
completion. It provides structure, a common framework, facilitates decision-making at phase-gate reviews, and
enables better resource planning.

Phase 1: Purpose: Formally authorize the project and define it at a high level.
INITIATION

Key Activities: • Identify business problem/opportunity the project addresses

• Perform high-level feasibility assessment
• Define project at broad level — purpose, objectives, deliverables
• Identify project sponsor and key stakeholders
• Appoint the Project Manager
• Develop the Project Charter — formal document authorizing the project

Key Outputs: Project Charter · Stakeholder Register · Preliminary Scope Statement

Phase 2: Purpose: Establish the detailed roadmap for achieving objectives. Most
PLANNING comprehensive phase.

Key Activities: • Define and document the full project scope

• Create the Work Breakdown Structure (WBS)
• Sequence project activities and identify dependencies
• Estimate durations, resources, and costs for each activity
• Develop the project schedule (Gantt chart, PERT/CPM network)
• Identify risks and plan mitigation strategies
• Create the comprehensive Project Management Plan

Key Outputs: Project Management Plan · WBS · Schedule Baseline · Cost Baseline · Risk Register

Project Management — Complete Study Guide Page 4

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Phase 3: Purpose: Implement the project plan and produce the project deliverables.
EXECUTION

Key Activities: • Direct and manage project work

• Acquire, develop, and lead the project team
• Manage stakeholder engagement and communications
• Perform quality assurance activities
• Procure materials, equipment, and services from vendors
• Produce the project deliverables as defined in scope

Key Outputs: Project Deliverables · Work Performance Data · Change Requests

Phase 4: Purpose: Track, review, and regulate the progress and performance of the
MONITORING & project (runs concurrently with Execution).
CONTROL

Key Activities: • Measure project performance using KPIs and EVM metrics
• Compare actual progress with the project baseline
• Identify variances and analyze root causes
• Forecast future performance and project completion
• Manage the Change Control process
• Control scope, schedule, cost, and quality

Key Outputs: Work Performance Reports · Change Log · Updated Plans and Baselines

Phase 5: Purpose: Formally complete and close the project.

CLOSURE

Key Activities: • Verify all deliverables completed to customer satisfaction

• Obtain formal written acceptance from client/sponsor
• Close all procurement contracts and settle vendor payments
• Release project team members and all resources
• Archive all project records and documentation
• Document lessons learned; conduct post-project review

Key Outputs: Final Project Report · Lessons Learned Register · Closed Contracts

■ Risk is HIGHEST at initiation and decreases as the project progresses. Cost of changes INCREASES
dramatically as the project advances.

3. Importance and Scope of Project Management

Why Organizations Need Project Management:

• Clear Strategic Alignment — Projects aligned with organizational strategy maximize ROI on investments
• Timely Delivery — Scheduling tools (Gantt, PERT, CPM) enable realistic timelines and dependency
management
• Budget Adherence — Cost estimation and EVM enable organizations to forecast and control spending
• Risk Reduction — Proactive risk identification, analysis, and response prevent project failures
• Quality Assurance — Quality planning, QA, and QC ensure deliverables meet defined standards
• Resource Optimization — Resource planning and leveling maximize efficiency of people and equipment
• Stakeholder Satisfaction — Communication plans and engagement strategies manage expectations
• Knowledge and Learning — Lessons learned accumulate organizational wisdom for future projects

Project Management — Complete Study Guide Page 5

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

• Accountability and Governance — Clear roles, change control, and audit trails ensure accountability
• Competitive Advantage — PMI Pulse 2020: High-PM-maturity organizations complete 89% of projects
successfully vs. 36% for low-maturity organizations

Ten PMBoK Knowledge Areas:

# Knowledge Area Core Focus

Coordinating all aspects — project charter, management plan, change

1 Integration Management
control

Defining what is and is not included — requirements, WBS, scope

2 Scope Management
control

Planning and controlling time — activity sequencing, PERT/CPM,

3 Schedule Management
schedule control

Budgeting and controlling expenditures — estimation, cost baseline,

4 Cost Management
EVM

5 Quality Management Ensuring deliverables meet standards — QA, QC, quality tools

Managing human and physical resources — acquisition,

6 Resource Management
development, conflict resolution

7 Communications Management Planning and managing project information flow to all stakeholders

8 Risk Management Identifying, analyzing, and responding to project uncertainties

9 Procurement Management Managing external contracts, vendors, and make-or-buy decisions

10 Stakeholder Management Identifying and engaging all stakeholders throughout the project

4. Project Identification and Formulation

Project Identification is the process of recognizing potential investment opportunities. Sources include:
• Government plans and policies (National Infrastructure Pipeline, Smart Cities Mission)
• Market demand analysis — gaps between current supply and potential demand
• Technological innovation (AI, renewable energy, electric vehicles, biotechnology)
• Natural resource endowments (minerals, water, agricultural land, coastline)
• Socioeconomic problems — unemployment, poverty, lack of healthcare/education
• Competitive pressures — responding to competitor product launches or innovations
• Customer feedback and Voice of the Customer (VoC) research
• R&D; and innovation labs — experimentation and prototyping

Project Formulation Steps:

St
Name Description
ep

Quick, low-cost assessment — market potential, technical outline, rough

1 Pre-Feasibility Study financial estimates, preliminary environmental screening. Decides whether
full feasibility is warranted.

Project Management — Complete Study Guide Page 6

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

St
Name Description
ep

In-depth, multi-dimensional study covering market, technical, financial,

2 Detailed Feasibility Study economic, social, environmental, and legal aspects. Basis for investment
decisions.

Comprehensive master document: executive summary, market analysis,

Detailed Project Report
3 technical description, cost estimates, financial projections, EIA, risk
(DPR)
analysis, implementation schedule.

Independent evaluation by lenders, government, or investment committees

4 Project Appraisal covering technical feasibility, financial viability, managerial capability, and
economic justification.

5 Investment Decision Based on appraisal findings: approve, modify, or reject the project.

5. Project Feasibility Analysis

1. Market Feasibility
Determines whether there is sufficient, sustainable demand for the project's output at a price that covers costs.
• Demand Analysis: Estimate current demand, historical trends, project future demand using Trend Analysis,
Regression Analysis, Market Surveys, Delphi Method
• Supply Analysis: Assess current supply (domestic + imports), identify competitors, estimate supply gaps
• Market Share and Sales Forecast: Based on competition, pricing, distribution, marketing strategy
• Pricing Strategy: Competitive pricing, cost-plus pricing, value-based pricing; elasticity of demand
• SWOT Analysis and Porter's Five Forces: Five competitive forces analysis
• Distribution: How will the product reach customers — direct, distributors, e-commerce, retail?

2. Technical Feasibility
Determines whether the project can be executed using available/acquirable technology and whether the
production system will be efficient.
• Product/Service Specifications: Dimensions, materials, quality standards, regulatory compliance
• Production Process and Technology: Process flowchart from raw material to finished product; comparison
of technology alternatives
• Capacity Planning: Installed vs. utilized capacity; production at minimum, normal, and maximum levels;
economies of scale
• Plant Location Analysis: Proximity to raw materials, labor supply, markets, infrastructure, government
incentives, land cost
• Plant Layout: Efficient arrangement of machinery, storage, utilities, and workspaces
• Raw Materials: Sources, availability, quality, cost; import dependency risks
• Manpower: Skill levels needed, local labor availability, training requirements

3. Financial Feasibility
Determines whether the project will generate sufficient financial returns to justify the investment.
• Capital Cost Estimation: Land, buildings, plant and machinery, pre-operative expenses, contingency
(5-10%)
• Working Capital: Inventories + Receivables + Cash - Creditors
• Means of Financing: Equity, debt, government grants; Debt-Equity ratio typically 2:1 to 3:1
• Revenue Projections: Sales volumes × selling prices; ramp-up over years as capacity utilizes

Project Management — Complete Study Guide Page 7

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

• Profitability Projections: Projected P&L; for 5-10 years; EBITDA, PBT, PAT margins
• Break-Even Analysis: Fixed Costs ÷ (Selling Price - Variable Cost per unit)
• Investment Appraisal: NPV, IRR, Payback Period, PI (detailed in Module III)

4. Environmental Feasibility
Determines whether the project complies with environmental laws and whether its impacts are acceptable.
• Environmental Impact Assessment (EIA): Screening → Scoping → Baseline Study → Impact Prediction →
Mitigation Planning → EIA Report → Approval
• Air Quality: Emissions and dust from construction and operations
• Water Quality: Effluent treatment, groundwater impact, water consumption
• Solid and Hazardous Waste: Management systems and disposal
• Ecological Impact: Forest clearing, wildlife corridors, biodiversity protection
• Displacement: Resettlement and rehabilitation of affected communities
• Carbon Footprint: Climate change impact and mitigation

6. Social Cost Benefit Analysis (SCBA)

SCBA (also called Economic Analysis) is a systematic evaluation of a project's social benefits and costs to
society as a whole, not just to the private investor. It asks: Does the project create net value for society, even if
it may not be commercially profitable?

Why Market Prices Are Inadequate:

• Taxes and subsidies distort private costs from social values
• Monopolies set prices above marginal cost
• Externalities — costs or benefits not captured in market prices (pollution, employment spillovers)
• Underpriced labor — in regions with high unemployment, market wage overstates social opportunity cost
• Undervalued foreign exchange — official rates may not reflect true scarcity of foreign currency

Key SCBA Concepts:

Concept Explanation

In high-unemployment regions, hiring an unskilled worker costs society less

Shadow Wage Rate
than the market wage. SWR = Market Wage × Conversion Factor (< 1 for
(SWR)
unskilled in developing countries)

Shadow Exchange Rate If official exchange rate undervalues foreign currency, imported inputs cost
(SER) more in social terms. SER corrects for this distortion.

Rate used to discount future social benefits and costs. Lower than private rates
Social Discount Rate — society values future consumption more; governments have longer time
horizons.

Negative (pollution, congestion — add to social cost) or Positive (training

Externalities
workers, reducing transport costs — add to social benefit). Not in market prices.

Benefit consumers derive beyond what they pay. Infrastructure reducing travel
Consumer Surplus
time creates consumer surplus — a genuine social benefit.

Income Distribution Give greater weight to benefits flowing to lower-income groups — reflecting
Weights societal preference for equity.

Economic Rate of Return IRR computed using shadow prices instead of market prices. Used by World
(ERR) Bank and ADB to evaluate public investments.

Project Management — Complete Study Guide Page 8

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

SCBA Methodologies:
Methodology Origin Numeraire Key Feature

Three-stage: Financial →
Domestic consumption at
UNIDO Approach UNIDO (1972) Economic Efficiency → Social
domestic prices
(income distribution)

Uses world market (border)

Uncommitted social
Little-Mirrlees (L-M) OECD (1969) prices as shadow prices; SCF
income at border prices
converts non-traded goods

Extension of L-M with explicit

World Bank / Border prices + distribution
World Bank income distribution weights by
Squire-van der Tak weights
income level

Financial Analysis vs. SCBA:

Aspect Financial Analysis Social CBA

Perspective Private investor Society / Government

Prices Used Market prices Shadow (accounting) prices

Objective Profit maximization Social welfare maximization

Employment, environment, equity,

Includes Revenue, costs
externalities

Discount Rate Cost of capital (market rate) Social discount rate (lower)

Output Measure NPV, IRR (financial) ENPV, ERR (economic)

7. Role of Project Manager and Organization Structures

PMI Talent Triangle — Three Competency Domains:

Competency Domain Key Skills and Behaviors

Mastery of scheduling, cost management, risk management, quality

Technical Project Management management; proficiency with MS Project/Primavera/Jira; PERT/CPM;
WBS; EVM; project lifecycle and governance

Motivating and inspiring diverse teams; building relationships; emotional

intelligence (self-awareness, empathy, social skills); influencing without
Leadership
authority; conflict resolution and negotiation; building psychological
safety

Understanding business environment and industry context; aligning

Strategic & Business
projects with organizational strategy; benefits realization; financial
Management
acumen; portfolio thinking

Ten Key Roles of a Project Manager:

Role Description

Develops the project plan, WBS, schedule, and budget; defines 'how' the project will be
Planner
executed

Project Management — Complete Study Guide Page 9

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Role Description

Organizer Assembles and organizes the project team; assigns roles and responsibilities

Motivates, guides, and leads the team toward project goals; creates vision and
Leader
psychological safety

Manages information flow between stakeholders; spends 70-90% of time in

Communicator
communication activities

Risk Manager Identifies, analyzes, and mitigates project risks; maintains the Risk Register

Decision-Maker Makes timely decisions to keep the project on track; balances competing constraints

Manages scope changes through formal change control; adapts the project to changing
Change Agent
conditions

Negotiates with vendors, clients, team members, and functional managers for
Negotiator
resources

Monitors progress, measures performance using EVM, and takes corrective action
Controller
when variances occur

Ensures proper project closure, documentation, lessons learned, and handover of

Closer
deliverables

Project Organization Structures:

Resource Key
Structure PM Authority Best For Key Advantage
Control Disadvantage

Little/None — Routine Deep technical Weak PM; poor

Functional
Functional acts as operations, small expertise; clear cross-functional
Manager
coordinator internal projects career paths coordination

Organizations Resource
Mostly PM has limited
with many small flexibility;
Weak Matrix Low Functional power; dual loyalty
projects sharing functional
Manager of team
resources heavily efficiency

Product
Balance of PM Most complex to
Balanced development,
Shared/Equal Shared and functional manage; conflict
Matrix technology
authority prone
companies

Engineering, PM has real Functional

Strong Matrix High-Very High Mostly PM pharmaceutical, authority; good managers may
IT projects coordination lose influence

Construction, Clear
Resource
Project defense, accountability;
Projectized Total duplication; team
Manager aerospace, fast decisions;
anxiety at end
large-scale strong PM

Large Complex
Flexibility to use
Varies by organizations governance;
Composite Mixed best structure for
project type with diverse inconsistent
each project
project types standards

Project Management — Complete Study Guide Page 10

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

■ MODULE II

Project Planning and Scheduling (10 Lectures)

1. Work Breakdown Structure (WBS)

The WBS is a hierarchical decomposition of the total project scope into smaller, more manageable
components (work packages). It is the foundation of all project planning — the basis for schedule, cost,
resource, risk, and communications plans.

WBS Design Principles:

Principle Explanation

The WBS must capture 100% of the work required — no more, no less. If a
100% Rule
deliverable is not in the WBS, it is out of scope.

No work package should overlap with another. Overlap creates confusion about
Mutually Exclusive
responsibility and double-counting in estimates.

Deliverable-Oriented WBS elements should be deliverables (nouns), not activities (verbs). 'Design
(Nouns) Document' not 'Prepare Design'. Activity definition comes later.

Work packages should be at least 8 hours (meaningful, trackable) and no more

8/80 Rule
than 80 hours (estimable, manageable) of work.

Progressive Start with the project at top level, decompose into phases/major deliverables, then
Decomposition further until work packages of manageable size are reached.

Each element gets a unique WBS code ([Link]) for cost coding, scheduling, and
Unique Coding
progress tracking.

Hospital Construction WBS Example:

1. HOSPITAL CONSTRUCTION PROJECT 1.1 Project Management 1.1.1 Project Planning | 1.1.2
Monitoring & Control | 1.1.3 Closure 1.2 Site Preparation 1.2.1 Land Surveys & Soil Testing
| 1.2.2 Site Clearance | 1.2.3 Temp Utilities 1.3 Civil Works 1.3.1 Foundation: [Link]
Excavation | [Link] Foundation Laying | [Link] Waterproofing 1.3.2 Structural Frame:
[Link] Columns & Beams | [Link] Slab | [Link] Staircase 1.3.3 External Envelope: [Link]
Brickwork | [Link] Roofing | [Link] Cladding 1.4 MEP Work 1.4.1 Electrical | 1.4.2 HVAC |
1.4.3 Plumbing & Fire | 1.4.4 Medical Gas 1.5 Interior Works 1.5.1 Partitions & Doors |
1.5.2 Flooring | 1.5.3 Painting | 1.5.4 False Ceiling 1.6 Medical Equipment 1.6.1
Procurement | 1.6.2 Installation | 1.6.3 Testing & Acceptance 1.7 External Works 1.7.1
Landscaping | 1.7.2 Parking & Roads | 1.7.3 Boundary Wall 1.8 Commissioning and Handover
1.8.1 Systems Testing | 1.8.2 Regulatory Inspections | 1.8.3 Staff Training | 1.8.4
Handover

2. Gantt Charts and Project Scheduling Tools

A Gantt Chart is a horizontal bar chart displaying project tasks against a timeline. Developed by Henry L. Gantt
(~1910–1915), it remains the most widely used project scheduling tool globally.

Project Management — Complete Study Guide Page 11

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Feature / Tool Description

Task List (Y-axis) All project activities listed vertically

Timeline (X-axis) Calendar dates — days, weeks, or months

Bars Each bar shows task start date, end date, and duration

Dependency Arrows Lines connecting bars show predecessor-successor relationships

Milestones (◆) Key events with zero duration — checkpoints, approvals, deliveries

% Complete Indicator Bar fill or separate indicator showing progress

Critical Path Highlight Critical path activities highlighted in red or bold

Resource Assignment Resource-loaded Gantt shows who works on which task

Tracking Gantt Compares planned bars with actual completion — shows variances

Software Tools Comparison:

Tool Type Key Features Best For

Gantt, CPM, resource leveling, EVM, Corporate projects,

MS Project Traditional
baselines construction, engineering

Large-scale scheduling, multi-project, Large infrastructure, oil & gas,

Primavera P6 Traditional
EPC defense

Scrum/Kanban boards, backlog, sprint Software development, digital

Jira Agile
tracking, burndown products

Kanban boards, card-based visual

Trello Agile/Lean Small teams, simple workflows
task management

Task management, timelines, Marketing, operations,

Asana Hybrid
portfolios, dashboards cross-functional teams

Highly customizable dashboards, Diverse industries, flexible

[Link] Hybrid
automations, integrations workflows

Spreadsheet-like with Gantt, Teams familiar with

Smartsheet Hybrid
automation, resource management Excel-style interfaces

3. Network Analysis: PERT and CPM

CPM — Critical Path Method

Developed by DuPont (1957) for plant maintenance. Uses deterministic (known, single) duration estimates.

Key CPM Formulas:

Earliest Finish (EF)

EF = ES + Duration

Latest Start (LS)

LS = LF − Duration

Total Float

Project Management — Complete Study Guide Page 12

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Total Float = LS − ES = LF − EF

Free Float
Free Float = ES(successor) − EF(activity)

Critical Path
Longest path through network = Minimum Project Duration (all activities have zero float)

CPM Worked Example:

Activ Predeces Duration
ES EF LS LF Total Float Critical?
ity sor (days)

A — 3 0 3 0 3 0 YES

B A 7 3 10 3 10 0 YES

C A 10 3 13 5 15 2 No

D B 5 10 15 10 15 0 YES

E C, D 8 15 23 15 23 0 YES

F E 4 23 27 25 29 2 No

G E 6 23 29 23 29 0 YES

H F, G 9 29 38 29 38 0 YES

I H 2 38 40 38 40 0 YES

■ Critical Path: A → B → D → E → G → H → I = 40 days. Activities C and F have 2 days of float.

PERT — Program Evaluation and Review Technique

Developed by US Navy (1958) for the Polaris missile project. Uses probabilistic (three-estimate) durations for
uncertain projects.

Expected Duration (te)

te = (a + 4m + b) / 6 where a = optimistic, m = most likely, b = pessimistic

Variance (σ²)
σ² = [(b − a) / 6]²

Standard Deviation (σ)

σ = (b − a) / 6

Project Variance (σ²_cp)

σ²_cp = Sum of variances of all critical path activities

Probability (Z-score)
Z = (Scheduled Date − Expected Duration) / σ_cp → Use standard normal table

PERT Worked Example:

Project Management — Complete Study Guide Page 13

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Pred
Activity to (a) tm (m) tp (b) te = (a+4m+b)/6 σ² = [(b-a)/6]²
.

A — 1 3 5 3.0 0.44

B A 3 6 9 6.0 1.00

C A 4 7 16 7.67 4.00

D B 2 4 12 4.67 2.78

E C, D 2 5 8 5.0 1.00

F E 1 2 3 2.0 0.11

Critical Path: A → B → D → E → F = 3.0 + 6.0 + 4.67 + 5.0 + 2.0 = 20.67 days

σ²_cp = 0.44 + 1.00 + 2.78 + 1.00 + 0.11 = 5.33 | σ_cp = √5.33 = 2.31 days

Probability of completing in 23 days: Z = (23 − 20.67) / 2.31 = 1.01 → P ≈ 84.4%

Probability of completing in 18 days: Z = (18 − 20.67) / 2.31 = −1.15 → P ≈ 12.5%

PERT vs. CPM Comparison:

Feature PERT CPM

Probabilistic (3 estimates: optimistic, most likely, Deterministic (1 known

Duration Estimate
pessimistic) estimate)

Time and Cost trade-off

Focus Time management under uncertainty
analysis

Low (construction,
Uncertainty High (R&D;, new development, defense)
engineering, maintenance)

Critical path, float, crash

Output Probability of meeting schedule
analysis

DuPont, 1957, plant

Origin US Navy, 1958, Polaris missile program
maintenance

Built-in — time-cost trade-off

Cost Analysis Not inherent — time focused
and crashing

4. Time-Cost Trade-off and Crashing

As project duration is reduced (crashing), direct costs increase (more resources needed) while indirect
costs decrease (overheads, penalties reduced). The optimal duration minimizes total cost (direct +
indirect).

Cost Slope
Cost Slope = (Crash Cost − Normal Cost) / (Normal Time − Crash Time) [Cost per day saved]

Total Cost
Total Cost = Direct Costs + Indirect Costs + Penalty Costs − Incentive Payments

Crashing Procedure:
• Step 1: Identify all paths and find the current Critical Path
• Step 2: List Cost Slopes for all critical activities — crash cheapest first

Project Management — Complete Study Guide Page 14

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

• Step 3: Crash the critical activity with the LOWEST cost slope by 1 day
• Step 4: Re-calculate all path lengths — identify new critical path(s)
• Step 5: Continue crashing until target duration is achieved OR total cost starts rising
• Step 6: Stop when any further crashing costs more in direct costs than it saves in indirect costs

Crashing Numerical Example:

Normal Crash Critic
Activity Normal Cost Crash Cost Cost Slope
Time Time al?

A 6 days ■12,000 4 days ■16,000 ■2,000/day YES

B 8 days ■20,000 6 days ■28,000 ■4,000/day YES

C 4 days ■8,000 3 days ■11,000 ■3,000/day No

D 5 days ■10,000 3 days ■16,000 ■3,000/day YES

Indirect Cost = ■3,000/day | Normal Duration = 19 days

Step 1: Crash A (lowest slope ■2,000/day) by 2 days → Duration: 17 days | Extra direct: ■4,000 | Indirect
saving: ■6,000 | Net saving: ■2,000 ✓

Step 2: Crash D (slope ■3,000/day) by 2 days → Duration: 15 days | Extra direct: ■6,000 | Indirect saving:
■6,000 | Net: ■0 (indifferent)

Step 3: Crash B (slope ■4,000/day) → Extra direct ■4,000/day > Indirect saving ■3,000/day | STOP — net
loss

■ Optimal Project Duration = 15 days. Crashing beyond this point increases total project cost.

5. Resource Optimization
Effect on
Technique Definition When to Use
Duration

Adjust schedule to eliminate

May extend When resource availability
Resource Leveling over-allocation by delaying
project duration is the binding constraint
non-critical activities into their float

When schedule deadline is

Resource Adjust schedule within available Does NOT
fixed but want smoother
Smoothing float to reduce peak demands extend duration
resource use

Perform activities in parallel that When time is critical;

Fast Tracking Reduces duration
were originally sequential increases risk

When deadline must be met

Add resources to critical activities
Crashing Reduces duration and budget allows extra
to reduce their duration
cost

Project Management — Complete Study Guide Page 15

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

■ MODULE III

Project Appraisal and Financing (6 Lectures)

1. Project Selection Criteria

Financial appraisal evaluates whether a project creates value and is worth investing in. Multiple methods are
used — each captures a different dimension of financial performance.

Comprehensive Numerical Example:

Initial Investment = ■5,00,000 | Required Rate of Return = 12% | Project Life = 5 years

Net Cash Flow PV Factor Present Value PV Factor

Year PV @16% (■)
(■) @12% (■) @16%

1 1,00,000 0.893 89,300 0.862 86,200

2 1,50,000 0.797 1,19,550 0.743 1,11,450

3 2,00,000 0.712 1,42,400 0.641 1,28,200

4 1,75,000 0.636 1,11,300 0.552 96,600

5 1,50,000 0.567 85,050 0.476 71,400

TOT
7,75,000 — 5,47,600 — 4,93,850
AL

1. Payback Period (PBP):

Cumulative CF: Year 1: ■1,00,000 | Year 2: ■2,50,000 | Year 3: ■4,50,000

Remaining after Year 3 = ■5,00,000 − ■4,50,000 = ■50,000

PBP
PBP = 3 + (50,000 / 1,75,000) = 3 + 0.286 = 3.29 years → ACCEPT (if target < 4 years)

2. Net Present Value (NPV):

NPV
NPV = Total PV − Investment = ■5,47,600 − ■5,00,000 = +■47,600 → ACCEPT (NPV > 0)

3. Internal Rate of Return (IRR):

At 12%: NPV = +■47,600 | At 16%: NPV = −■6,150

IRR
IRR = 12 + [47,600 / (47,600 + 6,150)] × (16 − 12) = 12 + (0.885 × 4) = 15.54% → ACCEPT (15.54% >
12%)

4. Profitability Index (PI):

PI
PI = 5,47,600 / 5,00,000 = 1.095 → ACCEPT (PI > 1)

5. Return on Investment (ROI):

Project Management — Complete Study Guide Page 16

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

ROI
Avg Annual CF = 7,75,000 / 5 = ■1,55,000 | ROI = (1,55,000 / 5,00,000) × 100 = 31% → ACCEPT

Method Result Decision Key Limitation

Payback
3.29 years ACCEPT Ignores TVM; ignores cash flows beyond payback
Period

NPV +■47,600 ACCEPT Requires accurate cash flow and discount rate estimates

IRR 15.54% ACCEPT May give multiple IRRs; scale insensitive

PI 1.095 ACCEPT Best for capital rationing; ignores absolute size

ROI 31% ACCEPT Ignores TVM; uses accounting profit not cash flow

Method Comparison Matrix:

Criterion PBP ROI NPV IRR PI

Accounts for Time Value of Money No No YES YES YES

Considers All Cash Flows No Yes YES YES YES

Simple to Calculate Yes Yes No No No

Best for Capital Rationing No No No No YES

Maximizes Shareholder Wealth No No YES Partial YES

Multiple IRR Problem N/A N/A N/A Possible N/A

2. Investment Risk and Sensitivity Analysis

Sensitivity Analysis — Numerical Example:

Testing how NPV changes if annual cash flows change (Base Case NPV = +■47,600):

Change in Cash
Total PV (■) NPV (■) Interpretation
Flows

+20% 6,57,120 +1,57,120 Strong positive — project highly profitable

+10% 6,02,360 +1,02,360 Positive — comfortably viable

0% (Base Case) 5,47,600 +47,600 Base — accept project

NPV turns NEGATIVE — project

−10% 4,92,840 −7,160
becomes unviable

−20% 4,38,080 −61,920 Significantly negative — reject

■ Project is HIGHLY SENSITIVE to revenue changes. Even a 10% revenue decline makes NPV negative.
Rigorous demand forecasting and market research are critical.

Types of Risk Analysis:

Project Management — Complete Study Guide Page 17

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Method Description Output

Changes one variable at a time Sensitivity table; Tornado diagram showing

Sensitivity Analysis
(±10%) while holding others constant which variables matter most

Tests NPV under combined scenarios

Range of NPVs showing optimistic and
Scenario Analysis (Best Case / Base Case / Worst
pessimistic outcomes
Case)

Assigns probability distributions to

Monte Carlo Probability distribution of NPV — e.g., '80%
multiple variables and simulates
Simulation probability NPV > 0'
thousands of random outcomes

Finds the level of output/revenue at

Break-Even Break-even volume, price, or cost — margin
which project just breaks even (NPV =
Analysis of safety assessment
0)

Decision Tree Maps sequential decisions and Optimal decision path based on Expected
Analysis uncertain outcomes with probabilities Monetary Value (EMV)

3. Sources of Project Financing

A. EQUITY FINANCING
• Promoter's Capital: Own contribution of project owners — skin in the game; demonstrates commitment
• Public Issue (IPO): Raising capital from the public through stock exchange listing
• Rights Issue: Offering new shares to existing shareholders at a discounted price
• Preference Shares: Fixed dividend, priority over equity in liquidation; hybrid instrument
• Retained Earnings: Profits reinvested into the project rather than distributed as dividends
• Private Equity: Investment by PE firms in established companies; different from VC

B. DEBT FINANCING
• Term Loans: Medium to long-term loans from banks/financial institutions for capital expenditure
• Debentures/Bonds: Fixed income instruments issued to the public or institutional investors
• Working Capital Loans: Cash credit, overdraft, bill discounting for day-to-day operations
• External Commercial Borrowings (ECB): Foreign currency loans from international markets
• Non-Convertible Debentures (NCDs): Fixed-rate debt instruments traded on exchanges
• Mezzanine Finance: Hybrid debt-equity instrument — senior to equity, junior to senior debt

C. VENTURE CAPITAL (VC)

• Seed Stage: Idea validation — very small investment, very high risk, founder-only team
• Series A: Product development — proof of concept, early users, first institutional VC round
• Series B/C/D: Scaling and growth — proven product-market fit, expanding team and markets
• Pre-IPO / Growth Stage: Large-scale expansion, preparing for public market listing
• VC provides: Capital + strategic guidance + network introductions + board governance
• Exit mechanisms: IPO (public listing), Strategic Acquisition (M&A;), Secondary Sale (to another PE/VC)

D. INSTITUTIONAL SUPPORT
• IDBI Bank: Industrial Development Bank — long-term project finance for industry
• SIDBI: Small Industries Development Bank — MSME financing and development
• NABARD: National Bank for Agriculture and Rural Development — agricultural projects

Project Management — Complete Study Guide Page 18

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

• NHB: National Housing Bank — housing and real estate project finance
• EXIM Bank: Export-Import Bank of India — financing for export-import businesses
• World Bank / ADB / IFC: International institutions for sovereign and private sector projects

4. Cost of Capital and Capital Budgeting

WACC Numerical Example:

Capital Structure: Equity ■40L (40%) | Debt ■50L (50%) | Preference ■10L (10%) | Total ■1,00,00,000

Weighted
Source Amount Weight Cost Calculation
Cost

CAPM: Ke = 6% + 1.2 × (12%−6%) =

Equity (Ke) ■40,00,000 0.40 13.2% 5.28%
13.2%

Kd = 10% × (1−0.30) = 7.0% (after

Debt (Kd) ■50,00,000 0.50 7.0% 3.50%
tax)

Preference
■10,00,000 0.10 9.0% Kp = Dividend / Net Proceeds = 9% 0.90%
(Kp)

TOTAL ■1,00,00,000 1.00 — WACC = Sum of weighted costs 9.68%

■ All projects in this company must be evaluated at a minimum discount rate of 9.68%. Projects with
IRR > 9.68% and NPV > 0 at WACC should be accepted.

Project Management — Complete Study Guide Page 19

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

■ MODULE IV

Project Implementation, Control and Closure (8 Lectures)

1. Earned Value Management (EVM)

EVM integrates scope, schedule, and cost into a single, objective performance measurement system. It answers
the fundamental question: 'Are we getting value for our spending?'

The EVM Problem:

Traditional reporting tells you: 'We spent ■50L and are 6 months into a 12-month project.' This seems fine —
but it misses the critical question: How much of the planned work is actually done? If only 40% of work is
complete (not 50%), the project is behind schedule AND over budget. EVM reveals this.

Three Baseline Measures:

Planned Value (PV) — 'The Budget'

Authorized budget assigned to planned work. PV = BAC × % planned complete

Earned Value (EV) — 'Work Accomplished'

Budget value of work actually completed. EV = BAC × % actually complete

Actual Cost (AC) — 'What Was Spent'

Total actual costs incurred for work performed to date

EVM Performance Metrics — Complete Formulae:

Metric Formula Interpretation Good = ?

Positive: ahead of schedule |

Schedule Variance (SV) EV − PV SV > 0
Negative: behind schedule

Positive: under budget | Negative:

Cost Variance (CV) EV − AC CV > 0
over budget

Schedule Performance 1.0 = on schedule | >1 ahead | <1

EV / PV SPI > 1
Index (SPI) behind

Cost Performance Index 1.0 = on budget | >1 under budget |

EV / AC CPI > 1
(CPI) <1 over

Estimate at Completion Forecasted total project cost at

BAC / CPI EAC ≤ BAC
(EAC) completion

Estimate to Complete Remaining budget needed to

EAC − AC ETC low
(ETC) complete project

Variance at Completion Positive: under budget | Negative:

BAC − EAC VAC > 0
(VAC) cost overrun

To-Complete Performance (BAC − EV) / (BAC − Efficiency needed to complete on

TCPI ≤ 1
Index (TCPI) AC) budget. >1 means must work harder

EVM Dashboard Example:

Project: Office Building | BAC = ■100L | 6 months into 12-month project

Project Management — Complete Study Guide Page 20

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Metric Value Meaning

PV (Planned Value) ■50L Should have spent ■50L worth of work by now

EV (Earned Value) ■40L Only ■40L worth of work actually completed

AC (Actual Cost) ■45L Actually spent ■45L to get that work done

SV = EV − PV −■10L ■10L worth of work BEHIND schedule

CV = EV − AC −■5L ■5L OVER BUDGET for work accomplished

SPI = EV/PV 0.80 Only 80% of planned work done — 20% behind

CPI = EV/AC 0.89 Only 89 paise worth of work per ■1 spent

EAC = BAC/CPI ■112.4L Project will likely cost ■12.4L MORE than planned

VAC = BAC − EAC −■12.4L Expected cost overrun of ■12.4L

Must be 9% MORE efficient going forward to finish on

TCPI 1.09
budget

2. Project Management Challenges

Scope Creep — The Silent Project Killer:

PMI's Pulse of the Profession (2018): 52% of projects experience scope creep. Uncontrolled expansion of
project scope without corresponding adjustments to time, cost, and resources.

The Anatomy of Scope Creep:

Stage Description

Requirements not clearly defined → everyone has a different mental model

Stage 1: Vague Initial Scope
→ diverging expectations from the start

Stage 2: 'While You're At It' Stakeholders request additions during execution: 'While rebuilding the
Requests website, add a member portal too.' Individually small, collectively massive.

Stage 3: Uncontrolled Without formal change control, team implements additions without
Implementation assessing impact on time, cost, and resources.

Stage 4: Cascading Delays Added scope pushes schedule back → budget rises → sponsor questions
and Overruns the project → crisis — all preventable with proper change control.

Formal Change Control Process:

Step Activity

Step 1: Change Any stakeholder submits CR form: description, reason, requestor, impact if NOT
Request Submission made

Step 2: Impact
PM and team analyze full impact: scope, schedule, cost, resources, quality, risk
Analysis

Step 3: CCB Review Change Control Board (sponsor, PM, key stakeholders): Approve / Reject / Defer

Step 4: Baseline If approved: update scope statement, WBS, schedule, budget. Establish new
Update baseline.

Project Management — Complete Study Guide Page 21

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Step Activity

Step 5: Documentation Log all CRs in Change Log. Maintain audit trail for governance.

Stakeholder Management — Power-Interest Grid:

Low Interest High Interest

MANAGE CLOSELY (Most critical

KEEP SATISFIED (Decision-makers with low
stakeholders) Regular engagement,
High Power day-to-day interest) Monitor and inform on key
frequent communication, involve in
decisions only
decisions

KEEP INFORMED (Engaged but

MONITOR (Broad audience with little influence) limited power) Regular updates;
Low Power
Periodic updates; watch for changes in power address concerns; leverage for
support

Tuckman's Team Development Model:

Stage Team Behavior PM Action

Team comes together; polite, excited,

Provide clear direction; establish norms; build
1. FORMING uncertain; testing boundaries; high
trust; clarify roles and goals
dependence on PM

Conflict emerges; roles and power

Acknowledge conflict; facilitate resolution; coach
2. STORMING contested; frustration; sub-groups
individuals; reinforce goals
may form

Team establishes norms; cohesion

Step back; support; reinforce positive behaviors;
3. NORMING grows; trust builds; collaboration
provide feedback
improves

High productivity; self-organizing;

4. Delegate; focus on strategic issues; celebrate
creative problem-solving; shared
PERFORMING achievements; remove obstacles
leadership

5. Team disbands; reflective; may feel Celebrate success; document lessons; provide
ADJOURNING loss; transition to new roles career guidance; formal recognition

3. Project Risk Management

Risk vs. Issue:

Risk: Uncertain future event — managed proactively before it occurs.

Issue: A risk that has materialized — requires immediate corrective action.

Example: 'Vendor may deliver late' → Risk. | 'Vendor just confirmed 2-week delay' → Issue.

Risk Identification Methods:

Method Description

Structured interviews with experienced PMs and domain experts to elicit risks
Expert Interviews
from experience

Project Management — Complete Study Guide Page 22

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Method Description

Full team workshop: 'What could go wrong?' Generates comprehensive, diverse

Brainstorming Sessions
risk list

Anonymous, iterative expert elicitation. Avoids groupthink. Consensus-building

Delphi Technique
over multiple rounds.

Industry-specific lists of risks from past projects — PMBOK, FIDIC, RIBA

Risk Checklists
standard checklists

Weaknesses → Threats (risks); Strengths → Reduce threats; Opportunities →

SWOT Analysis
Positive risks

Invalid project assumptions represent risks. Every assumption should be

Assumption Analysis
examined.

Cause-Effect Diagrams Ishikawa/Fishbone diagrams identify root causes of potential risk events

Risk Response Strategies:

For Threats For Opportunities
Strategy Example
(Negative) (Positive)

Change technology to avoid failure

Eliminate the risk by Ensure the opportunity
Avoid / Exploit risk | Acquire company to exploit
changing plan is realized
market opportunity

Shift impact to third

Transfer / Share risk/reward with Buy insurance | Form joint venture to
party (insurance,
Share partner exploit opportunity together
outsource)

Prototype to reduce technology risk |

Mitigate / Reduce probability Increase probability
Add resources to accelerate
Enhance and/or impact and/or impact
opportunity

Accept Do nothing; take the hit Do nothing; benefit if it Accept minor risks below threshold;
(Passive) if it occurs occurs document in risk register

Establish contingency Monitor and capture Add contingency budget; define

Accept (Active)
reserve (time/cost) benefit when ready trigger conditions

Probability-Impact Matrix:
Probability \ Impact Low Impact (1-3) Medium Impact (4-6) High Impact (7-9)

■ CRITICAL —
High Probability (7-9) ■ MEDIUM — Monitor ■ HIGH — Plan Response
Immediate Action

■ HIGH — Plan
Medium Probability (4-6) ■ LOW — Accept ■ MEDIUM — Monitor
Response

■ MEDIUM —
Low Probability (1-3) ■ VERY LOW — Accept ■ LOW — Accept
Monitor

EMV (Expected Monetary Value) Example:

Risk Probability Impact (■) EMV (■)

Vendor delivers late (+4 weeks) 30% +5,00,000 cost +1,50,000

Project Management — Complete Study Guide Page 23

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Risk Probability Impact (■) EMV (■)

Key developer resigns 20% +3,00,000 cost +60,000

Regulatory approval delayed 15% +8,00,000 cost +1,20,000

Client approves design early

25% −2,00,000 saving −50,000
(opportunity)

TOTAL CONTINGENCY RESERVE ■2,80,000

4. Project Quality Management

Cost of Quality (COQ):

Cost of Conformance (investing in quality): Prevention costs (training, process design, standards) + Appraisal
costs (testing, inspections, audits)

Cost of Non-Conformance (poor quality): Internal failure (rework, scrap) + External failure (warranty, returns,
litigation, reputation damage)

■ The Golden Rule: Every ■1 spent on PREVENTION saves ■10–■100 in FAILURE costs. Quality is
never free — but poor quality is always more expensive.

Seven Basic Quality Tools:

Tool Purpose When to Use

Root cause analysis — map all possible

Cause-Effect Diagram causes of a problem using 6M: Man, When a quality problem occurs
(Ishikawa/Fishbone) Machine, Method, Material, and root causes are unknown
Measurement, Mother Nature

Rank defects/problems from most to least

frequent. Identify 'vital few' causes Prioritizing which quality issues to
Pareto Chart (80/20 Rule)
responsible for majority (80%) of address first
problems

Monitor process stability over time.

Ongoing process monitoring in
Control Charts (SPC) Shows data against UCL and LCL. Points
manufacturing or operations
outside limits = special cause variation

Shows frequency distribution of data

Understanding distribution of
(spread, shape, central tendency).
Histogram defects, dimensions, delivery
Normal, skewed, bimodal shapes indicate
times
process health

Tests correlation between two variables Identifying whether a potential

Scatter Diagram — e.g., code reviews vs. defects; training cause actually correlates with
hours vs. error rates defects

Visual representation of a process —

Process redesign and
steps, decision points, flows. Identifies
Flowchart / Process Map understanding current-state
inefficiencies, loops, and improvement
workflows
opportunities

Simple data collection form for recording

Standardizing data collection
Checklist frequency of specific events, defects, or
during inspections or operations
failures. Raw data for Pareto/histograms

Project Management — Complete Study Guide Page 24

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

5. Project Closure and Post-Project Evaluation

Why Projects Fail to Close Properly:

• Team disbands immediately to new projects before closure activities are complete
• Lessons learned sessions skipped — 'we're too busy for retrospectives'
• Documentation incomplete, scattered across emails and personal drives
• Benefits realization never measured — no one checks if promised benefits were delivered
• Contracts left open creating ongoing financial and legal obligations
• Consequence: Organizations repeat the same mistakes project after project

Project Closure Steps:

Step Activity

Verify all deliverables have been completed to the customer's satisfaction against
Scope Verification
acceptance criteria

Formal Acceptance Obtain written acceptance sign-off from client and/or project sponsor

Close all procurement contracts; ensure all vendor payments are settled; release
Contract Closure
performance bonds

Release team members back to departments; release equipment, software

Resource Release
licenses, office space

Archive all project documents — plans, reports, contracts, correspondence — in

Document Archiving
retrievable format

Conduct structured retrospective; document what went well, poorly, and what to do
Lessons Learned
differently

Write comprehensive final project report — objectives vs. actuals, key decisions,
Final Report
outcomes, recommendations

Recognize and celebrate team achievements — important for morale and

Celebration
organizational culture

Types of Project Audit:

Audit Type What is Examined Conducted By

Adherence to PM processes, methodologies,

Process Audit PMO or external PM consultant
and organizational standards

Scope, schedule, cost, and quality outcomes Senior PM or independent

Performance Audit
vs. plan reviewer

Regulatory requirements, contractual Legal/compliance team or external

Compliance Audit
obligations, legal compliance auditor

Project accounts, expenditures, procurement

Financial Audit Internal/external financial auditors
integrity, cost reporting accuracy

Whether promised benefits were actually Benefits realization team or

Post-Completion Audit
realized 12-24 months after closure sponsor

Project Management — Complete Study Guide Page 25

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

■ MODULE V

Contemporary Issues, Applications and Case Studies (8 Lectures)

1. Waterfall, Agile, and Lean Project Management

WATERFALL (Traditional / Predictive):

Sequential, linear approach where each phase must be fully completed before the next begins. Originated in
manufacturing and construction, then adopted for software (unfortunately, as it proved problematic).

Aspect Details

Sequential: Requirements → Design → Development → Testing → Deployment →

Approach
Maintenance

Fixed, fully defined upfront. Changes are costly and discouraged once planning is
Scope
complete.

Documentation Heavy documentation at each phase — detailed specifications, design docs, test plans

Customer
Primarily at the beginning (requirements) and end (acceptance testing)
Involvement

Risk High risk of delivering wrong product — customer only sees final output at end

Construction, manufacturing, defense, government contracts with fixed requirements

Best For
and regulatory documentation needs

Clear milestones and deliverables; strong documentation; easy to manage; predictable

Advantages
timeline and cost

Inflexible to change; late defect discovery; customer may get wrong product; waterfall
Disadvantages
projects historically have 70%+ failure rates in software

AGILE PROJECT MANAGEMENT:

Iterative, incremental approach with continuous customer feedback and adaptation. Born from the Agile
Manifesto (February 2001), signed by 17 software practitioners in Snowbird, Utah.

Agile Manifesto — Four Values:

Agile Values Traditional Approach

Individuals and interactions over: Processes and tools

Working software over: Comprehensive documentation

Customer collaboration over: Contract negotiation

Responding to change over: Following a plan

SCRUM Framework — Complete Detail:

Project Management — Complete Study Guide Page 26

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Element Details

Time-boxed iteration of 2–4 weeks. Fixed duration. No scope changes once Sprint
Sprint
starts. Delivers a potentially shippable Increment.

Represents customer and business. Owns and prioritizes Product Backlog. Defines
Product Owner
user stories with acceptance criteria. Accepts or rejects completed work.

Servant-leader. Facilitates Scrum events. Removes impediments. Coaches team in

Scrum Master
Scrum. Protects team from interruptions. NOT the project manager.

Cross-functional, self-organizing team of 3–9 members. All skills needed to deliver

Development Team
the Increment. Accountable as a unit for Sprint Goal.

Ordered list of all features, enhancements, bug fixes needed. Written as User
Product Backlog Stories: 'As a [user], I want [capability] so that [benefit].' Never complete — evolves
continuously.

Product Backlog items selected for the Sprint + plan for delivering them. Owned by
Sprint Backlog
Development Team. Created during Sprint Planning.

Sum of all Product Backlog items completed this Sprint and all previous Sprints.
Increment
Must meet Definition of Done. Potentially shippable.

Whole team plans what to deliver in the Sprint. PO presents top backlog items.
Sprint Planning (8h)
Team selects and creates detailed plan (Sprint Backlog). Sets Sprint Goal.

Daily stand-up: What did I do yesterday? What will I do today? Any impediments?
Daily Scrum (15min)
Self-coordination — not a status meeting for managers.

Present completed Increment to stakeholders. Gather feedback. PO updates

Sprint Review (4h)
backlog. Informal, collaborative — not a formal gate review.

Sprint Retrospective Team inspects itself: what went well, what didn't, what to improve. Primary
(3h) continuous improvement mechanism. Psychologically safe environment essential.

KANBAN Method:
Principle Description

Kanban Board with columns: Backlog | To Do | In Progress | Review | Done. All

1. Visualize Workflow
work items visible as cards.

Maximum items per column. Forces completion before starting new work.
2. Limit WIP
Reduces multitasking, improves quality.

Smooth, continuous flow with no bottlenecks. If items pile up in one column —

3. Manage Flow
it's a bottleneck to be fixed.

Clear criteria for moving items between stages. Reduces ambiguity and
4. Explicit Policies
disputes.

Regular review of metrics: Lead Time (request to delivery), Cycle Time (start to
5. Feedback Loops
done), Throughput (items/week).

Lead Time = WIP / Throughput. Reducing WIP directly reduces lead time when
Little's Law
throughput is constant.

LEAN Project Management:

Project Management — Complete Study Guide Page 27

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Origins: Toyota Production System (TPS). Core Principle: Maximize customer value while minimizing
waste.

7 Types of Waste (MUDA):

# Waste Type In Manufacturing In Software/Services

1 Overproduction Making more than needed Building features no one uses

2 Waiting Idle time between operations Waiting for approvals, code reviews, specs

Passing information through too many

3 Transportation Moving materials unnecessarily
handoffs

More steps than the customer

4 Overprocessing Excessive documentation, over-engineering
values

Incomplete features, unused code, pending

5 Inventory Excess WIP and finished goods
tasks

6 Motion Unnecessary worker movement Searching for information, switching contexts

7 Defects Scrap and rework Bugs, errors, requirements mismatches

Lean Tools:
Tool Description Application

Visual map of entire value flow from

Value Stream Mapping Identify non-value-adding steps and
request to delivery, showing all steps,
(VSM) waste
delays, and information flows

Sort (remove clutter), Set in Order

Workplace organization and
5S Methodology (organize), Shine (clean), Standardize
standardization
(establish norms), Sustain (maintain)

Focused improvement workshops

Kaizen Events (3-5 days) targeting a specific process Rapid, structured process improvement
problem

Produce/procure only what is needed,

Just-in-Time (JIT) when needed — eliminate inventory Supply chain and production scheduling
waste

Error-proofing devices or procedures

Poka-Yoke Quality control and defect prevention
that prevent defects from occurring

Go to where the work is done

Management by walking around; waste
Gemba Walk ('gemba') to observe and understand
identification
actual conditions

Comprehensive Comparison: Waterfall vs. Agile vs. Lean:

Aspect Waterfall Agile Lean

Approach Sequential phases Iterative sprints Continuous flow

Pull-based, minimal
Planning Detailed upfront Progressive elaboration
batch

Project Management — Complete Study Guide Page 28

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Aspect Waterfall Agile Lean

Medium — eliminates
Change Tolerance Low — costly to change High — embraces change
waste

Minimal —
Customer Involvement Mainly at start and end Every sprint, continuous
process-focused

Heavy — all phases As needed — avoid

Documentation Light — just enough
documented waste

Cross-functional, Cross-functional,
Team Structure Hierarchical, functional
self-organizing empowered

Frequent incremental
Delivery Single delivery at end Continuous delivery
delivery

Identify at start; may miss Continuous — Eliminate through

Risk Management
emergent risks retrospectives standardization

Schedule and budget Velocity, sprint burndown, Cycle time, lead time,
Measurement
adherence value throughput

Fixed scope, stable Evolving requirements, Efficiency optimization,

Best For
requirements innovation waste reduction

Construction, bridge, dam, Software, digital, app Manufacturing,

Examples
defense development healthcare, services

2. Sustainable and Green Project Management

Sustainable Project Management integrates environmental, social, and economic considerations — the Triple
Bottom Line (3BL) — into project decision-making throughout the lifecycle.

Dimension Focus Areas Key Practices

Fair labor, community impact, equity, Fair wages, safe working conditions, community
PEOPLE
safety, cultural preservation, consultation, inclusive design, social impact
(Social)
indigenous rights, health assessment

Carbon emissions, energy, water, EIA, LEED/BREEAM, carbon accounting,

PLANET (Envir
land use, biodiversity, waste, renewable energy, ISO 14001 EMS, circular
onmental)
pollution, climate change economy

Financial return, employment, income,

PROFIT Traditional financial appraisal + social
tax contribution, economic multiplier
(Economic) cost-benefit analysis + long-term value creation
effects

UN Sustainable Development Goals (SDGs) Relevant to Projects:

SDG Title Project Type

SDG 3 Good Health and Well-Being Hospital construction, healthcare systems, pharmaceutical R&D;

School construction, e-learning platforms, teacher training

SDG 4 Quality Education
programs

Water treatment plants, sanitation infrastructure, rural water

SDG 6 Clean Water and Sanitation
supply

Project Management — Complete Study Guide Page 29

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

SDG Title Project Type

SDG 7 Affordable and Clean Energy Solar/wind farms, hydropower, energy efficiency retrofit projects

Industry, Innovation and Manufacturing modernization, R&D; projects, infrastructure

SDG 9
Infrastructure development

Sustainable Cities and Smart city projects, metro rail, urban housing, waste
SDG 11
Communities management

Renewable energy, electric vehicle infrastructure, carbon

SDG 13 Climate Action
sequestration

3. Case Studies — Successful and Failed Projects

CASE STUDY 1: ISRO CHANDRAYAAN-3 (2023) — SUCCESS

Industry Space / Government / R&D;

Objective Achieve soft landing near Moon's south pole — become 4th country to land on Moon

Budget ~■615 crore — fraction of competitor mission costs (frugal innovation)

Date Soft landing achieved: July 23, 2023

PM Practices 1. Rigorous risk management after Chandrayaan-2 failure (analyzed every failure
Applied mode)
2. Redesigned lander with stronger legs and wider landing capability range
3. Extensive simulation, testing, and verification — zero defects approach
4. Cross-functional coordination across all ISRO centers nationwide
5. Phased milestones with formal gate reviews before each critical phase
6. Simplified design — fewer complex systems = fewer potential failure points

Outcome Successful soft landing on lunar south pole. ■615 crore investment delivered global
scientific achievement.

Lessons 1. Failure is a learning opportunity — Chandrayaan-2 failure directly enabled C-3

Learned success
2. Simplification reduces risk — remove complexity wherever possible
3. Strong leadership + clear accountability = high-performance culture
4. Frugal innovation: constraint drives creativity and efficiency

CASE STUDY 2: DELHI COMMONWEALTH GAMES 2010 — FAILURE

Industry Public Sector / Construction / Events Management

Original Budget ■656 crore (2003 estimate)

Final Cost Over ■70,000 crore — 100x cost overrun

Project Management — Complete Study Guide Page 30

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Key Failure 1. Scope Creep: Continuous, uncontrolled additions to infrastructure requirements with
Modes no change control
2. Cost Overruns: Budget escalated from ■656 crore to ■70,000+ crore with no
accountability
3. Schedule Delays: Multiple venues not ready weeks before the event opening
4. Corruption and Mismanagement: Procurement irregularities; substandard
construction; kickbacks
5. Stakeholder Failure: Zero coordination between central government, Delhi state, and
organizing committee
6. Risk Ignorance: Monsoon risks ignored in construction scheduling — predictable
delays occurred

Root Causes No integrated project plan; weak governance; unclear ownership; political interference;
procurement failure

Lessons 1. Strong governance and independent monitoring are essential for public sector
Learned projects
2. Scope must be frozen from the start — no additions without formal change control
and budget approval
3. Procurement integrity is non-negotiable — competitive, transparent tendering
required
4. Risk planning must be proactive, not reactive — monsoon risk was entirely
predictable
5. Accountability must be clearly assigned — everyone responsible = no one
responsible

CASE STUDY 3: HERSHEY'S ERP IMPLEMENTATION (1999) — IT FAILURE

Industry FMCG / Information Technology

Project SAP ERP + two additional software systems implemented simultaneously

Impact $150 million in Halloween candy could not be shipped — catastrophic for a candy
company

What Happened 1. Rushed go-live timed for October/Halloween (peak season) — wrong timing decision
2. Three complex software systems implemented simultaneously — too much
complexity
3. 30-month timeline drastically compressed — insufficient testing time
4. Inadequate user training — employees didn't know how to use the new systems
5. No rollback plan — couldn't revert when problems emerged at go-live

Root Causes Compressed timeline; inadequate testing; poor change management; wrong go-live
timing; big-bang rather than phased approach

Lessons 1. Never compress critical testing and user training phases — they are not optional
Learned 2. Go-live timing must consider business seasonality — don't go live during peak
business periods
3. Change management is as important as technical implementation — user adoption is
key
4. Phased implementation (one system at a time) reduces risk vs. big-bang approach
5. Always have a rollback plan before going live with mission-critical systems

CASE STUDY 4: AADHAAR BIOMETRIC IDENTITY SYSTEM — IT SUCCESS

Project Management — Complete Study Guide Page 31

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Industry Government / Information Technology / Social Development

Scale Largest biometric database in the world — 1.3+ billion enrollments

Key PM 1. Agile approach: System built incrementally; enrollments began before full system
Innovations was complete
2. Technology-first culture: Attracted top technologists from India's software industry to
government project
3. Open standards and open source: Maximized interoperability and reduced vendor
lock-in
4. Distributed enrollment: Enrolled across thousands of centers simultaneously —
parallel execution
5. Quality management: Sophisticated de-duplication algorithms to detect and reject
duplicate enrollments
6. Outcomes-based contracts with enrolling agencies — paid per enrollment, not per
hour
7. Real-time dashboards: Enrollments tracked by region and operator with live
performance data

Leadership Nandan Nilekani brought private sector execution culture and technology expertise to
UIDAI

Outcome Aadhaar enabled direct benefit transfer, reduced leakage in welfare programs, and
created digital identity infrastructure.

Lessons 1. Government projects CAN succeed with right leadership, culture, and autonomy
Learned 2. Agile approaches work for government technology at scale
3. Measurable success metrics (enrollments per day) drive accountability and
performance
4. Private sector expertise + public sector mandate = powerful combination

Project Management — Complete Study Guide Page 32

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

■ COMPLETE FORMULA QUICK REFERENCE

All Modules — Key Formulae for Examination

Network Analysis (CPM & PERT)

Earliest Finish (EF) ES + Duration

Latest Start (LS) LF − Duration

Total Float LS − ES = LF − EF

Free Float ES(Successor) − EF(Activity)

PERT Expected Time (te) (a + 4m + b) / 6

PERT Variance (σ²) [(b − a) / 6]²

PERT Standard Deviation (σ) (b − a) / 6

Project Variance (Critical

Σσ² of all critical path activities
Path)

Z-score (Probability) (Scheduled Date − Expected Duration) / σ_cp

Time-Cost Trade-off

(Crash Cost − Normal Cost) / (Normal Time − Crash

Cost Slope
Time)

Direct Costs + Indirect Costs + Penalty −

Total Project Cost
Incentive

Financial Appraisal

Net Present Value (NPV) Σ[CFt / (1+r)^t] − Initial Investment

IRR (Interpolation) r1 + [NPV1 / (NPV1 − NPV2)] × (r2 − r1)

Profitability Index (PI) PV of Inflows / Initial Investment

Payback Period (uniform CF) Initial Investment / Annual Cash Inflow

Return on Investment (ROI) (Net Profit / Investment) × 100

Fixed Costs / (Selling Price − Variable Cost per

Break-Even Units
unit)

Cost of Capital

Cost of Equity (CAPM) Ke = Rf + β × (Rm − Rf)

After-tax Cost of Debt Kd = Interest Rate × (1 − Tax Rate)

Cost of Preference Kp = Annual Dividend / Net Proceeds

WACC (E/V × Ke) + (D/V × Kd × (1−T)) + (P/V × Kp)

Project Management — Complete Study Guide Page 33

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

Earned Value Management (EVM)

Planned Value (PV) BAC × % Planned Complete

Earned Value (EV) BAC × % Actually Complete

Schedule Variance (SV) EV − PV (+ = ahead, − = behind)

Cost Variance (CV) EV − AC (+ = under budget, − = over)

Schedule Performance Index

EV / PV (>1 = ahead, <1 = behind)
(SPI)

Cost Performance Index

EV / AC (>1 = under budget, <1 = over)
(CPI)

Estimate at Completion
BAC / CPI
(EAC)

Estimate to Complete (ETC) EAC − AC

Variance at Completion
BAC − EAC
(VAC)

To-Complete Performance
(BAC − EV) / (BAC − AC)
Index (TCPI)

Risk Analysis

Expected Monetary Value

Probability × Impact
(EMV)

Net Risk Reserve Σ(Threat EMVs) − Σ(Opportunity EMVs)

Lean / Kanban

Little's Law Lead Time = WIP / Throughput

Cycle Time Time from work start to work done

Throughput Number of items completed per time period

Project Management — Complete Study Guide Page 34

PROJECT MANAGEMENT All Modules: I – V | University Examination Level

END OF STUDY GUIDE

Project Management — All Five Modules

This guide covers: Introduction to PM | Planning & Scheduling | Appraisal & Financing
Implementation & Control | Contemporary Issues | Case Studies & Practical Applications

Best of luck in your examinations! ■

Project Management — Complete Study Guide Page 35