Productivity Management and Project Management

What is the Productivity Paradox?

Organisations often invest heavily in specific functions (e.g., manufacturing, CRM, inventory) yet fail to win orders or improve business performance. This gap between local productivity gains and global business outcomes is the Productivity Paradox.

Intuitively: a factory may be highly efficient, but customers still complain of delays or shortages. The traditional measure of productivity —$\text{Productivity} = \frac{\text{Output}}{\text{Input}}$— can show improvement in one area while the organisation as a whole stagnates or deteriorates. The paradox arises because output must be replaced with useful output — only activities that contribute to order-winning create real value. The rest is waste.

Illustrative Examples

1. Excessive Travel Distance for a “Good” Product

A company with four product lines (A–D) introduced products C and D late, expecting them to be strong. Data on total distance travelled on the shop floor (raw material → sub-assembly → final assembly):

Product C is supposed to be good, but it travels far too much on the shop floor. The result: high cost and long lead time, making it uncompetitive. The manufacturing system itself is inefficient, despite the product’s potential.

2. Non‑Manufacturing Activities Dominate Lead Time – Standard Orders

Data from 79 standard orders:

Nearly half the total lead time is consumed by scheduling – a non‑manufacturing planning activity. Good manufacturing exists, but scheduling inefficiency makes the product uncompetitive.

3. Order Handling + Scheduling Dominate – Special Orders

Data from 13 custom orders:

Understanding customer requirements, estimating cost, communicating, obtaining approval (order handling), then detailed planning (scheduling) together consume 84% of total lead time (~5 months). The manufacturing system is efficient, but the front‑end processes destroy competitiveness.

4. Back‑and‑Forth in Capital Goods Order Processing

A company selling customised machine tools follows a lengthy chain:

Design, process planning, and cost estimation iterate (two‑way arrows). After weeks, the final quote reaches the customer – but the delay may be unacceptable. Again, good technical capability exists, but the process is slow and uncoordinated.

Causes of the Productivity Paradox

1. Piecemeal improvements (local optima ≠ global optima) – Excelling in one function (e.g., manufacturing) while ignoring others (e.g., order handling) does not guarantee order‑winning.
2. Productivity is moderated by the supply chain – Even if one entity improves, weak links elsewhere block value delivery.
3. Yesterday’s order winners become today’s order qualifiers – Customer preferences shift. E.g., in the 1980s, “quality” was an order winner; today it is merely an order qualifier.
4. Value migration – As markets and demographics change, organisations must realign; failure to do so leads to profitless turnover (top line growth, bottom line shrinks).

Exam tip: The Productivity Paradox warns against measuring productivity in isolation. Always ask: Does this improvement contribute to order‑winning? If not, it may be waste.

Ground Rules for Managing Productivity

• Rule 1: Only activities that create value contribute to productivity; everything else is cost or waste.
• Rule 2: The locus of reference for value is the customer, not the organisation.
• Rule 3: Multiple entities (suppliers, distributors, service providers) significantly influence value creation.

The Notion of a Value Stream

A value stream is the path along which value flows, from initial concept (value proposition) through multiple entities, to the ultimate customer.

Example: Passenger Car

Ore mining → tiers of component/sub‑assembly suppliers → vehicle assembly → outbound logistics → dealership network → sales → after‑sale service.

Example: Holiday Package

Conceptualisation of the package → travel & ticketing → resort management → facilities at each destination (language, culture, policies) → inter‑destination travel → food & beverages.

All these entities collectively create the value.

Value Stream Competition

“Company A competes with Company B” is superficial. More accurately: the value stream associated with Company A competes with the value stream associated with Company B.

• A company may have an excellent product and manufacturing, but a badly developed supply base → value is blocked.
• A company may have a unique service, but last‑mile franchisees fail to deliver → value is blocked.

When a value stream is poorly configured (blockages exist), the productivity paradox emerges: local excellence does not reach the customer.

Key Takeaways

• The Productivity Paradox occurs when local productivity improvements do not translate into business gains.
• Causes include piecemeal focus, supply chain weaknesses, shifting order winners/qualifiers, and value migration.
• Use useful output (only what wins orders) in productivity measures: $\text{Value-based Productivity} = \frac{\text{Useful Output}}{\text{Input}}$.
• A value stream encompasses all entities that contribute to value creation; it is the unit of competition.
• Blockages in the value stream – not just internal inefficiency – are the root of the paradox.

Non-Value Added Activities and Lean Management

Value is the central lever for productivity. Only activities customers pay for are value-adding. Many business activities add no value—or even subtract value—and directly harm productivity. Eliminating such waste is the core of Lean Management, a structured framework built on Just‑in‑Time (JIT) and Total Quality Management (TQM).

---

Non‑Value Added Activities

Any activity that consumes resources without creating value the customer is willing to pay for. Examples:

• Accumulating inventories (raw material, WIP, finished goods)
• Machine breakdowns, defects, rework
• Waiting for materials, tools, information
• Moving parts over long distances (excess material handling)
• Double handling, over‑production
• Unnecessary paperwork, data entry, counting parts
• Poorly planned meetings, excessive approvals

