How does Scrum handle non-functional requirements (NFRs)?

Short answer: 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. Approaches: Embed NFRs into acceptance criteria. Use technical enabler stories to address infrastructure or performance needs. Define NFR-related checklists in DoD.

Example code

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.

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.