Your agile team has been delivering increments for a regulatory compliance product over the past four sprints. During the sprint review, the compliance officer raises concerns that while individual features work well, the product lacks end-to-end workflow validation required for regulatory approval. The product owner argues that all acceptance criteria were met and signed off. Stakeholders are now questioning whether the product will pass the mandatory audit in two sprints. The team has velocity data showing consistent delivery, but no integrated compliance testing has been performed. What should you do first to address this situation?

Question

Accepted Answer

The correct answer is A. Updating the definition of done to include end-to-end compliance validation addresses the root cause systemically and prevents future compliance gaps (ECO Process Task 3.16: Establish and maintain project quality standards). This ensures every increment meets regulatory requirements going forward. Option B treats compliance as technical debt rather than a fundamental quality requirement, creating a false choice between compliance and features. Option C is a predictive mindset that doesn't address the systemic issue. Option D focuses on retrospection without taking immediate corrective action needed before the audit.

More Process Questions