What are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)

What are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)
A . Put them on a separate list on the Scrum board, available for all to see.
B . Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
C . 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.
D . Add them to the definition of “Done” so the work is taken care of every Sprint.

View Answer

Answer: B,D

Explanation:

The correct answers are B and D, because adding non-functional requirements to the Product

Backlog and keeping the Product Owner posted on the expected effort helps prioritize and plan them in alignment with the product vision and goals. Additionally, adding non-functional requirements to the definition of ‘Done’ ensures that they are met every Sprint and do not accumulate technical debt.

Reference: Suggested Reading for Professional Scrum Master™ I