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

UNIT 2: PROJECT MANAGEMENT

1.0 FUNDAMENTALS OF PROJECT MANAGEMENT

1.1 Project Parameters and Attributes

Project: A temporary endeavor undertaken to create a unique product, service, or result.

Key Parameters (often called constraints or triple constraints):

• Scope: What work must be done.

• Time: Schedule/deadline.

• Cost: Budget.

• Quality: Standards and specifications.

• Resources: People, equipment, materials.

• Risk: Uncertain events.

Project Attributes:

• Temporary: Has a defined beginning and end.

• Unique: Not routine; produces distinct deliverables.

• Progressive Elaboration: Details become clearer as project progresses.

• Cross-functional: Requires teams from different departments.

[!TIP] Exam Focus: Distinguish between parameter (a measurable factor like cost) and attribute (a characteristic like temporary). Past papers ask for "parameters" specifically.

1.2 Objectives of Project Management

The primary goal is to achieve all project goals and objectives within the given constraints. Specific objectives include:

1. Deliver the defined scope on time.

2. Complete within the approved budget.

3. Meet required quality standards.

4. Optimize resource utilization.

5. Satisfy stakeholders.

6. Manage and mitigate risks effectively.

1.3 Importance of Project Management

• Provides structured framework for execution.

• Ensures efficient resource allocation and minimizes waste.

• Facilitates clear communication and accountability.

• Enables proactive risk management.

• Increases likelihood of project success and stakeholder satisfaction.

• Provides basis for performance measurement and control.

1.4 Phases of Project Management (PMI/PMBOK® Guide)

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

2. Planning: Establish scope, refine objectives, define course of action (detailed plans for scope, schedule, cost, quality, etc.).

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

4. Monitoring & Controlling: Track, review, and regulate progress and performance; identify necessary changes.

5. Closing: Finalize all activities to formally close the project or phase.

[!TIP] Common Pitfall: Do not confuse Phases (process groups: Initiating, Planning, Executing, M&C, Closing) with Project Life Cycle Stages (which may be more industry-specific like Concept, Design, Build, Operate). In this syllabus, they are treated similarly.

2.0 PROJECT LIFE CYCLE

2.1 Stages of Project Life Cycle

Typically follows a logical sequence:

1. Concept/Feasibility: Idea generation, initial evaluation, feasibility study.

2. Planning/Design: Detailed planning, scope definition, design finalization, scheduling, budgeting.

3. Execution/Implementation: Physical construction/development, resource mobilization, production.

4. Termination/Closing: Handover, commissioning, project review, documentation, closure.

5. Post-Project Evaluation (sometimes included): Review of outcomes vs. objectives.

[!TIP] Exam Link: Nov 2023 & Nov 2022 asked to "Elucidate the various stages of Project Life Cycle." Present the 4-5 stage model clearly.

2.2 Role and Importance of Planning in the Project Life Cycle

• Foundation: Planning is the most critical phase; it defines the roadmap for execution.

• Bridges Gap: Translates project objectives into actionable tasks, schedules, and budgets.

• Reduces Uncertainty: Identifies risks early and plans responses.

• Baseline for Control: Establishes performance measurement baselines (scope, time, cost).

• Improves Communication: Provides a common reference for all stakeholders.

• Increases Efficiency: Prevents rework, optimizes resource use, and avoids delays.

[!TIP] Key Point: "Failing to plan is planning to fail." Emphasize that planning directly influences success in later phases.

3.0 PROJECT PLANNING AND SCHEDULING

3.1 Objectives of Project Planning

• Define clear, measurable project objectives and scope.

• Develop a realistic schedule (timeline) with milestones.

• Establish a detailed cost estimate and budget.

• Identify, analyze, and plan for risks.

• Plan human, physical, and financial resources.

• Define quality standards and processes.

• Plan communication and stakeholder engagement.

• Create baseline documents for performance measurement.

3.2 Project Planning Techniques

3.2.1 Scheduling: Types of Schedules

3.2.2 Network Planning Models (PERT vs. CPM)

[!TIP] Critical Comparison: PERT deals with uncertainty (probabilistic), CPM deals with trade-offs (time-cost). Modern software often blends both.

3.3 Project Planning Tools

3.3.1 Gantt Charts

• Definition: A bar chart that illustrates a project schedule, showing start and finish dates of project elements.

• Use: Visualize project timeline, track progress against plan, show task dependencies and current status.

• DiagramSEARCH: "Gantt chart example project management"

3.3.2 Work Breakdown Structure (WBS)