Categories of Waste

Common Characteristics of Non‑Value Added Activities

• The customer will not pay for any of them.
• They negatively impact time, cost, quality, and delivery.
• They are value‑subtracting → productivity suffers.

Exam tip: Memorise the three categories with 2–3 examples each. The “customer will not pay” test is the quickest way to identify waste.

Key Takeaways

• Non‑value added activities = waste → lower productivity.
• Three categories: inventory, process, planning.
• All waste degrades time, cost, quality, delivery.
• Customers pay only for value‑adding steps.

---

Lean Management Framework

Lean enterprise – an organisation that deploys mechanisms to define value, identify the value stream (e.g. concept‑to‑launch, order‑to‑delivery, raw material‑to‑finished product), and systematically remove Muda (waste). Other forms of waste: Mura (unevenness), Muri (excess).

Basic Premise

Eliminate waste to create a smooth value stream.

Enabling Mechanisms

• Just‑in‑Time (JIT) – systematically expose problems by reducing inventory.
• Total Quality Management (TQM) – systematically and sustainably solve problems.

Tools & Techniques (representative)

The Benefit: “Less is More Productive”

With the same capacity, produce more; or for a given output, use fewer resources. Comparative example – Toyota vs. GM (automotive industry):

Exam tip: The Toyota/GM table illustrates that doing less (fewer engineered parts, fewer suppliers, fewer employees) can yield more output per employee. This is the essence of lean productivity.

Key Takeaways

• Lean = define value → map value stream → remove waste (Muda, Mura, Muri).
• Two pillars: JIT (expose problems) and TQM (solve problems).
• Tools range from setup reduction to process mapping.
• “Less is more productive” – fewer resources, same or higher output.

---

The Two Main Pillars: Just‑in‑Time and Total Quality Management

Water Flow Analogy

• Ship = daily operational rate (e.g. cars per shift, loan applications processed per day)
• Water = inventory (materials, excess people, idle machine capacity, unused space)
• Rocks = problems (poor quality, defective material, bottlenecks, machine breakdowns, managerial constraints)

Two approaches:

1. Pour water (increase inventory) – raises water level so the ship sails over the rocks, but hides the problems.
2. Chisel the rocks (reduce inventory) – lower the water level deliberately; when the ship cannot sail, expose the rock and fix it.

Lean chooses only to chisel – never to pour water.

Progressive Waste Elimination

1. Remove some inventory (water)
2. Problems (rocks) surface → ship cannot sail
3. Use JIT to expose the problem; use TQM to solve it
4. Repeat → water level (waste) declines continuously

Lean is a relative state – no absolute “lean”; organisations become progressively leaner.

Exam tip: The water‑rock analogy is the classic explanation for why JIT and TQM are inseparable. Always connect: reduce inventory → expose problem → solve problem → further reduce inventory.

Key Takeaways

• JIT = systematically expose problems (by reducing inventory).
• TQM = systematically solve problems (root‑cause fixes).
• Lean requires an organisation‑wide mechanism with top management support.
• Inventory includes materials, people, capacity, and space – any idle resource.
• The process is iterative: expose → solve → reduce → expose again.

Elements of a JIT Manufacturing System

Just-in-time (JIT) manufacturing systematically exposes and eliminates waste (inventory, excess manpower, idle capacity, unnecessary space). The water-flow analogy: inventory is water that hides rocks (problems); lowering the water level reveals problems that must be solved. Modifying structural and planning methods removes the “water” – i.e., waste.

Three fundamental modifications are needed:

1. Redesign the manufacturing system into a chain of internal customers.
2. Pull-based production planning and control (supermarket model).
3. Setup-time reduction → lot-size reduction.

Internal Chain of Customers

Each process is physically and logically linked to the next: the preceding process serves the succeeding process as its internal customer.

• Traditional layout: resources grouped by function (all grinders in one area, all mills in another). Material moves long distances, creates waiting, hides waste.
• JIT layout: resources regrouped by product family. Each product line has its own dedicated cell containing the needed machines and support (stores, material planning).

Advantage: simpler, more effective control; reduced travel distances and waiting; waste becomes visible.

Pull-Based Planning (Supermarket Model)

Instead of pushing work via schedules, each downstream step pulls what it needs from the upstream step – exactly as a supermarket shelf is replenished by the back store, which in turn triggers procurement.

• Downstream process withdraws required items.
• Upstream process only produces enough to replace what was taken.
• Eliminates overproduction and excess inventory.

Setup-Time Reduction and Lot-Size Reduction

• Setup = changeover time between product variants.
• Long setup → large batch sizes (to absorb the cost of downtime).
• Reducing setup time allows smaller batches, eventually single-piece flow.
• Methods: tool pre‑setting, quick‑change fixtures, parallel operations.

Kanban System for Inventory Reduction

Kanban (card or signal) controls the flow between stages using standard containers.

