back to notes

NFRs: Non-Functional Requirements

NFRs: Non-Functional Requirements

Non-Functional Requirements Define “how well” a function works, providing teams with constraints and directives. NFRs are also “enablers” necessary to make the feature or story functional as it is developed, tested, and deployed. Failure to address NFR concepts like performance, usability, security, infrastructure needs, accessibility and regulatory compliance can lead to expensive rework and unhappy customers.

Non-Functional Requirements can be captured at various levels As a technical enabler user story when applicable Definition of Done (if the NFR applies to all stories in a product /VS) Acceptance Criteria (if the NFR applies to one and only 1 story)



last updated august 2019