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

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

UNIT 4: Project Management Short Notes

(Based on RGPV Past Papers: B Project Management - Nov 2023, Nov 2022)


I. Fundamentals of Project Management

Definition: Project Management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements.

Parameters of Project Management (Iron Triangle + More):

The primary constraints are often called the "Triple Constraint":

  1. Scope: What work must be done? (Deliverables, features).

  2. Time: How long will it take? (Schedule, deadlines).

  3. Cost: What is the budget? (Financial resources).

  4. Quality: What are the standards? (Performance, fitness for use).

  5. Resources: What people, equipment, materials are needed?

  6. Risk: What could go wrong? (Uncertainties).

Exam Tip: Questions often ask to "explain parameters." List all 6, not just the triple constraint. Use the mnemonic S-T-C-Q-R-R.

Objectives of Project Management:

  • To achieve specific, unique, and time-bound goals.

  • To complete the project within the triple constraint (Scope, Time, Cost).

  • To optimize the use of resources (people, capital, materials).

  • To satisfy stakeholders' needs and expectations.

  • To proactively manage risks and issues.

Importance of Project Management:

  • Provides clarity on goals, roles, and responsibilities.

  • Ensures efficient resource allocation and control.

  • Facilitates risk mitigation and problem-solving.

  • Improves communication and stakeholder engagement.

  • Increases the likelihood of project success and customer satisfaction.

  • Enables better cost and time control, avoiding overruns.

Project Attributes:

  • Temporary: Has a definite beginning and end.

  • Unique: Produces a unique product, service, or result.

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

  • Cross-functional: Requires resources from different departments.

  • Driven by Stakeholders: Success is defined by stakeholder acceptance.


II. Project Life Cycle

Definition: The series of phases that a project passes through from initiation to closure.

Stages of Project Life Cycle (Generic):

  1. Initiation: Define project at a broad level, develop charter, identify stakeholders.

  2. Planning: Establish scope, refine objectives, define course of action. (Most critical for success).

  3. Execution: Complete the work defined in the project management plan.

  4. Monitoring & Controlling: Track, review, regulate progress and performance.

  5. Closure: Formally complete or terminate the project.

Phases of Project Management (Often used interchangeably with Stages):

  • Concept/Feasibility: Idea generation, initial analysis.

  • Definition/Planning: Detailed scope, schedule, budget, risk plans.

  • Implementation/Execution: Construction, development, production.

  • Commissioning/Handover: Testing, training, handing over to client.

  • Post-Project Evaluation: Lessons learned, final audit.

Importance of Planning in Project Life Cycle:

[!TIP] "Fail to plan = plan to fail." Planning phase consumes significant time but reduces execution uncertainty.

  • Defines the roadmap: How, when, by whom, and at what cost.

  • Baseline for control: Provides benchmarks for measuring progress (PV, EV, AC).

  • Risk identification: Proactive assessment allows mitigation strategies.

  • Resource optimization: Ensures right resources at right time.

  • Stakeholder alignment: Manages expectations and secures commitment.


III. Project Planning

Objectives of Project Planning:

  • To define clear, measurable project goals (SMART).

  • To establish a realistic schedule and budget.

  • To identify required resources and roles/responsibilities.

  • To outline communication, risk, and procurement strategies.

  • To create a baseline against which progress is measured.

Techniques Involved in Project Planning:

  • Work Breakdown Structure (WBS): Hierarchical decomposition of total scope.

  • Gantt Charts: Visual timeline for activities.

  • Critical Path Method (CPM): Identifies longest path of tasks.

  • Program Evaluation and Review Technique (PERT): Probabilistic time estimation.

  • Responsibility Assignment Matrix (RAM): e.g., RACI chart (Responsible, Accountable, Consult, Inform).

  • Milestone Planning: Key events marking major progress.

Tools Involved in Project Planning:

  • Software: Microsoft Project, Primavera P6, Jira, Asana, Trello.

  • Diagrams: Flowcharts, Network Diagrams (Precedence Diagramming Method).

  • Spreadsheets: MS Excel for cost tracking, simple schedules.

  • Templates: Standardized formats for WBS, risk registers, status reports.

Project Planning and Techniques (Integrated Overview):

Planning is not sequential but iterative.

  1. Start with Scope Statement → Develop WBS (core technique).

  2. Define activities from WBS → Sequence using Network Diagrams → Estimate durations (using PERT or expert judgment).

  3. Develop Gantt Chart (tool) from the network.

  4. Assign resources using RAM → Estimate costs → Develop budget.

  5. Identify risks → Plan responses → Finalize baseline plan.

Common Pitfall: Creating a schedule without a WBS leads to missed tasks. WBS is the foundation.


IV. Project Scheduling and Network Analysis

Project Scheduling: Types of Schedules

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

  2. Project Schedule: Detailed timeline with all activities, dependencies, milestones.

  3. Resource Schedule: Allocation of people/equipment over time.

  4. Milestone Schedule: Key dates only (e.g., design complete, prototype ready).

Network Planning Models: PERT vs. CPM