• Suppose 1,000 pieces of inventory exist between two stages. Put them in 10 containers of 100 each = 10 Kanban cards.
• Periodically remove one container → inventory drops to 900, revealing problems (e.g., machine breakdowns, defects) that were hidden by the buffer.
• The number of Kanban cards is deliberately reduced over time to force continuous improvement.

Supplier Collaboration

• Long-term partnerships with suppliers ensure defect-free, on-time deliveries.
• Reduces incoming inspection, rejects, and buffer stock.

Common Goal

All JIT elements aim to lower waste. As waste is removed, the proportion of value‑adding activities increases. The paradox “less is more productive” becomes reality – the organization becomes lean.

Exam tip: The “water flow” analogy is a classic exam question. Inventory hides problems; lowering it exposes them. Be ready to explain how each JIT element (cell layout, pull, Kanban, setup reduction) contributes to waste removal.

Key takeaways

• JIT requires physical restructuring into product-focused cells – an internal chain of customers.
• Pull planning controls production via downstream demand (supermarket model), eliminating push-driven overproduction.
• Setup-time reduction → smaller lot sizes → less work-in-process inventory.
• Kanban uses cards and standard containers to cap and systematically reduce inventory.
• Supplier collaboration ensures quality and on-time delivery, cutting inspection waste.
• All elements work together to expose and eliminate waste, raising the share of value-added time.

---

Process Mapping for Non-Value-Added (NVA) Analysis

Process mapping chronologically lists every step in a process, classifying each activity to identify waste. It is the essential first step toward eliminating non-value-added (NVA) work.

Example: Subassembly Process Map (81 activities)

A factory suspected long lead times in a subassembly were delaying final assembly. They traced every step from material request to completion. Activities were categorised as:

Summary of the 81 activities (lead time for one batch):

Only 6.3% of total lead time (106 out of 1,680 hours) actually added value from the customer’s perspective. The other 93.7% is waste – the customer would not pay for it.

Exam tip: The 6.3% value-add figure is a striking demonstration of how much waste typical processes contain. Expect to interpret a similar summary table and calculate the proportion of NVA activities.

Four Methods to Map a Process

Types of Data to Collect

• Distance travelled by materials.
• Elapsed time (timestamps from start to finish).
• Assets and people deployed (headcount, equipment used).
• Activity category (waiting, moving, value-add, cost-add, etc.).
• Ownership – who is responsible for each step.

Example: Procurement Process Data

A procurement process was mapped into three high-level activities:

The same data can be sliced differently (resource consumption, cost, defect rates) depending on the improvement goal.

Purpose

Process mapping provides the detailed snapshot needed to:

• Identify the largest sources of waste (e.g., waiting, rework).
• Launch targeted improvement efforts (e.g., “Why do we wait 53 times? How can we reduce moving?”).
• Measure baseline performance before and after changes.

Key takeaways

• Process mapping chronologically lists every step and classifies it as value-add, waiting, moving, or cost-add.
• In the example, only 6.3% of lead time was value-add – the rest is waste.
• Four methods: customer walkthrough (most reliable), collaborative charting, interviews, executive judgment (least reliable).
• Collect data on time, distance, people, category, and ownership.
• The map is the basis for waste elimination – after mapping, one can analyse causes and plan improvements.

The Process Improvement Methodology

Process improvement requires a structured, sustainable methodology to eliminate waste. A service organization example: customers complained of excessive delays, errors, and too much paperwork.

Broad objectives set for the exercise:

• Reduce time and paperwork by at least 25%
• Develop better job descriptions and procedures
• Deliver tangible cost savings
• Implement an online system

Process mapping (from previous step) identified 79 activities. Data collected on a sample of past cases:

Brainstormed improvement ideas were colour-coded by implementation horizon:

• Low-hanging fruit (e.g., process same day, send incomplete requests back) – implementable immediately with approval.
• Medium-term (e.g., change data collection format, share customer info) – takes weeks or up to a month.
• Long-term (e.g., online system) – significant time and investment.

Results after implementation (all ideas executed):

• Response time: average dropped to 1.1 days (sample of 25)
• Rejects: reduced to 0%
• Non-value added activities eliminated: 17

The 7-Step Methodology

A generalizable, structured approach any organization can adopt:

Step 2 requires classifying all activities into three categories:

• Value-adding (VA): Activities the customer is willing to pay for.
• Non-value adding (NVA): Activities the customer will not pay for.
• Necessary but non-value adding (NNVA): Activities that must remain temporarily (e.g., inspection) but should eventually be eliminated via better process control.

Organization Structure for Continuous Improvement

After high-level process mapping, detailed projects are carved out. Each project follows the 7-step methodology. This structure aligns with lean management and ensures waste elimination is tackled systematically.

Exam tip: The three activity categories (VA, NVA, NNVA) are central to process mapping. NNVA is a practical concession – it is still waste, but cannot be eliminated immediately. Distinguish it from pure NVA.

