CAPM Practice: Determine how to gather requirements

Business rules are constraints governing business behavior — tax calculations, approval thresholds, regulatory compliance requirements. BAs must identify and capture them explicitly; they're often embedded in tacit knowledge or policy documents rather than stakeholder memory.

**Why not A:** Informal team norms for how the project team works together are team operating agreements or working agreements, not business rules. Business rules are organizational policies and regulations that govern how the business operates and must be reflected in the solution's behavior.

**Why not C:** Technical coding and software design standards are development standards, not business rules. Business rules are business-level policies and regulations (like tax calculations or approval thresholds) that constrain how the solution must behave, not technical implementation standards.

**Why not D:** Rules for prioritizing requirements in the backlog are backlog management or prioritization frameworks, not business rules. Business rules are organizational constraints that the delivered solution must enforce, independent of how requirements are prioritized during development.