You are leading a regulatory compliance project using a hybrid approach where legal requirements are managed predictively with sequential gate approvals, while technical implementation uses iterative sprints. After three sprints, the compliance team reviews the working software and identifies that two implemented features may not fully satisfy regulatory requirements. The development team argues that requirements were ambiguous and their interpretation was reasonable. The next compliance gate is in two weeks. What is the best course of action?

Question

Accepted Answer

The correct answer is A. The issue stems from insufficient shared understanding between teams working in different methodologies. A requirements workshop creates alignment and prevents future misinterpretation by establishing clear, testable acceptance criteria that bridge compliance rigor with iterative development (ECO Process Task 1.5). This collaborative approach addresses the root cause while maintaining project momentum. Option B represents waterfall thinking that undermines the hybrid approach's benefits—stopping all work creates unnecessary delay when refinement and continued progress on unaffected items remains possible. Option C ignores the compliance risk severity in a regulated environment. Option D unnecessarily escalates what is fundamentally a requirements clarity issue that the project team should resolve collaboratively.

More Process Questions