MENU
How should a Development Team deal with non-functional requirements?
Suggested Answer: A
Get Premium PSM-I Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
The correct answer is A, because the Scrum Guide states that ''the definition of 'Done' is a formal description of the state of the Increment when it meets the quality measures required for the product.'' Therefore, non-functional requirements should be part of the definition of 'Done' and ensure every Increment meets them.
12 comments · newest first
FR
Freeman
3 days ago
C) sounds reasonable, but can we really fit that in?
DO
Donette
8 days ago
I disagree, B) shifts too much responsibility away from the team.
DE
Deeann
13 days ago
A) is the way to go! Every Increment should meet those requirements.
SH
Sherell
18 days ago
Wait, non-functional requirements can be ignored until the last sprint? Really?
HI
Hildred
24 days ago
D) seems risky, lead devs are already swamped!
TH
Theron
29 days ago
C) sounds like a solid plan, but is it practical?
CA
Carey
1 month ago
I disagree, it's everyone's responsibility, not just the devs.
AU
Augustine
1 month ago
A) is definitely the way to go!
NE
Nenita
1 month ago
I’m leaning towards option A too, but I wonder if there are cases where it might be okay to delegate some of those responsibilities to lead developers.
GE
Gerald
2 months ago
I think we had a similar question about handling non-functional requirements in a sprint. If I recall correctly, it was about addressing them throughout the development process, not just in a specific sprint.
ST
Stephen
2 months ago
I'm not entirely sure, but I feel like we practiced a question where it mentioned that the Development Team is responsible for these requirements. Was that in the context of Agile?
BE
Bettyann
2 months ago
I remember we discussed that non-functional requirements should be integrated into every Increment, so I think option A makes sense.