How does Scrum handle non-functional requirements (NFRs)? Non-Functional Requirements (NFRs) like security, performance, and scalability are treated as part of the Definition of Done (DoD) or explicitly captured in stories or tasks.

pproaches:

• Embed NFRs into acceptance criteria.
• Use technical enabler stories to address infrastructure or performance needs.
• Define NFR-related checklists in DoD.

Example:

For a fintech app, performance NFRs (e.g., “page load < 2 sec”) are part of every story's

DoD. Security is validated through automated scans in CI/CD.