Skip to content
CE-703 (B) · Project Management/Quick Revision Short Notes

Project Management (CE-703 (B)) - Unit 5 Short Notes

UNIT 5: PROJECT MANAGEMENT (CE-703(B))

Based on analysis of B PROJECT MANAGEMENT past papers (Nov 2023 & Nov 2022).


I. FUNDAMENTALS OF PROJECT MANAGEMENT

A. Definition and Core Parameters

A project is a temporary endeavor undertaken to create a unique product, service, or result. Project Management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements.

Key Parameters of Project Management:

  • Scope: What work is to be done.

  • Time: How long it will take (schedule).

  • Cost: The budget required.

  • Quality: The standards and specifications.

  • Risk: Uncertain events affecting objectives.

  • Resources: People, equipment, materials.

  • Stakeholders: Individuals/groups impacted.

Project Attributes/Characteristics:

  • Temporary: Has a definite beginning and end.

  • Unique: Produces a deliverable that is distinct from others.

  • Progressive Elaboration: Details become clearer as the project progresses.

  • Cross-functional: Requires expertise from various disciplines.

[!TIP] Exam Focus: "Parameters" and "Characteristics/Attributes" are direct 7-mark questions. Be prepared to list and explain each.

B. Objectives of Project Management

  • Primary Objective: To complete the project on time, within budget, and according to scope/quality specifications (the "Iron Triangle").

  • Secondary Objectives:

    • Maximize stakeholder satisfaction.

    • Optimize resource utilization.

    • Ensure safety and compliance.

    • Facilitate knowledge transfer and learning.

C. Importance of Project Management

  • Provides structured framework for execution.

  • Ensures efficient use of resources (time, money, people).

  • Manages risk and uncertainty proactively.

  • Improves communication and coordination among stakeholders.

  • Enhances quality and increases likelihood of project success.

  • Provides accountability and clear roles/responsibilities.

D. Project Life Cycle

The sequence of phases from project initiation to closure. Typical Stages:

  1. Initiation/Concept: Define project at a high level, feasibility study.

  2. Planning: Develop detailed roadmap (scope, schedule, budget, etc.).

  3. Execution/Implementation: Do the work, manage teams, produce deliverables.

  4. Monitoring & Controlling: Track progress, manage changes, ensure alignment with plan (occurs concurrently with Execution).

  5. Closing: Formal acceptance, handover, release resources, document lessons learned.

[!TIP] Exam Focus: "Stages of Project Life Cycle" and "Importance of Planning" are recurring questions. Emphasize that Planning is the most critical phase for defining the baseline against which all execution and control is measured.


II. PROJECT PLANNING

A. Overview and Significance

Planning is the process of defining project objectives, scope, and the course of action required to achieve them. It is the foundation for all subsequent project phases. A well-defined plan reduces uncertainty, improves communication, and provides a baseline for performance measurement.

B. Objectives of Project Planning

  • To define clear, measurable project goals and deliverables.

  • To establish a realistic schedule and budget.

  • To identify required resources and roles.

  • To anticipate and plan for risks.

  • To establish a baseline for performance measurement and control.

C. Project Planning Techniques

  • Critical Path Method (CPM): Deterministic model for scheduling, identifies critical path (longest path determining project duration).

  • Program Evaluation and Review Technique (PERT): Probabilistic model using three time estimates (Optimistic, Most Likely, Pessimistic) for uncertainty.

  • Gantt Charts: Visual bar chart illustrating schedule, start/end dates, and task dependencies.

  • Work Breakdown Structure (WBS): Hierarchical decomposition of total scope into manageable work packages.

D. Tools for Project Planning

  • Software: MS Project, Primavera P6, Asana, Trello.

  • Graphical Tools: Gantt charts, Network Diagrams.

  • Analytical Tools: Earned Value Management (EVM) spreadsheets, risk matrices.

  • Documentation Tools: Project charter, scope statement, WBS dictionary.

E. Project Scheduling

Concept: The process of creating a timeline that defines start and finish dates for project activities and milestones.

Types of Schedules:

  1. Master Schedule: High-level summary for senior management/stakeholders.

  2. Detailed Schedule: Comprehensive timeline with all activities, dependencies, and resource assignments (used by project team).

  3. Contingency Schedule: Includes buffer time for identified risks (often integrated as "float" or "slack" in CPM).


III. PROJECT COST & FINANCIAL MANAGEMENT

