Question

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

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

Answer 1

In Scrum, compliance issues are typically addressed by integrating them into the product development process, either by including them with other product features or by adding them to the product backlog and prioritizing them in early Sprints. Separate teams or pre-development documentation are not commonly suggested practices in Agile methodologies.Option C, having a separate team for compliance, and Option D, documenting compliance before development, are not generally adopted in Scrum, which emphasizes cross-functional teams and iterative development.

Step-by-step explanation:

In Scrum, regulatory compliance issues are often addressed as part of the product development process. Two common ways that teams deal with compliance are:

Addressed along with functional development of the Product: Compliance requirements are treated as any other product feature. They are incorporated into user stories or product backlog items and are prioritized and developed in Sprints along with other features. This ensures that compliance is integrated into the solution from the beginning, rather than being an afterthought.

Added to the Product Backlog and addressed in early Sprints: Compliance tasks are added to the product backlog just like other work. They should be tackled in the early Sprints of the project to ensure that any compliance issues are dealt with early on. These tasks should also include some business functionality, no matter how small, to ensure that every Sprint delivers a potentially shippable product increment.

Option C, having a separate team for compliance, and Option D, documenting compliance before development, are not generally adopted in Scrum, which emphasizes cross-functional teams and iterative development.

Answer 2

Regulatory compliance issues in Scrum are addressed alongside functional development of the Product and added to the Product Backlog for early addressing.

Step-by-step explanation:

When it comes to regulatory compliance issues in Scrum, they are usually dealt with in two ways:

1. They are addressed along with functional development of the Product. Scrum teams prioritize regulatory compliance tasks alongside other product development tasks to ensure that compliance is incorporated into the final product.
2. They are added to the Product Backlog and addressed in early Sprints while always requiring at least some business functionality, no matter how small. This means that even if a regulatory compliance task is small, it is still addressed early in the development process to ensure it is not overlooked.