Planning, Scheduling & Control

Means: Planning, scheduling and CONTROLLING a project's work, time, cost and people from concept and feasibility, through design and construction, to commissioning and handover.

Honestly · It is not paperwork or a one-time plan — it is continuous control that steers a project to delivery on time, on budget and to quality. In interiors, the designer is often the coordinator of contractor, vendors and consultants.

Means: The 'iron triangle' — a project is bounded by SCOPE, TIME and COST, with QUALITY at the centre; the three are linked, so changing one affects the others.

Honestly · You cannot fix all three independently: squeeze one corner and another gives. 'Good, fast and cheap — pick two' is closer to the truth than any promise of all three at once. Naming the trade-off honestly is half the job.

Means: The belief that a detailed enough plan or schedule will make the project succeed on its own.

Honestly · A MYTH. A plan is a hypothesis about the future, and management is what you do when reality disagrees. The value is in replanning and CONTROL — monitoring, updating, deciding — not in a beautiful chart that is never revised.

Means: Breaking the whole project DOWN, top to bottom, into major deliverables and then small, manageable WORK PACKAGES that can be estimated, assigned and tracked.

Honestly · The foundation of a realistic plan: you cannot schedule or cost what you have not broken down. A good WBS is the difference between a real programme and a wish — but it must be revisited as the project changes.

Means: The phases a project passes through — concept, feasibility, design, construction/execution, and commissioning/handover — each with its own decisions and controls.

Honestly · Knowing the life cycle lets a manager plan the right work at the right stage. Decisions made early (concept, feasibility) shape cost and outcome far more than late ones — the cheapest time to change is at the start.

Means: A graphical model of a project as EVENTS (nodes) and ACTIVITIES (arrows) with their logical dependencies — showing what must precede what, and how the work connects.

Honestly · Where a bar chart shows only timing, a network shows the LOGIC — the dependencies that a schedule must respect. It is the basis of CPM and PERT, and of finding the critical path and float.

Means: An ACTIVITY is a task that consumes time and resources (drawn as an arrow); an EVENT is an instant — the start or finish of activities (drawn as a numbered node).

Honestly · The distinction matters: activities have duration and cost; events have neither, they are milestones in time. Confusing the two muddles a network — keeping them straight keeps the logic clear.

Means: A DUMMY (drawn as a dashed arrow, zero duration, zero resource) that exists only to show a DEPENDENCY or to keep the network's logic and numbering correct.

Honestly · NUANCED: it is not real work and takes no time, but it is not pointless — it enforces a genuine logical link. Used in activity-on-arrow networks; understanding it is part of reading a network correctly.

Means: A bar chart showing each activity as a bar along a timeline — its start, duration and finish — the most common and readable schedule format.

Honestly · NUANCED: superb for SEEING timing and progress, but a basic Gantt does not show the dependency LOGIC or the float — that is what a network (CPM/PERT) adds. Modern linked Gantts show links; a plain one does not. Use both.

Means: The longest chain of dependent activities through the network — the one with ZERO float — whose length is the SHORTEST possible time to finish the whole project.

Honestly · It is about TIME, not importance or cost. Delay any activity on it and the whole project slips; a non-critical activity can slip within its float without harm. Managing a project is largely managing its critical path.

Means: The belief that the 'critical' path is the most important, most expensive or most difficult part of the job.

Honestly · A MYTH. 'Critical' has a precise, dull meaning: the path with no float, that controls the finish date. A cheap, simple activity can be critical; a costly, complex one can have plenty of float. Critical is about the schedule, nothing else.

Means: The spare time a non-critical activity has — how long it can be delayed without delaying the project (total float) or the next activity (free float).

Honestly · NUANCED: float is real, useful scheduling flexibility, not wasted time — it lets a manager shift work and smooth resources. But consuming a path's float uses it up, and can turn that path critical. Spend it deliberately.

Means: Critical Path Method — a network technique using a SINGLE time estimate per activity to find the critical path and float. Developed in 1957 (DuPont, for plant work).

Honestly · Right for well-understood, repetitive work like construction, where durations are fairly known. It is deterministic: one estimate, one answer. Its honest limit is that it assumes you know the durations — real ones vary.

Means: Program Evaluation and Review Technique — uses THREE estimates (optimistic o, most likely m, pessimistic p) so expected time te = (o + 4m + p) / 6, with a variance. Developed in 1958 (US Navy, Polaris).

Honestly · Right for novel, uncertain work where durations are unknown. It is PROBABILISTIC: it gives an expected time and a probability of meeting a date, not a certainty. That honesty about uncertainty is its whole point.

Means: Reading a PERT expected completion time as a firm, guaranteed finish date.

Honestly · A MYTH. PERT is built on uncertainty — its answer is an EXPECTED time with a spread, and a probability of finishing by a given date. A single confident date from PERT is false precision; the range and the odds are the real output.

Means: Shortening the project by adding resources to CRITICAL activities to cut their duration — overtime, more labour, faster methods.

Honestly · NUANCED: it genuinely cuts time, but shortening an activity RAISES its direct cost. Crash the lowest cost-slope critical activities first, and only until the TOTAL cost (direct + indirect) is least. Faster is not automatically cheaper.

Means: The belief that finishing sooner always saves money, so more crashing is always better.

Honestly · A MYTH. As you crash, direct cost RISES while indirect (overhead) cost falls; total cost is a U-curve with a least-cost OPTIMUM duration. Crash to that point, not past it — beyond the optimum, going faster costs more, not less.

Means: The instinct that putting more people onto a project that is running late will bring it back on time.

Honestly · A MYTH (Brooks's Law): 'adding manpower to a late project makes it later.' New people need training, work must be re-divided, and communication paths multiply — the overhead often outweighs the extra hands. Plan realistically instead.

Means: Two ways to fix an uneven resource demand. SMOOTHING shifts non-critical activities within their FLOAT to flatten peaks, keeping the end date. LEVELLING respects a resource LIMIT and may extend the project.

Honestly · NUANCED and often confused: smoothing when the DEADLINE rules (uses float only, end date fixed); levelling when the RESOURCE is limited (may push the finish out). Choosing the right one depends on what is truly fixed.

Means: Computer tools (MS Project, Primavera and others) that build schedules, compute critical paths and float, allocate resources and track progress.

Honestly · NUANCED: powerful for calculation and communication, but garbage in, garbage out — it computes the schedule, it does not MANAGE the project. Judgement, realistic estimates, communication and control stay human. The software serves the manager.