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

Backlog refinement applies core BA skills: eliciting detailed acceptance criteria, analyzing story complexity, splitting large epics into implementable stories, and facilitating technical discussions about implementation approaches — ensuring the team always has a supply of 'ready' stories for sprint planning.

**Why not A:** Backlog refinement is a continuous, iterative activity that occurs throughout the project — not a quarterly event requiring executive approval. In agile frameworks, refinement sessions typically happen weekly or as a standing team activity to ensure an adequate supply of ready stories before each sprint planning meeting.

**Why not B:** While developers do assess technical feasibility during backlog refinement, defining it as solely a technical activity mischaracterizes the process. BAs and product owners play a central role by clarifying acceptance criteria, decomposing epics, and aligning business intent — without which developers cannot accurately assess or estimate the work.

**Why not D:** Removing outdated items from the backlog is one small housekeeping task that may occur during refinement, but it is not the defining purpose of the activity. Backlog refinement is primarily about elaborating and preparing upcoming stories — adding acceptance criteria, splitting large items, clarifying scope, and estimating effort — so the team can confidently commit to work in sprint planning.