(What are two ways that regulatory compliance requirements are dealt with in Scrum?

In Scrum, regulatory and compliance requirements are not treated as work outside the Scrum Team or postponed until a separate phase. They must be made visible and managed as part of normal product development. Option C is correct because any work that is needed for the product, including compliance-related requirements, should be represented in the Product Backlog. The Product Backlog is the single source of work undertaken by the Scrum Team, so compliance items are handled alongside functional and technical work during Sprints.

Option D is also correct because compliance often affects whether an Increment is truly complete. Scrum requires each Increment to meet the Definition of Done, which creates transparency about quality and completeness. If regulatory conditions are necessary for releasability or completeness, they should be included in the Definition of Done and verified every Sprint.

Options A and B are incorrect because Scrum does not promote handing compliance to a separate team or completing all compliance analysis before Sprinting starts. Scrum uses an iterative, incremental approach where such requirements are addressed continuously.