Feature PERT (Program Evaluation and Review Technique) CPM (Critical Path Method)
Origin Developed for U.S. Navy's Polaris missile program (1958). Developed for DuPont & Remington Rand (1957).
Focus Time (uncertainty in activity durations). Time & Cost (trade-off between them).
Time Estimates Three estimates: Optimistic (O), Pessimistic (P), Most Likely (M). <br> Expected Time: $$\displaystyle T_e = \frac{O + 4M + P}{6} $$ <br> Variance: $$\displaystyle \sigma^2 = \left(\frac{P - O}{6}\right)^2 $$ Single deterministic estimate (based on historical data).
Activity Type Event-oriented (focus on milestones/events). Activity-oriented (focus on tasks/activities).
Application Research & Development, New Projects with high uncertainty. Construction, Repetitive Projects with predictable tasks.
Crashing Not typically used. Yes (reducing duration at increased cost).
Example Developing a new software application. Building a bridge or a building.

Exam Tip: Be ready to compare them in a 14m question. Highlight the three-time estimate and probabilistic nature of PERT vs. deterministic and cost-time trade-off of CPM.


V. Cost Management and Budgeting

Cost Estimating and Cost Improvement in Project Budgeting

Cost Estimating: Process of forecasting the costs of resources needed to complete project activities.

  • Methods:

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

    2. Parametric Estimating: Using statistical relationship (e.g., cost per square foot).

    3. Bottom-Up Estimating: Estimating individual work packages and rolling up (Most accurate, time-consuming).

    4. Three-Point Estimating (PERT): $$\displaystyle T_e = \frac{O + 4M + P}{6} $$ applied to cost.

    5. Reserve Analysis: Including contingency reserves for known-unknowns.

Cost Improvement (Cost Reduction/Control):

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

  • Variance Analysis: Comparing baseline cost vs. actual cost (CV = EV - AC).

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

    • Key Formulas:

      • Cost Performance Index (CPI) = $$\displaystyle \frac{EV}{AC} $$

      • Schedule Performance Index (SPI) = $$\displaystyle \frac{EV}{PV} $$

      • Estimate at Completion (EAC) = $$\displaystyle \frac{BAC}{CPI} $$ (if current cost performance continues)

  • Procurement Strategies: Competitive bidding, bulk purchasing, long-term contracts.

  • Risk Management: Identifying and mitigating cost risks early.


VI. Project Execution and Control

Role of Project Manager in Project Success:

  • Leader & Motivator: Builds and leads the team, resolves conflicts.

  • Planner & Scheduler: Develops and maintains the project plan.

  • Communicator: Primary point of contact for stakeholders, manages information flow.

  • Controller: Monitors progress, manages changes, controls scope, schedule, cost.

  • Problem Solver: Identifies issues, facilitates solutions.

  • Risk Manager: Proactively identifies and responds to risks.

  • Stakeholder Manager: Manages expectations, ensures engagement.

Control Charts (Statistical Process Control - SPC):

Used to monitor process variation and determine if a process is in statistical control.

  • Components:

    • Center Line (CL): Mean or average of the quality characteristic.

    • Upper Control Limit (UCL): Typically mean + 3σ.

    • Lower Control Limit (LCL): Typically mean - 3σ.

  • Common Types:

    • X-bar Chart: Monitors process mean (average of samples).

    • R-Chart: Monitors process variability (range of samples).

    • p-Chart: Monitors fraction defective (for attribute data).

  • Interpretation: Points outside UCL/LCL or non-random patterns indicate assignable causes (special variation) needing investigation.

Value of Work Performed (Earned Value - EV):

  • Definition: The budgeted cost of work actually performed (completed) during a given period. It measures scope accomplished in monetary terms.

  • Formula: EV = ( % of Work Completed ) × ( Budget at Completion for that Work )

  • Example: A task with a budget of $$\displaystyle 10,000 is 60% complete. EV = 0.60 × $$10,000 = $6,000.

  • Use: Core component of EVM to calculate CV (Cost Variance) and SV (Schedule Variance).


VII. Human Resource and Team Management