Key takeaways: Process Improvement Methodology

• A structured methodology prevents the "productivity paradox" – wrong improvements that waste effort.
• Necessary but non-value adding activities are temporary; the goal is their eventual elimination.
• Low-hanging fruit should be implemented first to build momentum.
• The methodology is consistent with lean management and supports sustainable productivity gains.

Performance Metrics for Productivity Improvement

Traditional performance measures (financial reports, variance analysis, spend analysis) serve control – they are like a scoreboard: historical, for top management, and tied to incentives. But for real-time operational improvement, workers need trajectory-of-the-ball measures.

Basketball analogy: Players cannot look at the scoreboard while playing; they need to track the ball's trajectory. Coaches watch both. In business, employees need operational, non-financial measures to adjust on the fly; managers need financial reports (scoreboard) for strategic overview and evaluation.

New role for performance metrics: Learning and improvement – not just control or incentives. Measures should be:

• Operational (not purely financial)
• Process-oriented
• Available to everyone doing the work

Categories of Performance Metrics

Measures for Improvement (local and/or global)

Worked example – Lead Time to Work Content From the process mapping case: Work content (VA) = 106 hours, Total lead time = 1,680 hours. $\text{Ratio} = \frac{1680}{106} = 15.85$ This indicates very low productivity; an ideal ratio would be 1–2.5.

Measures for Learning and Innovation (global – division/organization level)

All these measures, when improved, directly increase productivity by reducing waste and enhancing capability.

Exam tip: Distinguish "measures for improvement" (operational, local/global) from "measures for learning and innovation" (more strategic, often global). Both are non-financial and process-oriented – opposite of traditional control metrics.

Key takeaways: Performance Metrics

• Shift from financial control to operational learning – treat metrics as "trajectory of the ball", not just the scoreboard.
• Lead time to work content ratio > 5 indicates process waste; ideal is 1–2.5.
• Improvement metrics are local or global; learning metrics are typically global.
• ECNs, certified deliveries, and training time signal how fast the organization learns and improves.

Visual Control Aids for Productivity Improvement

Lasting productivity improvement rests on three pillars: it must be data-driven (not gut-feeling), employee-centred (the people doing the work drive the changes), and continuous (not a one-off event). Visual control aids are a single mechanism that satisfies all three simultaneously.

A visual control system is an operational measurement system that:

• Provides the trajectory of performance (not just end results) – analogous to watching the ball’s path in a basketball game, not only the final score.
• Is maintained by the operating personnel themselves (manufacturing or service).
• Is visually displayed – prominently on a board, screen, or in the work area – showing chosen measures monitored on an appropriate time basis (hourly, daily, weekly).

Examples of Measures

Daily/shift production, number of rejects, daily shipments, stoppages/interruptions per hour, schedule adherence, lead time, cost of wastage, quantum of improvements – all can be captured on a visual board.

Schematic Representation

In a manufacturing (or service) work area, a visual display board is placed alongside the workspace. For example, the board might show three measures: Quality, Lead Time, and Schedule Adherence, plotted over time. The group of employees uses this data to investigate and implement improvements.

Options for Visual Control Systems

• Prominent display boards with charts.
• Andon lights: coloured lights (red/yellow/green) that signal status (e.g., stop production, need help, normal).
• Floor paintings: visual demarcation of areas, paths, or inventory levels.
• Colour coding: e.g., red paint on a stack of steel sheets marks safety stock level; yellow marks reorder level; green indicates sufficient inventory.
• Kanban cards: visual signals for pull production.
• Poka-yoke (fool-proofing) devices: often visual, preventing errors.
• Electrical signals and other creative solutions.

Exam tip: The key is that options are limited only by creativity. Any visible indicator that triggers action qualifies.

Worked Example: Oil Waste Reduction

In a factory using machine tools with high-speed lubricant oil, excessive oil wastage occurred. The operating team set up a visual control board monitoring oil consumption (in monetary terms). Seeing the trend, they fabricated a simple gravity-based structure from slotted steel angles:

• Drilled angles are welded into a sloped trough.
• Collection trays are placed on both sides to catch dripping oil.
• After machining, components are placed on top of the sloped structure instead of on a pallet.
• Oil drips down the slope into the trays.

Result: Within the first month, 80% of the wasted oil was recovered – a huge saving. The idea came from the employees themselves, not from industrial engineers (who later built a more sophisticated version).

This example shows how visual control aids engage employees with the problem, capture their mind-space, and push them into thinking about solutions. They complement productivity improvement and waste elimination by fostering ownership.

Key Takeaways

• Visual control systems are data-driven, employee-centred, and continuous.
• They display real-time trajectory of key metrics, not just final outcomes.
• Options include boards, Andon lights, floor markings, colour codes, Kanban, Poka-yoke.
• The oil recovery example demonstrates how employee-driven visual controls can yield immediate, large savings.
• Visual aids capture attention and stimulate problem-solving on the shop/office floor.

---

Implementation Challenges in Lean Management

