Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Scrum PSM-I Exam - Topic 5 Question 82 Discussion

Actual exam question for Scrum's PSM-I exam
Question #: 82
Topic #: 5
[All PSM-I Questions]

What are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: B, D

The best two answers are B and D. These two ways of dealing with regulatory compliance issues are consistent with Scrum's values and principles, as they allow the Scrum Team to deliver valuable and potentially releasable increments of the product while meeting the necessary standards and regulations. They also enable the Scrum Team to inspect and adapt their compliance strategy based on feedback and changing requirements.

A is not a good answer because it creates a separate silo of responsibility for compliance issues, which can lead to delays, conflicts, and inefficiencies. It also violates the Scrum value of transparency, as the compliance team may not have full visibility into the product development process.

C is not a good answer because it implies a waterfall approach that assumes all the compliance requirements are known and fixed upfront, which is rarely the case. It also reduces the flexibility and responsiveness of the Scrum Team, as they may have to follow a rigid plan that does not reflect the current reality of the product or the market.


by Salome at Jan 27, 2025, 01:50 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Franklyn
6 months ago
Not sure if a separate list is effective. Isn't it just more clutter?
upvoted 0 times
...
Vesta
6 months ago
Wait, can you really capture open work for the next Sprint like that?
upvoted 0 times
...
Jose
6 months ago
Definitely agree with putting them in the definition of "Done."
upvoted 0 times
...
Brandee
7 months ago
I think adding them to the Product Backlog is the way to go.
upvoted 0 times
...
Doyle
7 months ago
A separate list on the Scrum board sounds good!
upvoted 0 times
...
Nickie
7 months ago
I feel like running tests before the end of the Sprint might not make them visible enough. It seems more reactive than proactive.
upvoted 0 times
...
Ethan
7 months ago
Adding them to the definition of "Done" sounds familiar, but I can't recall if that covers all non-functional aspects.
upvoted 0 times
...
Skye
7 months ago
I remember a practice question where we discussed adding them to the Product Backlog. That seems like a solid option.
upvoted 0 times
...
Rosendo
8 months ago
I think putting non-functional requirements on a separate list could help, but I'm not sure if that's the best way.
upvoted 0 times
...
Doretha
8 months ago
I'm feeling pretty confident about this one. I'd choose options A and D - putting the non-functional requirements on the Scrum board and including them in the definition of "Done". That way the whole team is aware of them and they get consistently taken care of.
upvoted 0 times
...
Deandrea
8 months ago
Okay, let's see here. I think the key is making the non-functional requirements visible to the whole team. So I'd probably go with A and D - putting them on the Scrum board and defining them as part of "Done". That way everyone can see them and make sure they're addressed.
upvoted 0 times
...
Georgeanna
8 months ago
Hmm, I'm a bit unsure about this one. I'm thinking options B and D might be the way to go - adding them to the Product Backlog and including them in the definition of "Done". But I'll need to double-check the details to make sure I'm interpreting it correctly.
upvoted 0 times
...
Sina
8 months ago
This seems pretty straightforward. I'd go with options A and D - putting the non-functional requirements on the Scrum board and including them in the definition of "Done" so they're always addressed.
upvoted 0 times
...
Josefa
1 year ago
Hmm, D sounds like the way to go. 'Definition of Done' is the holy grail. Though I do like the idea of B - the PO can crack the whip on those non-functional requirements!
upvoted 0 times
Leonora
12 months ago
B) Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
upvoted 0 times
...
Vallie
1 year ago
D) Add them to the definition of ''Done'' so the work is taken care of every Sprint.
upvoted 0 times
...
Renay
1 year ago
A) Put them on a separate list on the Scrum board, available for all to see.
upvoted 0 times
...
...
Stefania
1 year ago
D all the way! Putting them right in the 'Definition of Done' is a surefire way to keep the team focused on them. Though B is a close second - the PO better be on top of their game!
upvoted 0 times
...
Rikki
1 year ago
I prefer B and D. Adding them to the Product Backlog keeps the Product Owner informed, and including them in the definition of 'Done' ensures they are completed.
upvoted 0 times
...
Laila
1 year ago
C is an interesting approach, but I'm not sure capturing open work for the next Sprint is the best way to make them visible during the current one. D and B get my vote.
upvoted 0 times
Wenona
1 year ago
I agree, D and B seem like the best options to ensure everyone is aware of the non-functional requirements.
upvoted 0 times
...
Deandrea
1 year ago
C is a good point, but I think D is more effective for making non-functional requirements visible.
upvoted 0 times
...
...
Deja
1 year ago
I like D - adding them to the 'Definition of Done' ensures they don't get forgotten. Though B is good too, as long as the PO is keeping a close eye on them.
upvoted 0 times
Cristy
12 months ago
A) Put them on a separate list on the Scrum board, available for all to see.
upvoted 0 times
...
Leontine
12 months ago
B) Add them to the Product Backlog and keep the Product Owner posted on the expected effort.
upvoted 0 times
...
Minna
1 year ago
D) Add them to the definition of ''Done'' so the work is taken care of every Sprint.
upvoted 0 times
...
Dorothea
1 year ago
A) Put them on a separate list on the Scrum board, available for all to see.
upvoted 0 times
...
...
Mi
1 year ago
D and B seem like the most straightforward options. Keeping the non-functional requirements visible through the 'Definition of Done' and the Product Backlog is key.
upvoted 0 times
...
Irma
1 year ago
I agree with you, Vicki. Putting them on a separate list and adding them to the definition of 'Done' ensures they are not overlooked.
upvoted 0 times
...
Vicki
1 year ago
I think A and D are good ways to make non-functional requirements visible.
upvoted 0 times
...

Save Cancel