Answering: “What are two ways that regulatory compliance issues are dealt with in Scrum?” (PSM I)

Regulatory compliance is handled alongside functional development and placed on the Product Backlog for early Sprints, always delivered with at least some business functionality. It is not settled up front in a separate phase or handed to a separate team.

Exam Question

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

• A. They are discussed, determined, and documented before the actual feature development Sprints.
• B. They are addressed along with functional development of the product.
• C. They are added to the Product Backlog and addressed in early Sprints, while always requiring at least some business functionality, no matter how small.
• D. They are addressed by a separate team who is responsible for compliance issues.

Correct Answer

B and C.

Why This Is the Correct Answer

In Scrum, compliance work is part of what is needed to improve the product, so it lives on the Product Backlog or, where it applies to everything, in the Definition of Done. Building it alongside features lets the team inspect real, working compliance every Sprint instead of trusting documents. Putting compliance items early reduces risk, but each Sprint still produces a usable Increment. The Scrum Guide describes the Scrum Team as “responsible for all product-related activities,” which includes meeting regulatory needs.

Why the Other Options Are Wrong

A. Discuss, decide and document them before feature Sprints start. This is an up-front phase. Scrum does not have Sprints that deliver nothing usable, and compliance understanding improves as the product is built.

D. Have a separate compliance team handle them. A hand-off to another team breaks cross-functionality and pushes risk to the end. The Scrum Team stays responsible for a compliant, done Increment.

Exam Tip

For any non-functional or compliance question, look for answers that keep the work inside normal Sprints with the Scrum Team. Phases and separate teams are traps.

Key Takeaways

• Compliance work belongs on the Product Backlog or in the Definition of Done.
• Every Sprint still delivers some business functionality.
• The Scrum Team, not a separate group, owns compliance.