CAPM Practice: Determine how project methodologies influence business analysis processes

DevOps continuous delivery means features reach users quickly, enabling rapid learning. BAs adapt by defining smaller, more focused requirements chunks, monitoring production data after deployment, and incorporating fast feedback loops into requirements evolution.

**Why not A:** DevOps accelerates deployment but does not eliminate the need for requirements analysis. Features still need to be understood, prioritized, and specified before they can be built and deployed. Continuous delivery changes the cadence and granularity of requirements work, not whether it is needed at all.

**Why not B:** DevOps practices actually reduce the need for heavy upfront documentation because rapid feedback from real deployments replaces speculative detail. More formal documentation would slow the cycle and contradict the DevOps principle of minimizing handoff overhead. BAs in DevOps environments work with lightweight, just-in-time specifications.

**Why not D:** BA work is ongoing throughout a DevOps lifecycle — each deployment cycle brings new user data and feedback that informs the next set of requirements. Treating BA involvement as a one-time setup activity would deprive the team of the continuous requirements refinement that makes DevOps effective at delivering evolving business value.