CAPM Practice: Determine how to document project controls for an adaptive project

Compliance requirements can be met in agile by including them in the definition of done and as backlog items. This integrates regulatory work into normal delivery flow rather than treating it as a separate overhead burden.

**Why not A:** Regulatory compliance does not prevent the use of agile methods. Many highly regulated industries — aerospace, medical devices, financial services — successfully use adaptive approaches by treating compliance tasks as backlog items and Definition of Done criteria. The development methodology and the compliance obligation are independent concerns.

**Why not B:** Running compliance documentation in a completely separate track with no connection to the agile team creates dangerous traceability gaps: delivered functionality may not match what is documented for regulators. Integrating compliance into the team's normal workflow ensures accuracy and reduces costly late-stage rework.

**Why not D:** No recognized regulatory framework offers a blanket exemption for agile projects, and applying for such a waiver is not an available option. Documentation requirements imposed by regulators apply regardless of the development methodology used; the question is how to fulfill them efficiently, not whether to seek escape from them.