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

Where 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. 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.
E. Add them to the definition of "Done" so the work is taken care of every Sprint.

How To Pass PSM I Exam?

Scrum PSM I PDF dumps.

High quality PSM I PDF and software. VALID exam to help you pass.

How To Pass PSM II Exam?

Scrum PSM II PDF dumps.

High quality PSM II PDF and software. VALID exam to help you pass.

4 thoughts on “Where are two good ways for the Development Team to make non-functional requirements visible?

  1. B. Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
    +
    E. Add them to the definition of “Done” so the work is taken care of every Sprint.

    16
  2. E is fine, I am little confused in A/B , can someone explain why B not A, do we have to take extra effort for NFR’s?

    1. I think the reason for answer A is not correct is that even if we add it to the Scrum board it does not mean that it will be solved.

      1. Although there might be a scrum board in the Srum Team Room, a Scrum Board is not mentioned in the scrum guide and therefore it is not a neccessity. So A is wrong.

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.