CAPM Practice: Determine how to gather requirements

Benchmarking identifies requirements by studying how peer organizations handle similar business challenges. Comparing against industry leaders or competitors surfaces requirements and standards that stakeholders might not otherwise know to request.

**Why not A:** Benchmarking in a business analysis context is not about testing software performance metrics such as load times or throughput. Software performance testing is a technical QA activity, whereas benchmarking involves comparing organizational practices, processes, or outcomes against industry standards or competitors.

**Why not B:** While benchmarking may inform performance targets, it is not the act of setting team performance targets itself. Benchmarking is an analytical technique for comparing current practices against external or internal standards of excellence, which may then feed into target-setting as a downstream activity.

**Why not C:** Prioritizing requirements by business value is a separate technique (such as MoSCoW or weighted scoring). Benchmarking specifically involves comparing practices or metrics against reference points — industry leaders, competitors, or recognized standards — to identify improvement opportunities.