Which strategy in software development helps to anticipate possible changes before they require rework?

The correct answer is change anticipation. This strategy focuses on predicting and preparing for changes throughout the software development lifecycle. By identifying potential changes early, teams can develop systems that are flexible and modifiable, ultimately reducing the need for significant rework later on.

Change anticipation involves analyzing requirements and understanding user needs, which can shift over time. This proactive approach allows developers to build adaptable architectures and design solutions that accommodate future modifications, making the overall development process more efficient and responsive.

While incremental delivery does help in managing changes through shorter cycles and regular feedback, it does not specifically focus on anticipating changes before they occur. Prototyping can facilitate understanding of user requirements and uncover possible changes, but it is more about exploring ideas than predicting future needs. Risk management involves assessing and mitigating potential challenges, but it does not directly address the anticipation of changes within requirements or user expectations.