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.

Answer: B,D

Latest PSM I Dumps Valid Version with 197 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
1 Comment
Inline Feedbacks
View all comments
DeDan
DeDan
2 years ago

Hi there,
why is ‘B’ considered the right answere, when the only authorized person to change the product backlog is the product owner?
I was going for ‘A’ instead , understanding the Scrum Board term as an alternative term for Scrum backlog.

I am fully fine with ‘D’ for sure.