PMI Agile Certified Practitioner (ACP) Practice Exam

In Agile methodologies, the preferred approach to handling changes in requirements is to welcome changes even late in development. This principle is rooted in the Agile Manifesto, which emphasizes responsiveness to change over following a fixed plan.

The rationale behind this approach is that change is often a natural part of the development process, and Agile teams recognize that new insights can emerge as a project progresses. By embracing changes, teams can better align the final product with the evolving needs of stakeholders and customers. This adaptability not only enhances customer satisfaction but also contributes to delivering greater value throughout the project lifecycle.

Other options reflect more traditional project management views. Attempting to avoid changes at all costs undermines the flexibility that Agile aims to provide. Strictly controlling changes could lead to delayed deployments and loss of alignment with customer needs. Limiting change requests to only project managers can stifle collaboration and innovation, which are essential to Agile practices. Thus, welcoming changes is essential for Agile teams to thrive and succeed in delivering valuable products.