• Definition: A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.

• Purpose: Breaks down complex projects into manageable chunks (work packages). Forms the basis for scheduling, costing, and assigning responsibilities.

• Rule: "100% Rule" – WBS includes 100% of the project's scope.

• DiagramSEARCH: "Work Breakdown Structure example"

3.3.3 Other Planning Tools

• Network Diagrams: Arrow Diagramming Method (ADM) or Precedence Diagramming Method (PDM) to show activity dependencies.

• Project Management Software: MS Project, Primavera P6, Asana, Trello for scheduling, resource allocation, and tracking.

• Mind Maps: For brainstorming and scope definition.

• Histograms & Pareto Charts: For resource and issue analysis.

4.0 PROJECT COST MANAGEMENT

4.1 Cost Estimating and Cost Improvement Strategies

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

  • Methods: Analogous estimating (top-down), parametric estimating, bottom-up estimating, three-point estimating (PERT), vendor bid analysis.

• Cost Improvement Strategies:

  • Value Engineering (VE): Systematic analysis to achieve required functions at lowest total cost.

  • Value Analysis: Applied to existing projects to reduce cost without affecting function.

  • Design to Cost (DTC): Setting a target cost early and designing to meet it.

  • Make-or-Buy Analysis: Deciding whether to produce in-house or outsource.

4.2 Cash Flow Management

4.2.1 Elements of Cash Flow

• Cash Inflows: Receipts of cash (e.g., client payments, loans, owner equity).

• Cash Outflows: Payments of cash (e.g., material costs, labor, overheads, loan repayments).

• Net Cash Flow (NCF): $$\displaystyle \text{NCF} = \text{Total Cash Inflows} - \text{Total Cash Outflows} $$.

• Cumulative Cash Flow: Sum of NCF over time, showing cash position at any point.

4.2.2 Basic Principles of Cash Flow Estimation

1. Incremental Principle: Only consider cash flows that change due to the decision.

2. Timing Principle: Cash flows are recognized when actually received or paid (cash basis), not when earned or incurred (accrual basis).

3. Consistency Principle: Use same assumptions (inflation, taxation) throughout.

4. After-Tax Principle: Estimate cash flows on an after-tax basis.

4.3 Project Budgeting

• Definition: Aggregating the estimated costs of individual activities or work packages to establish an authorized cost baseline.

• Process: Activity cost estimates → Summation by category → Add contingency reserves → Final approval → Cost Baseline.

• Baseline: Approved, time-phased budget used for performance measurement (EVM).

4.4 Sources of Project Financing

5.0 PROJECT ORGANIZATION AND HUMAN RESOURCE MANAGEMENT

5.1 Organizational Structures

5.1.1 Functional Organization

• Structure: Traditional hierarchy; departments (e.g., engineering, marketing). Project manager has low authority, acts as coordinator/informant.

• Advantages: Efficient resource use, deep expertise, career paths within function.

• Disadvantages: Slow response, poor cross-functional communication, project priorities secondary to functional goals.

5.1.2 Matrix Organization

• Structure: Hybrid; personnel report to both functional manager and project manager. Authority varies.

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

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

  • Strong Matrix: PM has primary authority; functional managers provide resources.

• Advantages: Efficient resource use, improved communication across functions, flexible.

• Disadvantages: Dual reporting causes conflict, power struggles, complexity.

[!TIP] Exam Focus: Nov 2022 asked "Discuss advantages and disadvantages of Organizational Structures." Be prepared to compare all three (Functional, Matrix, Projectized).

5.1.3 Projectized Organization

• Structure: Organization is structured around projects. Project manager has high/full authority over resources and budget. Team is co-located often.

• Advantages: Fast decision-making, strong project focus, cohesive team.

• Disadvantages: Inefficient resource use (duplication), lack of career paths after project, potential for "empire building."

5.2 Role of Project Manager

5.2.1 Key Responsibilities and Skills

• Responsibilities: Develop plan, execute, monitor & control, manage stakeholders, manage team, manage risks, report.

• Skills:

  • Technical: Knowledge of project domain.

  • Leadership: Vision, motivation, conflict resolution.

  • Communication: Clear, frequent, tailored to audience.

  • Negotiation & Influence: Secure resources, resolve conflicts.

  • Problem-Solving: Analytical and decisive.

5.2.2 Contribution to Project Success

• Single point of accountability.

• Integrates all project aspects (scope, time, cost, quality, etc.).

• Drives team performance and stakeholder satisfaction.

• Manages constraints and changes proactively.

