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

Scrum Exam PSM-I 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.


Contribute your Thoughts:

Josefa
5 days 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
...
Stefania
6 days 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
10 days 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
10 days 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
...
Deja
15 days 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
...
Mi
18 days 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
19 days 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
21 days ago
I think A and D are good ways to make non-functional requirements visible.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77