Five Stage Team Development Model (Tuckman's Model):

Describes the stages teams go through to grow, face challenges, tackle problems, and deliver results.

Stage Key Characteristics Project Manager's Role
1. Forming Team members are polite, positive, dependent on PM for guidance. Goals/roles unclear. Provide clear direction, define objectives, build trust.
2. Storming Conflict emerges as roles clarify, ideas clash, resistance to constraints. Facilitate conflict resolution, reinforce goals, coach.
3. Norming Team resolves differences, establishes cohesion, develops routines, trust builds. Empower team, delegate, monitor progress.
4. Performing Team works independently, effectively, focuses on problem-solving & goals. High productivity. Delegate, observe, manage external interfaces.
5. Adjourning Project ends, team disbands. Members may feel loss/uncertainty. Celebrate achievements, document lessons, release resources.

Note: Teams can move back and forth between stages (e.g., new member may cause regression to Storming).


VIII. Contracts and Legal Aspects

Contracts: Definition and Essentials of Valid Contracts

Definition: A contract is a legally enforceable agreement between two or more parties that creates mutual obligations.

Essentials of a Valid Contract (Under Indian Contract Act, 1872):

  1. Offer and Acceptance: Clear, communicated, and unconditional.

  2. Lawful Consideration: Something of value exchanged (price, act, forbearance).

  3. Lawful Object: Purpose must be legal, not against public policy.

  4. Capacity to Contract: Parties must be competent (major, sound mind, not disqualified).

  5. Free Consent: Not obtained by coercion, undue influence, fraud, misrepresentation, mistake.

  6. Possibility of Performance: Terms must be clear and capable of being performed.

  7. Intention to Create Legal Relations: Social/domestic agreements usually not intended.

Common Pitfall: Missing "Lawful Object" or "Free Consent" makes contract voidable or void.


IX. Financial Management

Cash Flow: Elements and Components

Definition: The net amount of cash moving into and out of a project during a specific period.

Component Inflows (+) Outflows (-)
Operating Activities Revenue from project delivery, client payments. Salaries, materials, utilities, rent, taxes.
Investing Activities Sale of equipment, asset disposal. Purchase of machinery, land, buildings.
Financing Activities Loans received, equity infusion. Loan repayments, interest payments, dividends.

Net Cash Flow (NCF) for a period = Total Cash Inflows - Total Cash Outflows
Cumulative Cash Flow = Sum of all NCFs up to that period.

Basic Principles of Cash Flow Estimations:

  1. Incremental Principle: Consider only incremental cash flows (additional flows due to the project). Ignore sunk costs.

  2. After-Tax Principle: Use after-tax cash flows (taxes are a real cash outflow).

  3. Separated Principle: Separate investment (initial outflow) from operating cash flows.

  4. Consistency Principle: Apply same methodology (nominal vs. real) throughout.

  5. Timing Principle: Cash flows are assumed at period-end unless specified.

Sources of Project Financing:

Source Description Pros Cons
Equity Capital Owner's funds, venture capital, shares. No repayment obligation, no interest. Dilutes ownership/control, high cost of equity.
Debt Financing Term loans, bonds, debentures, bank overdraft. Tax-deductible interest, no ownership dilution. Fixed repayment (principal+interest), increases financial risk.
Internal Accruals Retained earnings, reserves. No external approval, no flotation cost. Limited amount, may affect dividends.
Grants & Subsidies Government funds, non-repayable. No repayment, often soft conditions. Highly competitive, restrictive use, may have conditions.
Leasing/Hire Purchase Asset use without full purchase. Lower initial outlay, tax benefits. Total cost higher, asset not owned until end.

X. Organizational Structures

Advantages and Disadvantages of Organizational Structures

Structure Advantages Disadvantages
Functional Efficient resource use, deep expertise, clear career paths. Poor cross-functional coordination, slow decision-making, project focus weak.
Projectized Strong project focus, fast decisions, team loyalty to project. Resource duplication, inefficient use of specialists, "tribalism," job insecurity after project.
Matrix (Balanced) Efficient resource use, better communication across functions, flexible. Dual reporting (conflict), power struggles, requires strong PM, complex.

Matrix Organizational Structure:

  • Definition: Hybrid structure where team members report to both a functional manager (for technical expertise, career) and a project manager (for project tasks).

  • Types:

    • Weak Matrix: Functional manager has more power. PM is coordinator/expediter.

    • Balanced Matrix: Power shared equally between PM and functional manager.

    • Strong Matrix: Project manager has primary authority, functional manager provides resources.

  • Key Parameter: "Split of authority" is the defining challenge. Success depends on clear communication and conflict resolution mechanisms.


XI. Risk Management

Risk Identification and Assessment in Project Management

Risk Identification: Process of determining which risks may affect the project and documenting their characteristics.

  • Techniques:

    • Brainstorming: Team/stakeholder workshops.

    • Checklist Analysis: Using historical information or industry lists.

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

    • Assumption Analysis: Challenging project assumptions.

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

    • Expert Judgment: Interviews with experienced personnel.

Risk Assessment (Analysis):

  1. Qualitative Analysis:

    • Probability & Impact Matrix: Rate risk on scales (e.g., 1-5). Plot on matrix to prioritize (High/Medium/Low).

    • Risk Data Quality Assessment: Evaluate accuracy/reliability of data.

  2. Quantitative Analysis (for high-priority risks):

    • Monte Carlo Simulation: Computer model to simulate outcomes and probabilities.

    • Sensitivity Analysis ("Tornado Diagram"): Identifies which risks have most potential impact.

    • Expected Monetary Value (EMV): EMV = Probability × Impact (in monetary terms). Used in decision trees.

Process Flow: Identify → Document in Risk Register → Qualitative Analysis (Prioritize) → Quantitative Analysis (for major risks) → Plan Responses → Monitor.


END OF UNIT 4 NOTES
Aligned with RGPV B Project Management (Nov 2023, Nov 2022) question patterns.

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