What are two ways that regulatory compliance issues are dealt with in Scrum? (Choose the best two answers)

Question

Options

• AThey are addressed by a separate team who is responsible for compliance issues.
• BThey are addressed along with functional development of the product.
• CThey are discussed, determined, and documented before the actual feature development Sprints.
• DThey are added to the Product Backlog and addressed in early Sprints, while always requiring at

• A
  7% (2)
• B
  89% (25)
• C
  4% (1)

Explanation

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

No community discussion yet for this question.