All concepts covered so far (JIT, Lean, Pull Scheduling, Process Mapping) are simple – even obvious. Yet the track record of implementation is poor. Why?

Two core features of improvement:

1. Desire for excellence is a cultural issue – it must be invested in as a habit, not a technology.
2. God is in the details – improvement is data-intensive, time-consuming, patient work. No shortcuts.

Three Key Challenges

Middle Management Issues

Common complaints from middle managers:

• “We are not familiar with the tools.”
• “It's not my job; no one feels motivated.”
• “We do not feel empowered.”
• “Department is too busy.”
• “We can’t communicate well with other areas.”

How to Address End-of-the-Road Syndrome

Expand the improvement journey along three dimensions:

Reasons Why Implementation Fails Despite Simple Concepts

• Gap between preach and practice: when leadership talks lean but behaves oppositely.
• Lack of stamina: improvement requires enormous, sustained effort.
• Leading is difficult: top management must lead from the front.
• Empowerment issues: middle management may refuse empowerment, or top management holds control tightly.
• Tunnel vision: top management lacks long-term perspective; cultural change is a long affair.
• Crisis paradox: either when there is no crisis (complacency) or when crisis is so severe that improvement efforts are deferred.

Exam tip: The three challenges (Starting Trouble, Midway Breakdown, End-of-the-Road Syndrome) are high-yield. Remember the middle management complaints and the three “step out” directions for overcoming End-of-the-Road.

Key Takeaways

• Concepts are simple, but implementation is difficult due to cultural and detail-oriented nature.
• Three key challenges: Starting Trouble, Midway Breakdown, End-of-the-Road Syndrome.
• Middle management faces tool unfamiliarity, lack of empowerment, and time pressures.
• To escape End-of-the-Road: step out of shop floor, step out of organization, step out of current mindset.
• Failure often stems from preach-practice gaps, insufficient stamina, poor leadership, and short-term thinking.

Project Management

Organizations perform work to create value. Work is classified into operations and projects.

• Operations: Ongoing, repetitive, day-to-day activities (e.g., running metro services, ticketing, regular maintenance).
• Projects: Temporary, unique endeavours with a defined start and end, aimed at creating a unique product, service, or output (e.g., building a new metro corridor, upgrading stations, implementing new signalling systems).

Example – Delhi Metro Rail Corporation (DMRC): Operations = running trains daily, fare collection, routine maintenance. Projects = constructing a new line, modernising ticketing technology.

Project Management Goals – The Four Dimensions (Q, C, D, F)

The same four competitive dimensions from operations (Quality, Cost, Delivery, Flexibility) apply to projects, reinterpreted:

Why Projects Fail (Time and Cost Overruns)

Common reasons (from business media) for exceeding budgets or missing deadlines:

• Inadequate preparation and planning
• Inaccurate time/cost estimates
• Lack of knowledge or technical talent
• Wrong site choice
• Insufficient infrastructure/equipment
• Regulatory changes
• Funding constraints

Project Life Cycle – The S‑Curve

When plotting % of project completed vs. time, the curve is S‑shaped:

1. Slow start – Team learns specifications, scope, new tools/methods; initial planning, resource mobilisation, site preparation consume time.
2. Quick momentum – Groundwork complete; actual work (construction, coding, installation) occurs; workflows stabilised, resources fully utilised, productivity peaks.
3. Slow finish – Testing, module integration, quality checks, documentation, final approvals, handover activities slow progress.

Exam tip: The S‑curve explains why early delays often amplify – the slow start is natural, but inadequate planning can extend it and jeopardise the momentum phase.

Project Network Diagrams

A project network diagram visually represents the sequence and dependencies of activities. It is used to determine the total project duration, identify the critical path, and manage schedule risk.

Steps to Construct (from Activity Data)

1. List all activities with their predecessor(s) and duration.
2. Represent each activity as a circle (node) labelled ActivityName (Duration).
3. Draw arrows from each predecessor to its dependent activity.
4. Place activities with no predecessor at the start; activities with multiple predecessors wait until all are complete.

Worked Example

Note: The example does not specify durations for activities B and G. Missing durations are marked ?.

Constructed network diagram (arrows represent “→ starts after”):

A(6)
├──→ B(?) ──→ C(7) ──┬──→ L(3) ──┐
├──→ D(2) ──→ E(4) ──→ F(10)      │
├──→ K(9) ──────────→ L(3) ──────→ M(5)
G(?)
└──→ H(10) ──┬──→ I(6) ──────────→ M(5)
J(13) ──────→ I(6)

The diagram shows all dependencies. Because durations for B and G are unknown, the total project duration cannot be computed.

Exam tip: When building a network diagram, ensure all predecessors are satisfied before an activity can start. Missing durations are common in exam questions – you will be given a complete data table.

Key Takeaways

• Projects are temporary and unique; operations are ongoing and repetitive.
• Project success is judged on the same four dimensions as operations: quality, cost, delivery, flexibility.
• The project life cycle follows an S‑curve: slow start → rapid momentum → slow finish.
• A project network diagram maps activity dependencies and durations; it is essential for schedule analysis.
• When constructing a diagram, place activities in the order of dependencies and label each node with its activity name and duration.

