CAPM Practice: Determine how to gather requirements

Right-sized requirements enable action without over-constraining. User stories that are too large (epics) can't be committed to in one iteration. Requirements too fine-grained prescribe implementation and leave no room for developer creativity. BAs calibrate granularity to what the team needs.

**Why not A:** Requirement granularity is not about document length in pages. A lengthy document can still have poorly calibrated detail levels, with some requirements too vague and others excessively detailed. Granularity concerns the precision of individual requirements.

**Why not B:** The number of stakeholders who contributed to a requirement has no bearing on its granularity. Granularity refers to the level of specificity in how a requirement is expressed, not its authorship or collaboration breadth.

**Why not D:** Grammatical detail in a sentence is unrelated to requirement granularity. Granularity addresses how finely a functional or technical need is decomposed — whether it provides enough detail for the team without over-constraining the solution design.