CAPM Practice: Determine how project methodologies influence business analysis processes

Real projects often have both stable and uncertain elements. A hybrid BA approach documents stable regulatory requirements predictively while using iterative prototyping for innovative UX features — matching the technique to the nature of the requirement rather than applying one approach to everything.

**Why not A:** Using both techniques on the same project is a deliberate, informed decision — not indecision about methodology. Hybrid approaches reflect sophisticated thinking about matching techniques to the nature of different requirement types within the same project.

**Why not B:** Combining predictive and adaptive techniques does not inherently reduce quality. When applied thoughtfully — using the right technique for the right type of requirement — a hybrid approach can actually improve requirements quality by matching the approach to the nature of each requirement.

**Why not C:** PMI standards explicitly recognize hybrid approaches that combine predictive and adaptive techniques. There is no prohibition against using mixed methods; in fact, PMI acknowledges that many real-world projects benefit from combining approaches.