Key Definitions

• Early Start (ES) – the earliest possible time an activity can begin, given predecessor constraints.
• Early Finish (EF) – the earliest time an activity can complete (ES + duration).
• Late Start (LS) – the latest time an activity can start without delaying the entire project.
• Late Finish (LF) – the latest time an activity can finish without delaying the project.
• Slack (or Float) – the amount of time an activity can be delayed without affecting project completion.
  • $\text{Slack} = \text{LF} - \text{EF} = \text{LS} - \text{ES}$
• Critical Path – the sequence of activities with zero slack; its total duration determines the project’s minimum completion time. Any delay on a critical activity directly delays the project.

Forward Pass – Computing ES and EF

Procedure:

1. Start from the beginning node(s). Set ES = 0 for any activity with no predecessor.
2. For each activity, $\text{EF} = \text{ES} + \text{Duration}$
3. For a successor activity, $\text{ES} = \max(\text{EF of all immediate predecessors})$
4. The project completion time is the maximum EF among all ending nodes.

Exam tip: In a forward pass, the ES of a merge point equals the largest EF among its predecessors – you wait for the longest preceding path.

Worked example – given network (activities and durations in weeks)

Forward pass calculations (left to right):

• A: ES = 0, EF = 0+6 = 6
• K: ES = max(EF of A) = 6, EF = 6+9 = 15
• B: ES = 6, EF = 6+4 = 10
• C: ES = max(EF of B) = 10, EF = 10+7 = 17
• L: ES = max(EF of K, EF of C) = max(15,17) = 17, EF = 17+3 = 20
• D: ES = 6, EF = 6+2 = 8
• E: ES = max(EF of D) = 8, EF = 8+4 = 12
• F: ES = max(EF of E) = 12, EF = 12+10 = 22
• G: ES = 0, EF = 0+2 = 2
• H: ES = max(EF of G) = 2, EF = 2+10 = 12
• J: ES = 0, EF = 0+13 = 13
• I: ES = max(EF of H, EF of J) = max(12,13) = 13, EF = 13+6 = 19
• M: ES = max(EF of L, EF of I) = max(20,19) = 20, EF = 20+5 = 25

Project completion time: max(EF of F, EF of M) = max(22,25) = 25 weeks.

Backward Pass – Computing LS and LF

Procedure:

1. Start from the ending node(s). Set LF equal to the project completion time (25 weeks).
2. For each activity, $\text{LS} = \text{LF} - \text{Duration}$
3. For a predecessor activity, $\text{LF} = \min(\text{LS of all immediate successors})$

Backward pass calculations (right to left):

• M: LF = 25, LS = 25−5 = 20
• F: LF = 25, LS = 25−10 = 15
• E: successor F → LF = LS of F = 15, LS = 15−4 = 11
• D: successor E → LF = 11, LS = 11−2 = 9
• I: successor M → LF = 20, LS = 20−6 = 14
• J: successor I → LF = 14, LS = 14−13 = 1
• H: successor I → LF = 14, LS = 14−10 = 4
• G: successor H → LF = 4, LS = 4−2 = 2
• L: successor M → LF = 20, LS = 20−3 = 17
• C: successor L → LF = 17, LS = 17−7 = 10
• B: successor C → LF = 10, LS = 10−4 = 6
• K: successor L → LF = 17, LS = 17−9 = 8
• A: successors K, B, D → LF = min(LS of K, B, D) = min(8,6,9) = 6, LS = 6−6 = 0

Slack and Critical Path

Slack = LF − EF (or LS − ES). Summarising all activities:

Critical Path: A → B → C → L → M (all slack = 0). Duration = 6 + 4 + 7 + 3 + 5 = 25 weeks – matches project completion.

Exam tip: The critical path is the longest path through the network – it governs project duration. Non‑critical activities have positive slack; they can slip within that slack without delaying the whole project.

Connection to Process Bottlenecks

The critical path is the project’s equivalent of a process bottleneck: it determines the maximum throughput (minimum completion time). Just as the resource with the least capacity constrains a process, the critical path – the longest sequence of dependent activities – constrains the project duration. Activities on the critical path are critical; any delay there directly lengthens the project.

Key Takeaways

• Forward pass: ES = max(EF of predecessors); EF = ES + duration. Project completion = max(EF of ending nodes).
• Backward pass: LF = min(LS of successors); LS = LF − duration. Start with LF = project completion at ending nodes.
• Slack = LF − EF = LS − ES. Zero slack → critical.
• Critical path is the longest path; it defines the minimum project duration (25 weeks in the example).
• More than one critical path can exist – all must be managed as bottlenecks.

Critical Path Identification: Alternate Path Enumeration Method

