CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Iterative requirements development mirrors adaptive project philosophy — starting with high-level understanding and adding detail progressively. Each delivery cycle provides feedback that refines requirements, acknowledging that perfect upfront specification is impossible and that learning through doing produces better requirements.

**Why not A:** Repeating the same information multiple times for emphasis describes redundancy in documentation, not iterative requirements development. Iterative development involves progressively building deeper understanding through multiple cycles of refinement, not restating the same content.

**Why not B:** Iterating through the alphabet covering requirement types in order is a fabricated process that does not reflect any recognized BA methodology. Iterative requirements development is about cyclical refinement of understanding, not alphabetical sequencing of requirement categories.

**Why not C:** Looping back to the beginning without progressing describes a stuck or unproductive process. Iterative requirements development involves progressive refinement where each cycle builds on the previous one, adding detail and incorporating new learning. Each iteration should advance the team's understanding forward.