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

Story splitting is one of the most critical agile BA skills. Patterns for splitting include: by workflow steps, by user role, by data variation, by operation (CRUD), by happy/unhappy path. Well-split stories enable incremental delivery and frequent feedback — the heart of adaptive development.

**Why not A:** Splitting estimation between complexity and risk components describes an estimation technique, not story splitting. Story splitting is specifically about decomposing large user stories into smaller, deliverable pieces of functionality, not about how effort or risk is estimated for those stories.

**Why not C:** Dividing story documents between team members for review describes a document review workflow, not story splitting. Story splitting is a requirements decomposition technique focused on creating smaller, independently valuable stories from larger ones, ensuring each piece can be completed and delivered within a single iteration.

**Why not D:** Creating two versions of a story for different audiences describes communication tailoring, not story splitting. Story splitting produces multiple distinct stories that each deliver a slice of value, not alternate presentations of the same story. The goal is to break down scope into iteration-sized increments, not to rewrite stories for different readers.