A. Cost Estimating

The process of forecasting the costs of resources needed to complete project activities. Methods:

  • Analogous Estimating: Using historical data from similar projects (top-down, less accurate).

  • Parametric Estimating: Using statistical relationships between historical data and other variables (e.g., cost per square foot).

  • Bottom-up Estimating: Estimating cost of individual work packages and rolling up (most accurate, time-consuming).

  • Three-point Estimating (PERT): Expected Time = (O + 4M + P) / 6 (used for time, can be adapted for cost).

B. Cost Improvement in Project Budgeting

  • Value Engineering (VE): Systematic review to improve function/value at lowest cost.

  • Cost Control: Tracking actual costs vs. budget, managing change orders.

  • Variance Analysis: Identifying and analyzing cost overruns/underruns.

  • Earned Value Management (EVM): Integrated scope, schedule, and cost performance measurement (see Unit VI).

C. Cash Flow Management

Elements of Cash Flow:

  • Cash Inflows: Payments from client, funding, asset sales.

  • Cash Outflows: Payments to vendors, salaries, equipment purchase, overheads.

  • Net Cash Flow: Inflows - Outflows for a period.

  • Cumulative Cash Flow: Running total of net cash flows.

Basic Principles of Estimation:

  • Base on detailed cost breakdown (WBS).

  • Consider timing of expenditures (not just total cost).

  • Include contingency reserves for known-unknowns.

  • Account for escalation/inflation for long-duration projects.

D. Sources of Project Financing

  • Internal Sources: Retained earnings, company reserves, sale of assets.

  • External Sources:

    • Debt Financing: Bank loans, bonds, debentures (requires repayment + interest).

    • Equity Financing: Venture capital, shareholder investment (no repayment, but ownership dilution).

    • Leasing/Hire Purchase: For equipment/machinery.

    • Government Grants/Subsidies: For specific sectors/projects.

    • Project Finance: Non-recourse/limited recourse financing secured by project assets.


IV. PROJECT ORGANIZATION & HUMAN RESOURCES

A. Organizational Structures

Structure Description Advantages Disadvantages
Functional Traditional hierarchy by department (e.g., Engineering, Marketing). Project manager has little authority. Efficient resource use, deep expertise, clear career paths. Slow decision-making, poor cross-functional coordination, project focus diluted.
Matrix <br> - Weak <br> - Balanced <br> - Strong Blend of functional and projectized. Team members report to both functional and project manager. Authority varies. Efficient resource use, improved communication, flexible. <br> Strong: Better project focus. Power struggle/conflict over resources, dual reporting confusion.
Projectized Full-time project team, project manager has full authority. Team disbanded after project. Fast decisions, high project focus, cohesive team. Resource duplication, inefficient for small projects, career uncertainty for team.

B. Role of the Project Manager

  • Key Responsibilities: Plan, execute, monitor, control, close. Manage scope, time, cost, quality, resources, communication, risk, stakeholders.

  • Core Competencies:

    • Technical: Knowledge of project management tools/techniques.

    • Leadership: Motivating, influencing, conflict resolution.

    • Communication: Clear, frequent, multi-channel.

    • Strategic/Business: Aligning project with organizational goals.

    • Problem-Solving: Proactive identification and resolution.

