What are two good ways for the Development Team to make non-functional requirements visible? (Choose two.)
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.
Franklyn
3 months agoVesta
3 months agoJose
3 months agoBrandee
4 months agoDoyle
4 months agoNickie
4 months agoEthan
4 months agoSkye
4 months agoRosendo
5 months agoDoretha
5 months agoDeandrea
5 months agoGeorgeanna
5 months agoSina
5 months agoJosefa
10 months agoLeonora
9 months agoVallie
9 months agoRenay
9 months agoStefania
10 months agoRikki
10 months agoLaila
10 months agoWenona
10 months agoDeandrea
10 months agoDeja
11 months agoCristy
9 months agoLeontine
9 months agoMinna
10 months agoDorothea
10 months agoMi
11 months agoIrma
11 months agoVicki
11 months ago