5.3 Team Development

5.3.1 Five-Stage Team Development Model (Tuckman's Model)

[!TIP] Exam Link: Nov 2022 asked "What are the parameters associated with five stage team development model?" – Describe each stage's characteristics and PM's role.

6.0 CONTRACTS AND LEGAL ASPECTS

6.1 Definition and Nature of Contract

• Definition: An agreement enforceable by law. (Indian Contract Act, 1872: "An agreement is a promise... and every promise... forming the consideration for each other is an agreement.")

• Nature: Creates legal obligations, based on mutual consent, has specific terms, is binding.

6.2 Essentials of a Valid Contract (Section 10, Indian Contract Act)

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

2. Lawful Consideration: Something of value exchanged; must be lawful.

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. Certainty of Meaning: Terms must be clear, not vague.

7. Possibility of Performance: Act must be possible.

8. Not Declared Void: Should not be expressly declared void by law.

6.3 Types of Contracts (Brief Overview)

• Based on Execution:

  • Executed: Both parties have performed.

  • Executory: One or both parties yet to perform.

• Based on Form:

  • Oral/Verbal: Spoken agreement.

  • Written: Documented (preferred for projects).

  • Specialty/Under Seal: Formal written document with seal.

• Based on Performance:

  • Bilateral: Mutual promises (most common).

  • Unilateral: One promise in return for an act.

• Common Project Types (for context):

  • Fixed-Price/Lump Sum: Agreed total price.

  • Cost-Reimbursable: Actual costs + fee.

  • Time & Material (T&M): Rates for time and materials used.

7.0 RISK MANAGEMENT

7.1 Concept of Risk in Project Management

• Risk: An uncertain event or condition that, if it occurs, has a positive or negative effect on project objectives (scope, schedule, cost, quality).

  • Threat: Negative risk.

  • Opportunity: Positive risk.

• Key Attributes: Probability (likelihood), Impact (severity).

• Risk Management: Proactive process of identifying, analyzing, and responding to risks.

7.2 Risk Identification Techniques

Goal: Create a list of potential risks.

1. Brainstorming: Team/experts generate ideas freely.

2. Checklist Analysis: Using historical information or standardized lists.

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

4. Delphi Technique: Anonymous, iterative expert consensus.

5. Assumption Analysis: Examining project assumptions for risks.

6. Diagramming Techniques:

   • Cause-and-Effect (Ishikawa/Fishbone): Identify root causes.

   • Flowchart: Map process to find failure points.

7. Documentation Reviews: Check plans, contracts, previous lessons learned.

[!TIP] Exam Link: Nov 2022 asked "Explain the term 'risk'... How do you identify the risks?" – Define risk clearly and list 4-5 techniques with brief explanation.

8.0 PROJECT MONITORING AND CONTROL

8.1 Performance Measurement

8.1.1 Earned Value Management (EVM)

Integrates scope, schedule, and cost to measure performance and forecast.

Key Formulas:

Forecasts:

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

• Estimate to Complete (ETC): $$\displaystyle ETC = EAC - AC $$.

• Variance at Completion (VAC): $$\displaystyle VAC = BAC - EAC $$.

[!TIP] Critical: Memorize PV, EV, AC definitions and CV/SV/CPI/SPI formulas. Nov 2022 asked "Value of work performed" (3m) – explain EVM briefly with key terms.

8.2 Control Mechanisms

8.2.1 Control Charts (Statistical Process Control - SPC)

• Purpose: Monitor process variation over time to detect if process is in statistical control.

• Key Components:

  • Center Line (CL): Process mean (e.g., $\bar{X}$ for X-bar chart).

  • Upper Control Limit (UCL): Typically $\bar{X} + 3\sigma$ or $$\displaystyle \bar{X} + A_2 \bar{R} $$.

  • Lower Control Limit (LCL): Typically $\bar{X} - 3\sigma$ or $$\displaystyle \bar{X} - A_2 \bar{R} $$.

• Common Types:

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

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

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

  • c-Chart: Monitors number of defects per unit.

• Interpretation:

  • In Control: Points within UCL/LCL, no non-random patterns.

  • Out of Control: Points outside limits or showing runs, trends, cycles → Investigate assignable causes.

• Application in Projects: Monitor quality of deliverables (e.g., concrete strength, defect rate in software modules).

[!TIP] Exam Focus: Nov 2022 asked "Explain control charts" (14m). Describe purpose, construction (CL, UCL, LCL), interpretation (rules for out-of-control), and give a project example (e.g., monitoring defect density).