Team level NFRs apply to...?

• A. The entire enterprise
• B. Feature or component in team's domain
• C. All ARTs
• D. Only non-functional parts

Answer: (B)

Team-level nonfunctional requirements define the quality attributes that a team’s deliverables must meet for the features or components within that team’s domain. They guide how the team designs, builds, tests, and operates those items, covering attributes like performance, reliability, security, maintainability, and usability. Because these NFRs are scoped to the work the team is responsible for, they apply specifically to the features or components the team owns, not to the entire enterprise or every ART. While some NFRs can be shared across teams, at this level the focus remains on the team's own domain. They apply to the delivery of the team’s features, and can influence acceptance criteria and how work is done, rather than being limited to nonfunctional parts only.