C. Team Development (Tuckman's Model)

Five Stages:

  1. Forming: Team members meet, polite, dependent on leader for direction.

  2. Storming: Conflicts arise over roles, ideas, processes. Power struggles.

  3. Norming: Team establishes norms, resolves conflicts, cohesion builds.

  4. Performing: High-functioning, autonomous, focused on goals.

  5. Adjourning: Project ends, team disbands, lessons learned documented.

[!TIP] Exam Focus: "Five-stage team development model and parameters" was a 14-mark question. Be ready to describe each stage with its key characteristics and the project manager's role in each.


V. CONTRACTS & LEGAL ASPECTS

A. Definition and Types of Contracts

Contract: A legally binding agreement between two or more parties. Common Types in Projects:

  • Fixed-Price/Lump Sum: Pre-agreed total price. Risk mainly on contractor.

  • Cost-Reimbursable: Client pays actual costs + fee. Risk mainly on client.

  • Time & Material (T&M): Payment based on time spent and materials used. Hybrid risk.

  • Unit Price: Payment per unit of work (e.g., per cubic meter of concrete).

B. Essentials of a Valid Contract

  1. Offer & Acceptance: Clear proposal and unqualified agreement.

  2. Consideration: Something of value exchanged (money, service).

  3. Intention to Create Legal Relations: Serious intent to be bound.

  4. Capacity: Parties must be legally competent (sound mind, age).

  5. Free Consent: No coercion, undue influence, fraud, misrepresentation.

  6. Lawful Object & Consideration: Purpose must be legal.

C. Contract Management in Projects

  • Pre-award: Scope definition, bidding, vendor selection.

  • Award: Formal signing, baseline establishment.

  • Administration: Managing changes, payments, communications, claims.

  • Close-out: Final acceptance, warranty management, final payment.

  • Key Principle: Maintain clear, documented communication and manage scope changes rigorously to avoid disputes.


VI. RISK, CONTROL & PERFORMANCE MANAGEMENT

A. Risk Management

Risk: An uncertain event or condition that, if it occurs, has a positive or negative effect on project objectives. Risk Identification Techniques:

  • Brainstorming: Team/Stakeholder workshops.

  • Checklist Analysis: Using historical risk lists.

  • Assumption Analysis: Challenging project assumptions.

  • SWOT Analysis: Strengths, Weaknesses, Opportunities, Threats.

  • Delphi Technique: Anonymous expert consensus.

  • Diagramming Techniques: Cause-and-effect (Ishikawa), flowcharts.

B. Control Mechanisms

Control Charts (Statistical Process Control - SPC):

A graphical tool to monitor process variation over time.

  • Components: Center Line (CL - process mean), Upper Control Limit (UCL), Lower Control Limit (LCL).

  • Purpose: Distinguish between common cause variation (inherent to process) and special cause variation (assignable, needs correction).

  • Application in PM: Monitor cost performance, schedule variance, quality metrics.

C. Performance Measurement (Earned Value Management - EVM)

Integrates scope, schedule, and cost to measure performance and forecast. Key Formulas:

  1. Planned Value (PV): Budgeted cost of work scheduled.

  2. Earned Value (EV): Budgeted cost of work performed.

  3. Actual Cost (AC): Actual cost of work performed.

Variance Analysis:

  • Schedule Variance (SV): SV = EV - PV

    • SV > 0: Ahead of schedule.

    • SV < 0: Behind schedule.

  • Cost Variance (CV): CV = EV - AC

    • CV > 0: Under budget.

    • CV < 0: Over budget.

Performance Indices:

  • Schedule Performance Index (SPI): SPI = EV / PV

    • SPI > 1: Efficient (ahead).

    • SPI < 1: Inefficient (behind).

  • Cost Performance Index (CPI): CPI = EV / AC

    • CPI > 1: Cost efficient (under).

    • CPI < 1: Cost overrun.

[!TIP] Exam Focus: "Value of Work Performed" is a direct question. Memorize the 4 core terms (PV, EV, AC) and the 2 Variance formulas (SV, CV). Understand interpretation of positive/negative values.


VII. ADVANCED PLANNING TECHNIQUES

A. Network Planning Models (CPM vs. PERT)

Feature CPM (Critical Path Method) PERT (Program Evaluation & Review Technique)
Nature Deterministic (single time estimate) Probabilistic (three time estimates)
Time Estimate One (most likely) Three: Optimistic (O), Most Likely (M), Pessimistic (P)
Focus Time-Cost Trade-off (crashing) Time uncertainty & probability
Application Construction, repetitive projects R&D, new product development, high-uncertainty projects
Expected Time Not Applicable TE = (O + 4M + P) / 6
Variance Not Applicable Variance = [(P - O)/6]^2

Critical Path: Longest path through the network diagram. Determines the shortest possible project duration. Zero Total Float on critical path activities.

B. Other Planning Techniques

  • Simulation (Monte Carlo): Uses computer models to simulate thousands of possible project outcomes based on probability distributions for activity durations/costs. Provides probability of meeting deadlines/budgets.

  • What-if Analysis: "Scenario planning." Evaluating impact of specific events (e.g., "What if key resource is delayed by 2 weeks?").

  • Resource Leveling/ Smoothing: Adjusting schedule to resolve resource over-allocations while minimizing impact on critical path.

  • Agile/Iterative Planning: Rolling-wave planning, backlog grooming, sprints (for adaptive/uncertain projects).

Go to where you left off?

Quick Add to Notes

Save questions, your own notes and screenshots into notes filed by unit. It takes a free account.

Create free account

Have an account? Log in