CAPM Practice: Determine how to gather requirements

A story meeting the Definition of Ready (understood, sized, with acceptance criteria, and no blocking dependencies) can be reliably committed to in iteration planning. Stories that aren't ready slow down planning and create mid-iteration surprises.

**Why not A:** Developer approval alone does not make a story ready. The Definition of Ready is a set of objective criteria — including clear acceptance criteria, appropriate sizing, and shared understanding — that must be satisfied. A team's verbal approval without these criteria being met leaves gaps that cause mid-sprint disruptions.

**Why not C:** The project manager adding a story to the sprint backlog is a scheduling action, not a readiness determination. Readiness is defined by the story's quality attributes (estimated, understood, small enough, acceptance criteria defined), not by who places it on a list.

**Why not D:** An arbitrary time-based rule like "written for at least two weeks" has no foundation in agile practice. A story could be written months ago and still lack acceptance criteria or be too large. Readiness is about completeness of definition, not elapsed time since creation.