Which principle is NOT part of the Agile values and principles?

The principle that is recognized as not part of the Agile values and principles is characterized by its high tolerance for project scope changes. In Agile methodologies, while the ability to adapt to changes in project scope is acknowledged—due to the dynamic nature of software development—the emphasis is on managing those changes effectively rather than having an inherently high tolerance.

Agile methodologies encourage collaboration, feedback, and iterative development, which naturally leads to changes based on stakeholder input. However, the goal is to prioritize delivering value and maintaining a sustainable pace, rather than accepting changes without consideration. In fact, Agile practices emphasize maintaining a clear product vision and managing scope through proper backlog management and iterative planning.

Conversely, the other principles highlight essential aspects of Agile. Close cooperation between business stakeholders and developers fosters better communication and understanding of requirements. Prioritizing working software as the primary measure of progress allows teams to focus on delivering functional and valuable products rather than getting bogged down by extensive documentation or bureaucratic processes. Lastly, promoting simplicity ensures that the team focuses on delivering the most valuable features with the least complexity, which often leads to better maintainability and faster delivery.