CAPM Practice: Determine how project methodologies influence business analysis processes

Even in agile, non-functional requirements (NFRs) must be explicitly defined — 'the system must handle 10,000 concurrent users' is a constraint regardless of whether architecture emerges or is defined upfront. NFRs must be included in the Definition of Done and tested throughout delivery.

**Why not A:** Emerging architecture does not mean technical requirements are completely flexible. Non-functional requirements like performance and security targets remain as fixed constraints that the architecture must satisfy, even as the specific architectural approach evolves iteratively.

**Why not B:** Agile does not eliminate the need for non-functional requirements. Developers making architecture decisions still need explicit quality constraints to design against. Without defined NFRs, the team has no measurable targets for performance, security, or scalability.

**Why not C:** Requiring complete architecture requirements before development begins contradicts the principle of emerging architecture in agile. The point is that the architecture evolves, but the quality constraints (NFRs) that guide that evolution must still be explicitly defined upfront.