liveBook · Manning

Scope drift

As explained in Lead Developer Career Guide

Scope creep is the uncontrolled expansion of a project's requirements or deliverables after work has begun.

Scope drift is the uncontrolled expansion of project requirements or deliverables after work has begun. It often begins when teams design systems without solid business requirements or shared agreement. section 1.2.3

Reduce the risk before new work starts:

  • Gather business requirements before designing the system. section 1.2.3
  • Confirm that the development team agrees on what is being built. section 1.2.3
  • Ask why each product or feature is being built, not only how. section 1.2.3

A preventable expansion

A team begins designing a client’s system before clarifying business requirements. As new interpretations and features emerge, the original deliverables can expand beyond control. section 1.2.3

How Lead Developer Career Guide covers it

How deep it goes
Defines the risk and offers brief prevention guidance through requirements, agreement, and feature rationale.
Examples
Uses premature system design without agreed requirements as a workplace example of scope expansion.
What it assumes
Assumes client and stakeholder interaction; teaches the importance of requirements and agreement before system design.
What you can do after
Evaluate requirements and feature purposes before design to reduce uncontrolled expansion.
How it connects
Connects scope drift with business requirements, stakeholder communication, team agreement, and feature rationale.

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 Lead Developer Career Guide. The section links point to the parts of the book it draws on.