Scrum Exam PSPO-I 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

An

3 months 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

3 months 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

3 months 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

3 months ago

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

upvoted 0 times

...

Trinidad

3 months 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

3 months ago

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

upvoted 0 times

...

Miesha

3 months ago

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

upvoted 0 times

...

Van

3 months 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

3 months 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

3 months 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