The Agile principle "welcome changing requirements, even late in development" relates to which agile manifesto?

The value of working software over comprehensive documentation addresses the form of deliverables and how progress is measured, not the team's posture toward changing requirements.

Individuals and interactions over processes and tools addresses team collaboration and human communication preferences, not adaptability to requirement changes.

Customer collaboration over contract negotiation emphasizes the nature of the customer relationship and partnership, not specifically the acceptance of late-stage requirement changes.

The fourth Agile Manifesto value explicitly states preference for 'responding to change over following a plan.' The principle of welcoming changing requirements, even late in development, is a direct practical expression of this value, emphasizing that the ability to adapt delivers greater customer value than rigid adherence to a predetermined plan.