At this point the Manifesto put its finger on the sore spot

[sujonkumar6300]

The client-supplier relationship in software development cannot have traditional bases (one demands and pays the other to comply). This relationship must be one of collaboration with mutual benefits.

Responding to change about following a plan
Change requests from the client, which may cause the plan to be modified, have already occurred in traditional processes. The insistence of the authors of the Manifesto on this point may be a consequence of the fact that typical contracts required this rigidity of following a previously agreed plan without offering much room for changes.

But I also suspect that it is a call to the developers themselves, who get Algeria Mobile Database desperate when a client changes their “game” and they already thought that the system was almost ready. The authors of the manifesto want to tell them that their anger is pointless. After all, the system must serve the client and the users, and therefore they have to accept the changes even if it hurts them.

The fine print...
At the end of the part of the Manifesto dedicated to values, we find something that is like the fine print of contracts:

“That is, although we value the elements on the right, we value those on the left more.”