CAPM Practice: Determine how project methodologies influence business analysis processes

Backlog refinement is continuous — the team regularly reviews the backlog to add detail, split large items, estimate, and reprioritize. BAs contribute substantially: writing acceptance criteria, clarifying requirements, researching ambiguous areas, and helping the team understand upcoming work.

**Why not A:** Backlog refinement is not a one-time event at the start of the project. It is an ongoing, continuous activity that occurs throughout the life of the product. Treating it as a front-loaded activity contradicts the agile principle of progressive elaboration.

**Why not B:** Restricting refinement to the last day of each sprint is far too infrequent and narrow. The Scrum Guide recommends teams spend roughly 10% of their sprint capacity on refinement, spread across the sprint as needed — not compressed into a single day.

**Why not C:** While the product owner is accountable for the backlog, refinement is a collaborative team activity. BAs contribute significantly by clarifying requirements, decomposing stories, writing acceptance criteria, and helping the team estimate — excluding them would undermine the quality of refined items.