The building blocks of project controls — Scope, Time, and Cost

It starts with psychology, not software

Before the math, there's the human layer. A realistic, logical plan creates something you can feel on site: confidence. The team has energy, morale holds. Hand that same team a schedule that is mathematically impossible — a deadline that no honest sequence of work can hit — and you get the opposite: burnout, then disengagement, then people quietly checking out.

This is why setting clear, realistic targets isn't a "nice to have." It's the prerequisite for project control to even function. Following a plan that was broken from day one doesn't control anything — it just documents the breakage as it happens.

The Triple Constraint — and the golden rule

Picture a balance. On one side sit Scope and Quality. On the other, Time and Budget. And the whole thing rests on Resources. Move any weight and the balance tips.

The rule that follows is simple and non-negotiable: if time or budget is constrained, scope or quality must come down proportionally. You cannot squeeze the deadline, freeze the budget, hold the scope, and keep the quality — all at once. Something gives. The only choice you have is whether you decide what gives, or whether the project decides for you.

This is the exam's golden rule and the site's golden rule at the same time: an imbalanced plan can't be controlled. Say no to the impossible plan before it starts, not after it fails.

The WBS is the central nervous system

If Scope-Time-Cost is the body, the Work Breakdown Structure is its nervous system. Get the WBS wrong and every signal that travels through the project — every progress update, every cost report, every forecast — is wrong at the source.

There's one hard rule: a WBS must be deliverable-based, never phase-based. This sounds academic until you've lived the consequences.

Right: 1.0 East Wing · 2.0 West Wing · 3.0 Security Room. Physical, concrete, completable pieces.

Wrong: 1.0 Design · 2.0 Development · 3.0 Testing. Slicing by time period is invalid — and here's why it matters.

Imagine the budget gets cut in half mid-project. With a deliverable-based WBS, you finish the East Wing completely and hand it over — a functioning building. With a phase-based WBS, the cut leaves every phase half-done: you have design fragments, half-built systems, nothing tested. Zero functional output. One structural decision, made before construction, determines whether a budget cut leaves you with something or nothing.

The four building blocks of the model

Once scope is structured correctly, the schedule model itself is built from exactly four components — like a circuit, they only work in synergy:

Activity. A measurable unit of physical or intellectual work with a duration greater than zero.

Milestone. A critical checkpoint with a duration of exactly zero — a "foundation-laying ceremony," a permit approval, a phase gate.

Resource. The people, equipment, material, or capital required to do the work.

Logic. The structural relationship that links activities and milestones to each other.

Alone, these are inert. Activities fed by resources and bound by logic become something else entirely: a dynamic forecasting engine. Change one duration and the whole model recalculates the impact.

Why these rules exist — they're not arbitrary

It's worth knowing that these controls weren't invented by academics. They came from law and money. In 1967 the US Department of Defense set the first rules integrating cost and schedule (C/SCSC). In 1993 the Government Performance and Results Act forced results-based accountability across federal agencies. Today, Earned Value Management is the standard in both public and private sectors — and the logic behind all of it is blunt: if the controls aren't reliable, the funding gets cut.

That's the real stakes behind "get the fundamentals right." It's not about passing an exam. It's about whether the money keeps flowing.

What's coming next

We now know a schedule is a model, and that model rests on Scope-Time-Cost balance and a deliverable-based WBS. In Week 3 we go after one of the most common — and most costly — confusions in the whole field: the difference between your Schedule Model and the Gantt chart hanging on the wall. They are not the same thing, and mistaking one for the other quietly wrecks projects. Follow along on LinkedIn or YouTube.