CAPM Practice: Determine how project methodologies influence business analysis processes

In predictive projects, prototypes help validate requirements before locking them into documentation. In adaptive projects, working software increments deliver more than prototypes — they're real, tested functionality that stakeholders can evaluate in each sprint review, making elaborate prototyping less necessary.

**Why not B:** Prototyping is used in both predictive and adaptive approaches, making this statement factually incorrect. In predictive projects, prototypes help validate requirements before committing to full development. In adaptive projects, the iterative delivery of working software effectively replaces traditional prototyping with real, functional increments.

**Why not C:** While prototyping is commonly associated with predictive projects for upfront validation, it is incorrect to say it is only used there. Adaptive projects leverage the concept of prototyping through their iterative nature, where each increment serves as a validated prototype that evolves into the final product.

**Why not D:** Adaptive projects actually use less formal prototyping than predictive projects, not more. In adaptive environments, the rapid delivery of working software in short iterations naturally reduces the need for separate formal prototypes, since stakeholders can evaluate and provide feedback on real functionality rather than mock-ups.