Project execution, dependencies and governance

The anatomy of delivery

Dependency visibility and explicit change control matter more than the appearance of a complete schedule.

148 pages · Edition 2026-10-10

Delivery / dependenciesIllustrative composition

An illustrative dependency construction. It shows why relationships matter, without portraying a real programme or schedule.

The questions

Which accepted outcomes and dependency evidence make the delivery baseline usable?
When does a duration or interface change move the critical path or invalidate the apparent margin?
What distinguishes accepted progress from activity, expenditure and an optimistic forecast?
Which authority and evidence should permit baseline change, recovery action and service handover?

The argument

A schedule is useful when it represents commitments, dependencies and acceptance conditions that govern delivery. This playbook distinguishes a complete-looking chart from a controlled model of work, then connects network reasoning to estimation, interfaces, baselines, change decisions, accepted progress, recovery and commissioning. Frozen fictional studies reproduce the Delivery atlas calculation and show how sequencing, duration changes, omitted release work and parallel paths alter the result. The selected-path normal deadline approximation remains explicitly separate from whole-project completion confidence. Practical records preserve the evidence, authority and conditions needed to act on a forecast. Public institutional guidance supplies scoped methods rather than empirical duration rates for an unnamed project. The recommendation is conditional: use dependency visibility and change control where they improve the decision, while adapting the planning method when discovery, scarce resources or noncompensable constraints make a fixed precedence model insufficient.

Scope and boundaries

Evidence cut-off: 2026-10-10. Cross-sector analytical methods; every source retains its original jurisdiction and scope

Included

Project execution, dependencies and governance
Transparent illustrative examples and reproducible methods
Counterarguments, decision conditions and practical implementation records

Limits

Illustrative inputs explain mechanisms and are not actual project data or empirical estimates.
A deterministic model cannot establish implementation feasibility, legal effect, lender acceptance or future outcomes.
Cited public guidance is used only within explicitly stated source scope; institutional frameworks require local adaptation.

1
A schedule is a model of commitments
Define outcomes, work boundaries, dependencies and decision authority
2
The work breakdown sets the control perimeter
Distinguish deliverables, tasks, interfaces and acceptance evidence
3
Dependencies carry the real sequencing logic
Examine physical, information, resource and contractual predecessors
4
Durations need an estimation basis
Separate estimates, calendars, elapsed time, effort and external lead time
5
The critical path is conditional on the network
Derive forward and backward passes and distinguish float from usable flexibility
6
Resource constraints can invalidate an elegant network
Compare precedence feasibility with scarce teams, equipment and access windows
7
Interfaces deserve explicit acceptance tests
Define handoff objects, readiness, evidence and rejection rights
8
Baseline approval must preserve assumptions
Freeze scope, dates, calendars, resources and evidence with decision conditions
9
Change control is a valuation process
Assess scope, dependency, cost, risk and benefit effects before accepting a change
10
Progress must mean accepted work
Distinguish started, produced, tested, delivered and accepted states
11
Earned value can mislead on weak baselines
Explain planned, earned and actual cost while questioning aggregation and quality
12
Schedule variance has a cash consequence
Trace indirect costs, delayed receipts and resource extension without asserting a universal delay multiplier
13
Forecasting needs explicit uncertainty
Separate deterministic completion dates, scenario ranges and probabilistic estimates
14
Recovery plans can consume the remaining margin
Analyse crashing, resequencing, concurrency and rework introduced by acceleration
15
Risk responses must enter the network
Link prevention, contingency and triggers to tasks and resources
16
Governance sets decision latency
Locate approvals, escalation thresholds and unresolved ownership
17
Suppliers are part of the delivery system
Track design freeze, purchase release, manufacture, logistics and inspection
18
Commissioning integrates what construction separated
Define subsystem readiness, integrated tests and sustained service acceptance
19
Lessons require original forecasts and actual outcomes
Preserve baseline, changes and evidence to learn from estimation error
20
When a complete schedule is not useful
Consider discovery work, uncertainty, emergent tasks and adaptive planning
21
Appendix: network calculation specification
Document canonical dates, float, cycles and validation rules
22
Appendix: illustrative delivery studies
Publish serial, parallel, changed-duration, interface-delay and invalid-network fixtures
23
Appendix: operational control worksheets
Complete dependency, acceptance, change, risk and escalation examples
24
Appendix: source scope and release-mechanism fit
Retain institutional source boundaries and distinguish continuous review duration from calendars, conditional resubmission, resources and authority.