Linked from

The 15 pages that link to Agile software development, each with the reason it gives.

• Systems engineeringCompared with: Its adaptation to changing needs contrasts with plans and assurance practices used in some large engineered systems.

• Project managementCompared with: It contrasts with predictive planning by revising plans through short delivery cycles.

• Software engineeringRelated: Agile methods are one family of ways to organize engineering work.

• Technical debtRelated: The debt metaphor became widely useful in discussions of rapid, iterative development.

• Requirements engineeringCompared with: Its evolving backlogs and short feedback cycles contrast with treating requirements as a fixed, early specification.

• Product managementRelated: Many product teams use its cycles to refine priorities as they learn.

• Software developmentCompared with: Agile prioritizes short feedback cycles over comprehensive upfront plans.

• Video game developmentRelated: Teams use iterative delivery to revise features as playtests reveal problems.

• Engineering design processCompared with: It is a domain-specific alternative to sequential plans for handling changing requirements.

• Requirements analysisCompared with: Agile teams refine requirements incrementally instead of relying solely on fixed upfront specifications.

• Ward CunninghamNarrower topic: Cunningham’s work on extreme programming placed him among the contributors to agile practice.

• New product developmentRelated: Its frequent releases and feedback loops suit products whose requirements evolve during development.

• Software prototypingRelated: Agile teams often use prototypes to clarify uncertain requirements early.

• History of softwareRelated: Agile methods responded to the limits of rigid, document-heavy development plans.

• TaskRelated: Agile teams break planned outcomes into work items completed across iterations.