CAPM Practice: Determine how project methodologies influence business analysis processes

Traditional UAT (a distinct phase before go-live) is compressed in adaptive projects because continuous sprint reviews serve acceptance testing functions. Each sprint review is effectively a mini-UAT — stakeholders validate delivered functionality regularly rather than waiting until the end.

**Why not A:** Adaptive methodologies absolutely perform user acceptance testing. In agile approaches, UAT occurs iteratively—often at the end of each sprint or iteration—allowing stakeholders to validate working increments of the solution. Claiming that adaptive methods skip UAT entirely misrepresents how agile teams ensure the product meets user expectations through continuous feedback.

**Why not C:** UAT does not occur only at the very end in both methodologies. In predictive approaches, UAT typically happens near the end of the project lifecycle after development and system testing are complete. However, in adaptive approaches, UAT is integrated throughout the project via sprint reviews and iteration demos, providing earlier and more frequent validation opportunities.

**Why not D:** This option incorrectly claims that only predictive methodologies perform UAT while adaptive ones rely solely on automated testing. Automated testing in agile covers unit, integration, and regression testing but does not replace the need for human user acceptance testing. Both approaches require users to validate that the solution meets their actual business needs.