Navigating Governance and Audits in Agile Environments
Most organizations conduct audits to verify that their processes are functioning effectively and to identify areas for improvement. In regulated industries, external audits are a standard practice. Teams need some level of governance to ensure no one cuts corners.
When Agile Teams Face Waterfall Governance
On SPaMCAST, I recently shared a story about an agile team facing stricter governance than a waterfall project. The level of executive sign-offs and documentation was shocking to everyone. Here’s what the QA team had to deliver:
1. New Test Strategy and Plan for Every Release
The team had to use a rigid waterfall template for each release. They documented detailed plans, even when only epics or high-level stories existed. With frequent releases, they spent too much time rewriting documents that quickly became outdated.
2. Test Exit Reports for Every Release
For every release, the team had to produce a new exit report using a specific template. They were unable to link to summary reports in Jira or Zephyr. Instead, they manually recorded all numbers and included notes from retrospectives.
3. Release Sign-Offs
Even after publishing a definition of done, executives had to sign off on every release. The team sent individual emails confirming that development, testing, and reviews had finished before moving to production.
Imagine repeating this process every month!
The Audit Experience
These requirements made audits a scramble. The team passed, but only after rushing to complete all the paperwork. The challenge grew because the organization’s Agile Center of Excellence (CoE) established these rules and subsequently revised them several times. Teams had to adjust their audit deliverables to meet the latest requirements continually.
We never identified the root cause of this extra governance. Did the CoE impose waterfall-style controls without considering the agile context? Or did the organization revert to old habits after decades of experience with the waterfall method?
Striking the Right Balance
Governance plays a crucial role in ensuring quality and compliance, particularly in areas where regulations are applicable. The trick is to identify what information auditors truly need and report it with minimal disruption. When organizations adapt governance to fit agile practices—instead of forcing waterfall templates—they make audits smoother and more meaningful. Teams stay focused on delivering value instead of getting bogged down by paperwork.
Bottom line: Governance and audits are here to stay, but they don’t have to slow you down. Align audit requirements with agile ways of working, focus on what matters, and keep your teams delivering value.