Finding the critical path (the sequence of activities that determines the shortest possible project duration) can be done by computing slack from early/late starts and finishes (the method covered earlier). However, for small-scale networks a more intuitive approach works: enumerate all possible paths from the start node to the end node, sum the durations of activities on each path, and identify the path with the longest total duration. That path is the critical path, and its duration equals the project duration.

Worked example: Six-activity network (A–M)

Paths and durations (durations in weeks):

The longest duration is 25 weeks (Path 1). Therefore:

• Critical path: A → B → C → L → M
• Project duration: 25 weeks

This result matches the slack-based analysis from the previous video, confirming Path 1 as the critical path.

Exam tip: Path enumeration is efficient only when the network has few paths. For large, complex networks (many activities, many dependencies), enumerating all paths becomes impractical. The slack method (early/late start/finish) scales better.

Comparison: Enumeration vs. Slack Method

Key takeaways

• The critical path is the longest path through the project network.
• Its length gives the minimum project duration.
• For small networks, list all start-to-end paths, sum durations, pick the max.
• For large networks, compute slack (zero-slack activities lie on the critical path).

---

Project Cost Structures and Cost-Time Trade-Offs

Projects involve two broad categories of cost, and managers must balance them to find the optimal project duration.

Direct Costs

Direct costs are expenses directly tied to executing project activities: labour wages, equipment rental, materials, overtime, and the cost of accelerating an activity (e.g., using air freight instead of sea freight, hiring specialist consultants, renting extra machines).

• If the project runs slowly (long duration), fewer resources are used per week → low direct cost.
• If the project is accelerated (short duration), more resources are packed into each week → high direct cost.

Indirect Costs

Indirect costs are general overheads of running the project itself: site office, supervision salaries, utilities, project management team, interest on blocked capital, and opportunity cost (lost revenue due to project delay).

• Indirect costs increase as project duration increases (longer overhead period).

Total Cost and Optimal Duration

Total cost = Direct cost + Indirect cost. The trade-off is:

• Very short project → direct cost dominates (high acceleration expenses).
• Very long project → indirect cost dominates (high overhead).

The optimal project duration minimises the total cost.

Crashing: Accelerating Activities

Crashing means reducing an activity’s duration by spending additional direct cost. Each activity has a crash time (the shortest technically feasible duration) beyond which it cannot be reduced, no matter how much money is spent. The cost per week of accelerating is the extra direct cost incurred for each week saved.

Example dataset

Activities A–M have current durations and crash data. For illustration:

• Activity B: current time 4 weeks, crash to 3 weeks costs ₹700 per week saved.
• Activity F: current 10 weeks, can be crashed down to a minimum of 7 weeks, each week saved costs ₹500.
• Indirect cost: ₹1000 per week of project duration (overall project overhead).

Exam tip: The cost of accelerating an activity is a direct cost increase. The trade‑off is between paying more to crash (direct) vs. paying less overhead (indirect) because the project finishes earlier. The goal is to minimise total cost.

Key takeaways

• Direct cost: cost of executing and accelerating activities. Rises when project is shortened.
• Indirect cost: project overhead. Rises when project is extended.
• Total cost = Direct + Indirect. The optimal duration balances these.
• Crash time is the minimum possible duration for an activity; crashing costs extra per week.
• The optimal project duration is found by comparing direct cost increases from crashing against indirect cost savings.

Cost-Time Trade-off in Project Networks

Project crashing is the process of reducing the total project duration by accelerating individual activities, at some cost. The goal is to find the optimal project duration that minimises the sum of direct costs (crashing) and indirect costs (overheads).

1. Two Cost Structures

• Direct cost – the cost of crashing or accelerating a single activity (e.g., overtime, extra labour, equipment). This cost is incurred per week of reduction.
• Indirect cost – overheads of the project (rent, supervision, utilities) that accrue per unit of time – here, ₹1000 per week.

The trade-off: crashing reduces indirect cost (shorter project → fewer overhead weeks) but increases direct cost (pay to speed up activities). The optimal duration is where total cost (direct + indirect) is minimised.

2. Crashing Rules

Crashing is performed one week at a time on the critical path (the longest path in the network, which determines project duration). Only crashable activities may be reduced – some cannot be crashed (e.g., A and M in this example) or cannot be crashed below a minimum technical time (e.g., L minimum = 2 weeks).

Decision rule at each step: Crash the crashable activity on the critical path with the lowest crashing cost per week.

Exam tip: Always re-identify the critical path after every crash – the set of critical paths may change, creating multiple bottlenecks.

---

Worked Example: From 25 Weeks to Optimal 23 Weeks

Initial project data:

• Activity durations, predecessors, and the project network are already defined.
• Critical path: A→B→C→L→M, duration = 25 weeks.
• Only activities B, C, L are crashable on that path (A and M not crashable).

• Indirect cost = ₹1000 per week.

Step 1 – Crash L (₹300/week) → duration 25 → 24 weeks

• Benefit: project shorter by 1 week → save ₹1000 indirect cost.
• Net gain = ₹1000 – ₹300 = ₹700.
• Update network: L now 2 weeks. Recompute all paths.

