Project Planning and Scheduling

Break the project into a work breakdown structure of activities, sequence them with their dependencies, and represent the schedule (bar chart for simple jobs, network for complex ones) against which progress is monitored.

Key formulas & points

Skim these first — then read the full notes below.

  • WBS breaks project into manageable work packages
  • Lead and lag between activities
  • Baseline schedule for progress monitoring

Topic details

Introduction

Project planning defines what work is to be done, in what sequence and by when. It begins with the work breakdown structure (WBS), which decomposes the project into manageable work packages that can be estimated, assigned and tracked.

Scope in B.Tech and GATE syllabus

The simplest schedule representation is the bar (Gantt) chart, which shows each activity against a time axis; it is easy to read but cannot show the logical dependencies between activities, which is its main limitation compared with network methods.

Why this topic matters in practice

Milestone charts highlight key events and deliverables, and resource histograms show how manpower, plant and materials are loaded over time. A baseline schedule, once approved, becomes the reference against which actual progress is measured and controlled.

Key relations & formulas

Formulas (Indian textbook notation)

  • Barchart:activityvstime;nodependencylogicBar chart: activity vs time; no dependency logic

Formulas (Indian textbook notation)

  • MilestonechartforkeydeliverablesMilestone chart for key deliverables

Formulas (Indian textbook notation)

  • ResourcehistogramfromactivityresourceloadingResource histogram from activity resource loading

Notation and sign conventions

Relation 1 —
Barchart:activityvstime;nodependencylogicBar chart: activity vs time; no dependency logic

Formulas (Indian textbook notation)

  • Barchart:activityvstime;nodependencylogicBar chart: activity vs time; no dependency logic
Write this relation with symbols exactly as in Construction Management — PS Ghai before substituting numbers. Examiners award partial marks for a correct setup even when arithmetic slips.
Relation 2 —
MilestonechartforkeydeliverablesMilestone chart for key deliverables

Formulas (Indian textbook notation)

  • MilestonechartforkeydeliverablesMilestone chart for key deliverables
Write this relation with symbols exactly as in Construction Management — PS Ghai before substituting numbers. Examiners award partial marks for a correct setup even when arithmetic slips.
Relation 3 —
ResourcehistogramfromactivityresourceloadingResource histogram from activity resource loading

Formulas (Indian textbook notation)

  • ResourcehistogramfromactivityresourceloadingResource histogram from activity resource loading
Write this relation with symbols exactly as in Construction Management — PS Ghai before substituting numbers. Examiners award partial marks for a correct setup even when arithmetic slips.

Fundamentals and definitions

The work breakdown structure is the foundation of planning: by hierarchically dividing the project into deliverables and then work packages, it ensures nothing is omitted and provides the units for cost estimating, scheduling and responsibility assignment.

Governing relations in practice

Bar charts plot activities as horizontal bars along a time scale; their strength is clarity for communication and their weakness is the inability to represent interdependencies, so a delay to one activity does not visibly ripple to others. This shortcoming led to network techniques (CPM/PERT).

Design and analysis considerations

Dependencies between activities include finish-to-start (the most common), with leads and lags to model overlaps or mandatory gaps; capturing them correctly is essential for a realistic schedule.

Advanced theory and extensions

The baseline schedule freezes the planned dates and resources; comparing actual progress against it reveals slippage early, and resource histograms drawn from the schedule expose peaks that may need levelling to match available resources.

Assumptions and validity limits

State assumptions explicitly before using any relation for project planning and scheduling — steady state, uniform properties, linear elastic material, ideal gas, incompressible flow, etc., as applicable.
Wrong assumptions invalidate the entire solution even when the formula is correct. In Construction Management viva and GATE descriptive questions, listing valid assumptions often earns separate marks.

Step-by-step problem approach

1. Read the question and list given data with SI units (common in Construction Management papers).
2. Draw a neat labelled diagram where applicable — examiners in Indian universities award diagram marks even when arithmetic slips.
3. Identify which relation from this topic applies to project planning and scheduling.
4. Use equation 1:
Barchart:activityvstime;nodependencylogicBar chart: activity vs time; no dependency logic
.
5. Use equation 2:
MilestonechartforkeydeliverablesMilestone chart for key deliverables
.
6. Substitute values, compute, and verify units and sign (direction).
7. State conclusion in one line — e.g. safe/unsafe, stable/unstable, feasible/infeasible.

Applications & exam relevance

Project Planning and Scheduling appears in EPC and infrastructure projects. In Indian civil curricula this topic is tested because it connects theory to planning, scheduling, and contracts.
GATE and semester exams often combine project planning and scheduling with earlier units — revise prerequisites before attempting mixed problems.
Industry interview panels sometimes ask: "Where did you use project planning and scheduling?" — answer with a lab, mini-project, or plant visit example if possible.

Common mistakes in exams

• Treating a bar chart as showing logical dependencies, which it cannot.
• Building a schedule without a proper work breakdown structure.
• Omitting leads and lags between overlapping activities.
• Failing to set a baseline against which to measure progress.

Quick revision checklist

Before attempting project planning and scheduling problems, confirm you can:
1. WBS breaks project into manageable work packages
2. Lead and lag between activities
3. Baseline schedule for progress monitoring
Revise the solved examples in Construction Management — PS Ghai and one previous-year GATE or university paper for this unit.

Worked examples

Try the problem first — open the solution when you are ready to check.

Work packages from a WBS

Problem

A small building project is broken into: substructure, superstructure, finishes and services. If each is further divided into 3 work packages, how many work packages are there, and why is this decomposition useful?

Solution

Number of work packages = 4 major elements × 3 = 12 work packages. This decomposition is useful because each package is small enough to estimate cost and duration, assign to a responsible party, and monitor individually — providing the building blocks for the schedule (bar chart or network) and for cost control.

Conceptual check — Project Planning and Scheduling

Problem

In a Construction Management semester or GATE paper you are asked: "State the main assumption, the governing relation, and one practical consequence of project planning and scheduling." What should a complete answer include?

Exams & GATE

PS Ghai — distinguish bar chart limitations vs network methods.

📖 Standard books (India)

  • Construction ManagementPS Ghai

    Read: Syllabus unit

    CPM, PERT, and project planning