CAPM Practice: Determine how project methodologies influence business analysis processes

Sprint 0 is a setup period before delivery begins — establishing product vision, creating initial backlog with epics and themes, conducting stakeholder identification, setting up tooling, and doing just enough architecture to start. BAs lead backlog creation and stakeholder engagement activities in sprint 0.

**Why not A:** Iteration 0 is specifically a preparatory sprint — it does not deliver working features to stakeholders. Its purpose is to establish the foundation for the project, including vision, initial backlog creation, environment setup, and architectural decisions. Feature delivery begins in subsequent iterations.

**Why not C:** A retrospective or lessons-learned review of a previous project is a distinct activity, not the purpose of sprint 0. While lessons learned may inform sprint 0 planning, the sprint itself is focused on setting up the current project — not evaluating a past one.

**Why not D:** Sprint 0 is not about producing comprehensive documentation. In adaptive methodologies, the goal is to create just enough artifacts to begin delivery — such as a product vision, initial backlog, and high-level architecture. Writing exhaustive requirements documentation contradicts the agile principle of valuing working software over comprehensive documentation.