volume_mute

How Agile Minimises Delays from Changing Requirements

publish date: 2026/06/04 22:55:36.831426 UTC

volume_mute

One major cause of delay in conventional software development is how the process handles changing requirements. How do agile methods specifically address this to accelerate deployment?

Agile methods use automated code generation to instantly incorporate requirement changes without manual rework

Agile methods freeze requirements at the start to prevent changes from occurring

Agile methods interleave specification, development and validation — requirements and design evolve together so that when requirements change, only the current increment needs rework rather than the entire system specification and design

Agile methods outsource requirements changes to the customer, removing them from the critical path

Correct Answer

Explanation

In conventional plan-driven processes, requirements changes trigger expensive rework of specifications, designs, and implementations across the whole system. Agile methods avoid this by interleaving specification, development, and validation — requirements and design evolve together. When requirements change, only the current increment is affected, significantly reducing the analysis and documentation that must be redone, which directly accelerates delivery.

Reference

Software Engineering, Ian Sommerville, 9th edition

Quizzes you can take where this question appears

Exercises: Applied Agile Development