CAPM Practice: Determine how project methodologies influence business analysis processes

When code integrates and builds continuously, BAs can validate requirements against working software much more frequently than in traditional projects. This early and continuous validation catches requirements misunderstandings while they're cheap to fix.

**Why not A:** Continuous integration directly affects how quickly changes are built, tested, and available for review. Claiming it has no effect on BA validation ignores the reality that CI pipelines produce testable builds faster, enabling BAs to validate requirements against working software more frequently and with shorter feedback loops.

**Why not C:** CI automates build and integration testing, but it does not replace the BA's validation activities. Automated tests verify that code functions correctly at a technical level, while BA validation confirms that the delivered functionality meets business requirements and stakeholder expectations. These are complementary, not substitutable, activities.

**Why not D:** Requiring the BA to review every individual code commit is impractical and misunderstands the BA's role. BAs validate that features meet business requirements, typically at the story or feature level. Code-level review is a development team responsibility. CI enables BAs to validate more efficiently, not to become code reviewers.