Scrum PSPO-I Exam - Topic 2 Question 29 Discussion

Actual exam question for Scrum's PSPO-I exam

Question #: 29
Topic #: 2

[All PSPO-I Questions]

How should a Scrum Team deal with non-functional requirements?

(choose the best answer)

AManage them during the Integration Sprint prior to the Release Sprint.

BAssign them to the lead developers on the team.

CEnsure every Increment meets them.

DMake sure the release department understands these requirements, but it is not the
Scrum Team's responsibility.

Show Suggested Answer

Suggested Answer: C

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.

by Lang at Mar 05, 2025, 10:43 AM

Limited Time Offer

25%

Off

Get Premium PSPO-I Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Paola

5 months ago

Wait, are we really saying it's not the Scrum Team's responsibility? That seems off.

upvoted 0 times

...

Elfriede

5 months ago

I disagree, D seems too dismissive of the team's role.

upvoted 0 times

...

Geraldine

5 months ago

C is definitely the way to go! Every Increment should meet those requirements.

upvoted 0 times

...

Antonio

6 months ago

Honestly, I thought non-functional requirements were just a given for every Increment.

upvoted 0 times

...

Billye

6 months ago

A sounds reasonable, but isn't it risky to leave them for the Integration Sprint?

upvoted 0 times

...

Glenna

6 months ago

I’m leaning towards "C" too, but I wonder if it’s realistic to ensure every Increment meets all non-functional requirements.

upvoted 0 times

...

Lelia

6 months ago

I feel like "A" could work, but it might not be the best approach since it suggests waiting until the Integration Sprint.

upvoted 0 times

...

Ahmed

7 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.

upvoted 0 times

...

Lera

7 months ago

I think non-functional requirements should be integrated into each Increment, but I'm not sure if "C" is the best choice.

upvoted 0 times

...

Yun

7 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.

upvoted 0 times

...

Dean

7 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.

upvoted 0 times

...

Lynette

7 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.

upvoted 0 times

...

Rolande

8 months 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.

upvoted 0 times

...

Shonda

8 months 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.

upvoted 0 times

...

An

1 year ago

I think managing non-functional requirements during the Integration Sprint makes sense, as it allows for early identification and resolution of any issues.

upvoted 0 times

...

Altha

1 year 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.

upvoted 0 times

...

Garry

1 year 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.

upvoted 0 times

Tarra

1 year ago

D) Make sure the release department understands these requirements, but it is not the Scrum Team's responsibility.

upvoted 0 times

...

Trinidad

1 year 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.

upvoted 0 times

...

Tonette

1 year ago

A) Manage them during the Integration Sprint prior to the Release Sprint.

upvoted 0 times

...

Miesha

1 year ago

I agree with Kerry. It's important for the team to focus on meeting those requirements in each increment.

upvoted 0 times

...

Van

1 year 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.

upvoted 0 times

...

Selma

1 year 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.

upvoted 0 times

...

Katie

1 year 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.

upvoted 0 times