Are NFR backlog items?

• A. Yes, they are backlog items
• B. No, but they are constraints
• C. They are epics
• D. They are risks

Answer: (B)

Non-functional requirements describe how the system must operate, not just what it should do. They set constraints on design and implementation—things like performance, availability, security, and compliance. In SAFe, these constraints guide architecture and delivery across teams and are typically enforced through architecture constraints, acceptance criteria, or explicit quality attributes tied to backlog work.

Because backlog items represent work to deliver value, NFRs aren’t themselves backlog items to be implemented as features. Instead, they constrain every backlog item and shape how each piece of work must be designed and tested. They aren’t epics (large deliverables) nor risks (uncertainties about future outcomes); they are the criteria that the solution must satisfy. If an NFR isn’t met, it can become a risk, but the NFR itself is a constraint guiding the work.