The Perceived Conflict
Many pharma professionals believe agile and GxP compliance are fundamentally incompatible: agile embraces change, GxP demands control; agile minimizes documentation, GxP requires extensive evidence. This perceived conflict is based on a misunderstanding of both frameworks. Agile doesn't prohibit documentation — it prioritizes working software alongside necessary documentation. GxP doesn't require waterfall — it requires evidence that systems are fit for intended use.
Practical Patterns
- User Story Traceability: Each user story maps to requirements in the URS. Acceptance criteria double as test case specifications. This creates traceability without separate documentation artifacts.
- Sprint-Aligned Validation: Validation activities (IQ/OQ/PQ equivalents) execute within the sprint that delivers the corresponding functionality, not as a separate post-development phase.
- Living Documentation: Validation documents are updated continuously in a wiki or document management system, reviewed each sprint, and baselined at release milestones.
- Automated Testing: Automated regression tests serve dual purpose: development quality assurance and GxP validation evidence. Test execution logs become part of the validation package.
- Risk-Based Approach: Not all user stories require the same validation rigor. Risk assessment determines documentation depth, aligned with GAMP 5 risk-based principles.
The question is never "agile or GxP?" — it's "how do we design our agile process to produce the evidence GxP requires, as efficiently as possible?"