In which way does agile project management differ from waterfall?

Agile project management distinguishes itself from the waterfall model primarily through its adaptability to change. Agile methodologies are designed to respond to changes in requirements and user feedback throughout the project lifecycle. This adaptability is a core principle of Agile, enabling teams to iterate on their work based on real-time information and stakeholder input. As iterations are completed, the team can revisit and modify the direction of the project according to new insights, which is essential in dynamic environments where requirements often evolve.

In contrast, the waterfall model is a linear and sequential approach where changes can be challenging to implement once a phase is completed. This rigidity makes waterfall less suited for projects where requirements may shift during development.

The other options highlight characteristics that are not accurate in terms of how agile and waterfall methodologies are defined and implemented. Waterfall typically involves a greater emphasis on documentation, agile values collaboration and stakeholder involvement, and waterfall is not particularly designed for rapid prototyping. Thus, option A stands out as the most accurate distinction between the two methodologies.