PSM I Exam QuestionsBrowse all questions from this exam

PSM I Exam - Question 7


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

Show Answer
Correct Answer: BD

Non-functional requirements should be visible and transparent to the entire Scrum Team and stakeholders. Adding them to the Product Backlog ensures transparency as the Product Backlog is a constantly updated and visible artifact that everyone can see. This helps to keep track of non-functional requirements and their priorities. Including non-functional requirements in the definition of 'Done' ensures that these requirements are addressed during each sprint and not overlooked, maintaining the product’s quality consistently.

Discussion

10 comments
Sign in to comment
SnomaxOptions: BD
Oct 10, 2023

B and D

ZuitOptions: AB
Jul 2, 2023

A and B increase the visibility. D ensures that is is done, but visibility is limited

DjedjigOptions: BD
Feb 19, 2024

B,D are correct

Sco365Options: BD
Aug 17, 2023

Answer should be B&D

skafandriiOptions: BD
Aug 22, 2023

looks logical

CarlosTheBoldestOptions: BD
Dec 20, 2023

https://www.scrum.org/resources/blog/how-handle-non-functional-requirements-nfrs

Quinns_Options: AD
Mar 6, 2024

A,D A. Putting non-functional requirements on a separate list on the Scrum board makes them visible and ensures that the team is aware of them during Sprint planning and execution. It allows for easy reference and tracking of these requirements throughout the development process. D. Adding non-functional requirements to the definition of "Done" ensures that they are considered completed at the end of each Sprint. This helps in maintaining the quality of the product and ensures that these requirements are not overlooked or neglected during the development process.

Mi_WindsorOptions: BD
Jul 30, 2023

B and D is the correct answer

Jyoti1010Options: BD
Sep 26, 2023

B and D

psikorskiOptions: BD
Oct 9, 2023

B and D "Scrum’s artifacts represent work or value. They are designed to maximize transparency of key information. Thus, everyone inspecting them has the same basis for adaptation" The Artifacts are: Product Backlog, Sprint Backlog and Increment - with the Definition of Done. regarding A. - SCRUM framework does not have a Scrum board artifact, so it may not everyone in the organization may be aware that it exists and adding a separate list for NFRs just adds complexity. regarding C - this could be one of the actions to perform to ensure the increment meets the definition of done, however - it does not necessarily lead to increased transparency.