New critical paths (both 24 weeks):

1. A–B–C–L–M
2. J–I–M ($13 + 6 + 5 = 24$).

Crashable activities now: On path 1: B (700), C (500). On path 2: J (400), I (700). L already at minimum.

Step 2 – Crash C (₹500) and J (₹400) simultaneously → duration 24 → 23 weeks

• Why both? To reduce project duration, both critical paths must be shortened by 1 week each.
• Choose lowest-cost on each: C (500) on path 1, J (400) on path 2.
• Total crashing cost = 500 + 400 = ₹900.
• Benefit: save ₹1000 indirect cost (1 week).
• Net gain = ₹1000 – ₹900 = ₹100.
• Update: C now 6 weeks, J now 12 weeks.

New critical paths (all 23 weeks):

1. A–B–C–L–M
2. G–H–I–M (GHIM) – now appears as critical
3. J–I–M (JIM)

(Actually JIM was 23, GHIM also 23, ABCLM 23.)

Step 3 – Consider further crash to 22 weeks

Now three critical paths. To reduce project duration, each path must be shortened by 1 week.

Crashable activities:

Strategy options:

• Crash a common activity on two paths (e.g., crash I, which lies on both GHIM and JIM) – cost ₹700. Then crash C on ABCLM (₹500). Total = ₹1200.
• Crash non-common activities – on GHIM crash H (₹200), on JIM crash J (₹400), on ABCLM crash C (₹500). Total = ₹1100.

The cheaper option is the second: crash H, J, and C at total direct cost ₹1100.

• Benefit: save ₹1000 indirect.
• Net loss = ₹1000 – ₹1100 = –₹100.

Since net loss arises, do not crash further. The optimal project duration remains 23 weeks.

---

Summary of the Crashing Process

Exam tip: When multiple critical paths exist, you must reduce all of them by the same amount to shorten the project. Crashing only one path leaves the project duration unchanged.

---

Key Takeaways

• Direct cost = cost to crash an activity (per week); indirect cost = overhead per week (here ₹1000).
• Always crash the cheapest activity on the critical path first, but only if the net benefit (indirect saving minus crash cost) is positive.
• After each crash, recompute critical paths – they can multiply.
• When multiple critical paths appear, you need to crash one activity on each path (or a common activity) to reduce project duration.
• The optimal project duration is the point where an additional crash yields a net loss (total cost increases). In this example, it is 23 weeks.
• Activities have minimum technical times – cannot be crashed beyond that limit.

Gantt Charts

Gantt Charts are a visual tool that display project activities along a time dimension. They complement the project network diagram (critical path method) by showing when each activity starts and finishes, and which activities run in parallel. The X-axis represents time; the Y-axis lists the project activities.

Reading the Gantt Chart

• Each activity is drawn as a horizontal bar spanning its start to finish time.
• The total length of the bar equals the activity’s duration.
• Activities on the critical path appear as a continuous chain with no gaps between them. Their combined duration equals the project duration.
• Non‑critical activities may have slack — gaps before or after their bar where they can shift without delaying the project.

Visualizing the Critical Path

From the earlier analysis (forward/backward pass, slack calculation), the critical path was A → B → C → L → M, with durations 6, 4, 7, 3, 5 weeks respectively.

• Project duration = $6 + 4 + 7 + 3 + 5 = 25$ weeks.
• On the Gantt chart, these five bars appear sequentially (no overlap, no gaps). The total time from start of A to finish of M is 25 weeks.

Exam tip: The critical path is the longest chain of activities with zero slack. Any delay on a critical path activity directly delays the entire project.

Non‑Critical Paths and Slack

Take path A → D → E → F (non‑critical). On the Gantt chart, these bars may have gaps or start later than their predecessor.

• If activity E is delayed by 1 week, the bar shifts right, but because E has slack, the overall project duration remains 25 weeks.
• Discipline: Non‑critical activities can absorb small delays as long as the delay does not exceed their slack. Only delays on the critical path lengthen the project.

Resource Mapping and Parallelism

The Gantt chart reveals which activities are scheduled in parallel — a critical insight for resource allocation.

• At a given time, multiple bars may be running concurrently.
• For example, activities B and D may overlap in time. If both require the same specialised team, one team cannot execute both simultaneously. You need either multiple teams or must re‑schedule one activity to avoid overlap.

• The chart helps identify resource bottlenecks and decide whether to add parallel teams or sequence activities differently.

Key Takeaways

• Gantt chart = time‑based visual of project activities (X‑axis = time, Y‑axis = activities).
• The critical path appears as a continuous, gap‑free chain; its total duration = project duration.
• Slack on non‑critical paths allows small delays without affecting the project finish.
• Delaying a critical path activity always delays the project; delaying a non‑critical activity may not.
• Parallel activities in the Gantt chart imply parallel resource needs — one team cannot cover overlapping activities if the same skill is required.
• Gantt charts complement network diagrams by adding the time dimension and resource visibility.