Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.

Unlimited Access

Get Unlimited Contributor Access to the all ExamTopics Exams!
Take advantage of PDF Files for 1000+ Exams along with community discussions and pass IT Certification Exams Easily.

Exam PSM I topic 1 question 7 discussion

Actual exam question from Scrum's PSM I
Question #: 7
Topic #: 1
[All PSM I Questions]

What are two effective ways for the Scrum 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 to ensure transparency.
  • 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.
Show Suggested Answer Hide Answer
Suggested Answer: BD 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
Quinns_
1 month, 3 weeks ago
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.
upvoted 2 times
...
Djedjig
2 months, 1 week ago
B,D are correct
upvoted 2 times
...
CarlosTheBoldest
4 months, 1 week ago
Selected Answer: BD
https://www.scrum.org/resources/blog/how-handle-non-functional-requirements-nfrs
upvoted 2 times
...
Snomax
6 months, 3 weeks ago
Selected Answer: BD
B and D
upvoted 4 times
...
psikorski
6 months, 3 weeks ago
Selected Answer: BD
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.
upvoted 1 times
...
Jyoti1010
7 months ago
B and D
upvoted 1 times
...
skafandrii
8 months, 1 week ago
Selected Answer: BD
looks logical
upvoted 2 times
...
Sco365
8 months, 2 weeks ago
Selected Answer: BD
Answer should be B&D
upvoted 2 times
...
Mi_Windsor
9 months ago
B and D is the correct answer
upvoted 1 times
...
Zuit
10 months ago
Selected Answer: AB
A and B increase the visibility. D ensures that is is done, but visibility is limited
upvoted 3 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...