CAPM Practice: Determine how project methodologies influence business analysis processes

In predictive projects, the BA front-loads work — comprehensive requirements documents (BRD, functional specs) are produced before design begins, because changes after design are expensive and because the entire project plan depends on stable requirements.

**Why not A:** Daily standups and product backlog management are Scrum/agile ceremonies. In a predictive (waterfall) project, there are no sprints or backlogs. The BA's focus during initiation/planning is on comprehensive upfront requirements documentation.

**Why not B:** Sprint retrospectives are an agile practice that does not exist in predictive project methodologies. Waterfall projects follow sequential phases, and the planning phase centers on thorough requirements elicitation and documentation.

**Why not D:** User stories and iterations are agile artifacts and practices. In a predictive project, the BA produces detailed requirements specifications and use cases during planning, not user stories organized into iterations.