Question

During a release planning session for a regulated healthcare product, your compliance officer insists that all user stories must be fully documented with detailed requirements specifications before development begins, citing audit requirements. Your agile team argues this contradicts their working agreements and will create massive waste, as they've successfully used acceptance criteria and collaborative elaboration for 15 sprints. The compliance officer shows you audit findings from another division that was penalized for insufficient documentation. Your organization has no precedent for agile projects in regulated environments. How do you proceed?

Accepted Answer

Engage a compliance specialist familiar with agile in regulated industries to define an appropriate documentation framework that satisfies both regulatory requirements and agile principles before proceeding

Answer

Negotiate a hybrid approach where the team creates lightweight specification documents just-in-time during refinement, treats them as living artifacts updated throughout development, and captures final state at sprint end for compliance archives

Answer

Explain to the compliance officer that agile projects are exempt from traditional documentation requirements because working software is the primary measure of progress, and point them to the agile manifesto

Answer

Implement the compliance officer's requirements fully to ensure regulatory safety, then work to optimize the documentation process over time as the team builds trust with compliance

PMP Practice Question: Process — Agile, Hard

More Process Questions