The correct answer is even late in development, the team welcomes change requirements. This is the principle best exhibited in this scenario – the expectation (and accommodation) that requirements can change at any time. The other responses
are incorrect because even though changing requirements may satisfy the customer, it’s not as important or good of a choice as the correct answer; the behavior in this scenario has nothing to do with the frequency of software delivery,
or the reflection on how the team can be more effective.