Answering: “How should a Scrum Team deal with non-functional requirements?”

The Scrum Team should make sure every Increment meets its non-functional requirements. Leaving them for later, for a lead developer or for another department builds up risk and undone work.

Exam Question

How should a Scrum Team deal with non-functional requirements? (choose the best answer)

• A. Ensure every Increment meets them.
• B. Assign them to the lead developers on the team.
• C. Manage them during the Integration Sprint proceeding the Release Sprint.
• D. Make sure the release department understands these requirements, but it is not the Scrum Team’s responsibility.

Correct Answer

A. Ensure every Increment meets them.

Why This Is the Correct Answer

Non-functional requirements cover things like security, performance, reliability and accessibility. Because they apply across many features, they are often captured in the Definition of Done, which the Scrum Guide describes as “a formal description of the state of the Increment when it meets the quality measures required for the product.” It also says “Work cannot be considered part of an Increment unless it meets the Definition of Done.” If an Increment does not meet them, it is not truly usable, and the gap becomes hidden technical debt. Building these qualities into every Increment keeps the product releasable and keeps transparency honest.

Why the Other Options Are Wrong

B. Assign them to the lead developers. Scrum has no lead developer role, and quality is shared by all Developers. Assigning it to a few creates bottlenecks.

C. Manage them in an Integration Sprint before a Release Sprint. Scrum has no integration or release Sprints. Every Sprint must produce a Done, usable Increment.

D. The release department handles them, not the Scrum Team. The Scrum Team is responsible for all product-related activities. Pushing quality to another department means the Increment is not really done.

Exam Tip

Any answer that postpones quality to a special Sprint or hands it to another group is wrong. Think “every Increment” whenever quality comes up.

Key Takeaways

• Non-functional requirements are part of every Increment.
• The Definition of Done is a natural home for them.
• Integration and release Sprints are not part of Scrum.