Project Scoping

Overview

A project that does not have a clear scope is a project that will run over budget. Scoping is the discipline of defining what is in, what is out, and what it will cost — before you commit to building anything.

Scoping is not paperwork. It is the single most cost-effective intervention in a project's lifecycle. An hour spent scoping properly can save a month of rework downstream.

What We Do

Our scoping work typically covers:

• Requirements decomposition — breaking high-level intent into discrete, testable requirements.
• Scope statements with explicit exclusions — saying clearly what is not in scope is as important as saying what is.
• Work breakdown structures — decomposing the work into deliverables that can be estimated, assigned and tracked.
• Estimation — both top-down (for sanity checks) and bottom-up (for commitments), with the difference between them flagged for discussion.
• Assumptions and dependencies registers — recording what has to be true for the estimates to hold, and what we are waiting on from others.

Why Scoping Matters

Most project failures are scope failures. Either scope was unclear from the start, or it was clear and then it crept — one small addition at a time — until the original plan no longer reflected reality.

We make the boundary visible so it can be defended. Once everyone agrees what is in scope, any change request can be assessed on its merits: is it worth the cost and the time, and where does the budget come from? Without a defined scope, there is nothing to assess against, and "small" additions accumulate without anyone noticing.

Our Approach

We are direct about uncertainty. Where we cannot estimate confidently — because the problem is genuinely unfamiliar, or because key inputs are missing — we say so. We propose a short discovery phase to reduce the uncertainty, rather than dressing up a guess as a commitment.

This is unfashionable in an industry that prefers confident numbers to honest ones, but it produces projects that finish on plan rather than projects that overshoot quietly.