CAPM Practice: Determine how project methodologies influence business analysis processes

The most fundamental mindset shift is from 'define everything before building anything' to 'build to learn.' This requires accepting uncertainty, trusting that requirements will become clearer through delivery, and being comfortable with emergent rather than comprehensive upfront specification.

**Why not A:** Transitioning to agile does not mean the BA stops working with business stakeholders. In agile, BAs continue engaging with business stakeholders — often more frequently through ongoing collaboration, sprint reviews, and continuous feedback loops. The shift is about collaboration style, not abandoning stakeholder relationships.

**Why not B:** Agile does not advocate eliminating all documentation. It values working software over comprehensive documentation, but appropriate documentation is still produced. The real shift is about creating just-enough, just-in-time documentation rather than swinging to the extreme of no documentation at all.

**Why not C:** This choice describes moving in the wrong direction — from agile practices back to waterfall practices. Writing user stories is an agile technique, while requirements specifications are a traditional artifact. The mindset shift when adopting agile should move toward iterative, lightweight approaches, not back toward heavyweight documentation.