What are two effective ways for the Scrum Team to make non-functional requirements visible? (choose the best two answers)

Non-functional requirements (NFRs) define the quality attributes of a system, such as security, performance, and usability. The Scrum framework provides two primary ways to make them visible and ensure they are addressed. First, if an NFR is a pervasive quality standard that should apply to every relevant Increment (e.g., "all code must pass security scans"), it should be included in the Definition of Done. This ensures the team consistently meets this quality standard every Sprint. Second, if an NFR requires a significant, discrete piece of work (e.g., "Refactor the database to support 1 million concurrent users"), it should be added to the Product Backlog as a Product Backlog Item (PBI). This makes the work transparent, allowing the Product Owner to prioritize it against other functional requirements.

A. Deferring incomplete work to the next Sprint is an anti-pattern. The goal is to produce a "Done" Increment that meets all requirements, including NFRs, within the Sprint.
B. Creating separate lists outside the official Scrum artifacts (Product Backlog, Sprint Backlog) reduces transparency and can lead to work being overlooked. All work should be in the Product Backlog.

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide.

For option C (Definition of Done): "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product." (p. 10). NFRs are critical quality measures.

For option D (Product Backlog): "The Product Backlog is an emergent

ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team." (p. 8). This confirms that any work

including for NFRs

must reside in the Product Backlog to be transparent and prioritizable.

2. Inayat

I.

Salim

S. S.

Marczak

S.

Daneva

M.

& Shamshirband

S. (2015). A systematic literature review on agile requirements engineering. IEEE Transactions on Software Engineering

41(9)

839-860. https://doi.org/10.1109/TSE.2015.2433479

This review synthesizes research on agile practices. It identifies that NFRs are commonly handled in two ways: "as constraints on functional requirements (often in the form of acceptance criteria or the Definition of Done) or as separate non-functional requirements in the product backlog." (Section 4.2

"Handling NFRs"). This directly supports options C and D as established practices.