Working Together

How Scope & Estimates Work

A useful estimate starts with a useful definition of the work. The goal is to make deliverables, assumptions, dependencies and review points visible before they become surprises.

Outcome

Start with the result

Define what should exist or be improved at the end of the engagement.

Deliverables

Name the actual outputs

List the pages, reports, systems, research products, workflows or other assets included in the scope.

Assumptions

Make hidden dependencies visible

Identify what the estimate assumes about access, source material, approvals, existing technology and decision-making.

Review

Define feedback points

Clarify how many review cycles or approval stages are reasonably expected for the work.

Change

Separate new scope from revision

Distinguish between refining an agreed deliverable and adding a new deliverable or objective.

Timing

Connect schedule to dependencies

A realistic timeline accounts for inputs, approvals and sequencing rather than treating every task as independent.

Different projects need different estimate structures.

A narrowly defined assignment may be simple to scope up front. A research-heavy or exploratory project may be better divided into phases so later work is estimated after the first phase reduces uncertainty. The useful structure is the one that makes risk and expectations visible.

The estimate should explain the work.

A number without a scope is not very informative. DDPW’s preference is to connect pricing and timing to the specific deliverables, assumptions and project structure rather than force every engagement into the same package.

Start a Project