What are two good ways for the Development Team to make a non-functional requirements visible?

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

View Answer

Answer: A,C