MENU
How should a Scrum Team deal with non-functional requirements?
(choose the best answer)
Suggested Answer: C
Get Premium PSPO-I Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
In Scrum, non-functional requirements are part of the quality and completeness criteria for the product. They should be incorporated into the Definition of Done, ensuring that each Increment meets these requirements, making it potentially shippable and usable by stakeholders.
28 comments · newest first
PA
Paola
10 months ago
Wait, are we really saying it's not the Scrum Team's responsibility? That seems off.
EL
Elfriede
10 months ago
I disagree, D seems too dismissive of the team's role.
GE
Geraldine
10 months ago
C is definitely the way to go! Every Increment should meet those requirements.
AN
Antonio
10 months ago
Honestly, I thought non-functional requirements were just a given for every Increment.
BI
Billye
10 months ago
A sounds reasonable, but isn't it risky to leave them for the Integration Sprint?
GL
Glenna
11 months ago
I’m leaning towards "C" too, but I wonder if it’s realistic to ensure every Increment meets all non-functional requirements.
LE
Lelia
11 months ago
I feel like "A" could work, but it might not be the best approach since it suggests waiting until the Integration Sprint.
AH
Ahmed
11 months ago
I remember a practice question where we discussed the importance of addressing non-functional requirements throughout the development process. "C" seems to align with that.
LE
Lera
11 months ago
I think non-functional requirements should be integrated into each Increment, but I'm not sure if "C" is the best choice.
YU
Yun
12 months ago
Hmm, I'm not sure about that. Shouldn't the Scrum Team be responsible for ensuring the non-functional requirements are met? That seems like a core part of their job.
DE
Dean
12 months ago
I think the answer is to make sure the release department understands these requirements, but it's not the Scrum Team's responsibility. We should focus on delivering the functionality.
LY
Lynette
12 months ago
I'm a bit confused. Should we really be managing non-functional requirements separately from the regular work? That doesn't seem very Agile to me.
RO
Rolande
1 year ago
Okay, I've got this. The key is to ensure every Increment meets the non-functional requirements. That's the best way to deal with them in Scrum.
SH
Shonda
1 year ago
Hmm, this is a tricky one. I'll need to think carefully about the Scrum principles and how they apply to non-functional requirements.
AN
An
2 years ago
I think managing non-functional requirements during the Integration Sprint makes sense, as it allows for early identification and resolution of any issues.
AL
Altha
2 years ago
I believe assigning non-functional requirements to lead developers could lead to silos. It's better to have the whole team responsible for them.
GA
Garry
2 years ago
C) Ensure every Increment meets them. Duh, it's Scrum 101. The whole team has to work together to meet all the requirements, functional or not.
TA
Tarra
2 years ago
D) Make sure the release department understands these requirements, but it is not the Scrum Team's responsibility.
TR
Trinidad
2 years ago
C) Ensure every Increment meets them. Duh, it's Scrum 101. The whole team has to work together to meet all the requirements, functional or not.
TO
Tonette
2 years ago
A) Manage them during the Integration Sprint prior to the Release Sprint.
MI
Miesha
2 years ago
I agree with Kerry. It's important for the team to focus on meeting those requirements in each increment.
VA
Van
2 years ago
D) Make sure the release department understands these requirements, but it is not the Scrum Team's responsibility? Haha, nice try, but the Scrum Team can't just dump that on someone else.
SE
Selma
2 years ago
B) Assign them to the lead developers on the team? Really? That's like passing the buck. The whole team should be responsible for non-functional requirements.
KA
Katie
2 years ago
C) Ensure every Increment meets them. That's the way to go! The Scrum Team is responsible for delivering a working product, and non-functional requirements are just as important as the functional ones.
PO
Polly
2 years ago
C) Ensure every Increment meets them.
PA
Paola
2 years ago
B) Assign them to the lead developers on the team.
KA
Kathrine
2 years ago
A) Manage them during the Integration Sprint prior to the Release Sprint.
KE
Kerry
2 years ago
I think the Scrum Team should ensure every Increment meets non-functional requirements.