CAPM Practice: Determine how project methodologies influence business analysis processes

Backlog refinement is perpetual because requirements knowledge grows through delivery. Sprint reviews reveal new information, retrospectives surface process requirements, and market changes drive priority shifts. The BA continuously refines the backlog to keep it current, accurate, and ready for upcoming sprints.

**Why not A:** Product backlog refinement is not performed solely by the product owner. In practice, it is a collaborative activity involving the product owner, the development team, and often the BA. The BA plays a key role in clarifying requirements, adding acceptance criteria, and breaking down large items — contributions that make refinement effective.

**Why not C:** Backlog refinement is not a quarterly planning event — it happens continuously throughout the project. Treating it as a periodic event would allow the backlog to accumulate poorly defined items between sessions, creating bottlenecks when the team needs ready work. Continuous refinement ensures a steady flow of well-prepared backlog items.

**Why not D:** Describing refinement as a one-time activity before each sprint conflates it with sprint planning and understates its scope. While refinement does prepare items for upcoming sprints, it is an ongoing effort that looks further ahead than just the next sprint. Limiting it to a single pre-sprint session would not provide enough time to adequately clarify, estimate, and decompose backlog items.