liveBook · Manning

Scope drift

As explained in Everyday Data Visualization

Scope creep is the uncontrolled expansion of a project's requirements beyond its original plan, potentially delaying completion or changing the intended outcome.

Scope drift is the uncontrolled growth of a project’s requirements beyond its original plan. Small additions may be reasonable, but expansion becomes dangerous when it delays completion by weeks or months or changes the intended outcome. section 9.3

Too many cooks

A project has several stakeholders with competing preferences: one approves the design, another demands a different font, and a delayed decision-maker later rejects a specialized filter menu. The team repeatedly revises completed work, consuming time and money while the finish line moves away. section 9.3.2

Scope drift commonly appears when:

  • Requirements keep arriving instead of staying aligned with the original plan. section 9.3
  • Too many stakeholders give competing instructions or cannot provide timely sign-off. section 9.3.2
  • No one clearly calls the shots, leaving iterative design and development without timely guidance. section 9.3.2

How Everyday Data Visualization covers it

How deep it goes
Defines scope drift through its causes and consequences, but does not provide detailed mitigation procedures.
Examples
Uses competing font feedback, delayed approval, and rejection of a specialized filter menu to illustrate rework.
What you can do after
Diagnose scope drift by identifying continual additions, conflicting stakeholders, delayed feedback, and absent decision ownership.
How it connects
Connects scope drift to project requirements, stakeholders, sign-off, and iterative design and development.

Also explained in

Compare how 2 books explain scope drift →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Everyday Data Visualization. The section links point to the parts of the book it draws on.