CAPM Practice: Determine how project methodologies influence business analysis processes

Predictive projects need comprehensive documentation because requirements drive all downstream phases and changes are expensive. Adaptive projects rely on 'just enough' documentation — the conversation, collaboration, and working software complement lightweight written artifacts.

**Why not A:** Adaptive projects do not require more documentation than predictive projects. The opposite is generally true. Adaptive projects favor lightweight artifacts supplemented by conversation and working software, while predictive projects rely more heavily on comprehensive upfront documentation to drive downstream phases.

**Why not B:** Documentation requirements differ significantly between methodologies. Predictive projects need detailed upfront specifications because changes are expensive later, while adaptive projects use lighter documentation because requirements evolve through iterative delivery and continuous feedback.

**Why not C:** Both predictive and adaptive methodologies require some form of requirements documentation. Predictive projects use comprehensive documents like BRDs and functional specifications, while adaptive projects use user stories, acceptance criteria, and other lightweight formats. Neither operates without any documentation.