Answering: “What are two effective ways for the Scrum Team to make non-functional requirements visible?”

Non-functional requirements become visible by adding them to the Product Backlog or to the Definition of Done. A separate list or deferring test work to the next Sprint hides them or delays them.

Exam Question

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

• A. Add them to the Product Backlog to ensure transparency.
• B. Add them to the Definition of Done so work is taken care of every Sprint.
• C. Put them on a separate list on the Scrum board, available for all to see.
• D. Run the integration and regression tests before the end of the Sprint, and capture the open work for the Sprint Backlog of the next Sprint.

Correct Answer

A and B.

Why This Is the Correct Answer

The Product Backlog is “the single source of work undertaken by the Scrum Team,” so specific non-functional work, such as a performance upgrade, should be there where it is visible and ordered. Requirements that apply to everything, like security or response-time standards, fit better in the Definition of Done. That way every Increment meets them automatically. Both options keep the requirements transparent and part of normal work. Low transparency, as the Scrum Guide warns, leads to decisions that diminish value and increase risk.

Why the Other Options Are Wrong

C. Put them on a separate list on the Scrum board. A second list splits the work and bypasses the Product Owner’s ordering. The Product Backlog is the single source of work.

D. Run tests late and push open work into the next Sprint. This means work was not done in the current Sprint. Tests should be part of meeting the Definition of Done every Sprint.

Exam Tip

For non-functional requirements, the two homes are the Product Backlog for specific work and the Definition of Done for standards that apply everywhere.

Key Takeaways

• Specific non-functional work goes on the Product Backlog.
• Product-wide standards go in the Definition of Done.
• Separate lists and deferred testing hide work.