How to handle a NFR in backlog?

• A. Ignore until later
• B. Assign only to the PM
• C. Create items to implement or evolve them
• D. Discard as not needed

Answer: (C)

Non-functional requirements belong in the backlog as work items to implement or evolve. They describe the system qualities and constraints the solution must meet—things like performance, security, scalability, reliability, maintainability, and usability. In SAFe, capturing NFRs as backlog items (often as enablers) ensures they are planned, sized, prioritized, and tracked just like features. This keeps architecture and technical quality visible during PI planning and sprint execution, and it ties NFRs to testable criteria and acceptance criteria, so you can verify they’re met.

Treating NFRs as backlog items helps you address them across teams, not just leave them to one role or ignore them. It also supports building an architectural runway and aligning investments with system quality expectations. For example, an NFR around performance can be turned into an enabler item with a measurable target (such as a specific response time threshold), while a security NFR can translate into required controls and testing. Ignoring or discarding NFRs leaves risk unmitigated and quality untracked, whereas creating and evolving backlog items ensures continuous attention and delivery of the desired qualities.