Scopedriven

Scopedriven is a term used to describe an approach to software development and project management in which the defined scope serves as the primary constraint and driver of decision-making. In this model, planning, prioritization, and resource allocation are anchored in the agreed-upon objectives and boundaries of the work, and changes to scope are treated with formal consideration.

The term is a contemporary neologism rather than a formally standardized methodology. It appears in practitioner discussions to distinguish scope-centric planning from time-centric or value-centric approaches. It is often invoked in teams that seek to prevent scope creep by making scope decisions explicit and accountable.

Key characteristics include a clearly defined scope at the start of a cycle, formal change-control processes, and prioritization aligned with the scope. There is frequent re-evaluation of scope against outcomes, with an emphasis on delivering predefined capabilities rather than adding features mid-cycle. This can help align teams with stakeholders but may reduce flexibility if market conditions shift.

Critique and limitations center on the risk that overemphasis on scope can hinder responsiveness and lead to delays or misalignment with user needs if the scope is poorly defined. Effective scopedriven practice relies on strong governance, clear documentation, and ongoing stakeholder engagement.

See also: scope, scope creep, scope management, agile, product management, feature-driven development.