Which statement best describes how NFRs relate to backlog management?

• A. NFRs influence backlog by constraints and require items to implement or evolve them
• B. NFRs are ignored in backlog management
• C. NFRs are separate from backlog
• D. NFRs replace all backlog items

Answer: (A)

Nonfunctional requirements set the quality constraints the system must meet, and they shape how the backlog is refined. They act as constraints on backlog items, so every backlog item—whether a user story or an architectural enabler—must address those quality attributes or evolve the design to satisfy them. This means NFRs influence what gets prioritized and how acceptance criteria are defined, since a story or feature should demonstrate that these quality attributes are met (for example, performance, security, reliability). NFRs are integrated into backlog management rather than being ignored or treated as separate, and they do not replace backlog items—they guide and constrain what is built, often driving architectural work or enablers to ensure the system meets the required standards. For instance, a performance NFR might lead to backlog items that implement caching or load-testing strategies, while a security NFR might require specific authentication, authorization, and encryption work as part of the item or as an accompanying enabler.