volume_mute

Agile Requirements Change vs. Traditional Change Management

publish date: 2026/06/06 22:28:8.952635 UTC

volume_mute

How do agile development processes handle requirements changes differently from traditional formal change management?

The user prioritizes the change and, if high priority, it replaces lower-priority features planned for the next iteration — no formal change management process is used

Changes are batched and reviewed only once a year at a formal change board

All requirements changes are automatically rejected to maintain system stability

The user submits a formal change request that goes through all three stages of the change management process

Correct Answer

The user prioritizes the change and, if high priority, it replaces lower-priority features planned for the next iteration — no formal change management process is used

Explanation

In agile processes, when a user proposes a requirements change, it does not go through a formal change management process. Instead, the user prioritizes the change. If it is high priority, it replaces system features that were planned for the next iteration and have not yet been implemented — a much lighter-weight approach than the formal three-stage process.

Reference

Software Engineering, Ian Sommerville, 9th edition

Quizzes you can take where this question appears

Requirements Management Planning