KPM

Communicating Accounting Information Inventory Management WIP Non-GAAP Metrics Reduce Billing Bottlenecks Auditor Independence Accounting Methods Year-End Financials Auditing Revenue Recognition Inventory Management System Access To Capital M&A Due Diligence What Is Materiality Job-Costing Systems Technology Bank Reconciliation Cybersecurity New Segment Expense Disclosure Rules QuickBooks To Prepare 2024 Budgets Safeguard Organization Assets Offsetting Rules Inventory Count negotiation M&A Accounting Monthly Financial Close Shareholder advance Payroll challenges Prepare for audit QuickBooks income tax Crypto Accounting Percentage-Of-Completion Financial Statement PCAOB Overhead Mileage in QuickBooks UTPs Cross-Train Employee Benefit Plan Audits Accounts Receivable

Is Your Company Ready For Agile Auditing?

Agility — or the ability to react quickly — is essential to surviving and thriving in today’s competitive landscape. Though agile techniques were originally used in the realm of software development, this concept has many applications in the modern business world, including how companies approach their internal audits. Here is an overview of agile auditing and why many internal audit teams are using this method.

The Basics
Whereas a traditional audit requires extensive planning, fieldwork, and reporting, an agile audit moves at a faster pace. An agile audit also allows the audit team to continually refocus their attention and efforts where they are needed the most.

Agile auditing relies on the following key concepts:

Audit backlogs: The audit team keeps a backlog of reviewed and approved audit programs. As the environment evolves, the audit team can add, remove, or reprioritize audit programs within the backlog. This dynamic approach ensures that the audit team focuses on the most pressing issues — and reduces the likelihood that they will waste time on an issue from a previous audit plan that is no longer relevant.

User stories: Auditors create user stories that are made up of:

  • A user
  • An action
  • An outcome

Each story corresponds to a unit of work related to the audit. The user is the individual responsible for performing critical tasks related to the story. The action is what the user must do to generate a desired outcome.

For example, a retailer (the user) wants to process credit card payments from customers online (the action), so they can order online (the outcome). Creating a story provides the audit team with an understanding of the user’s requirements and the desired outcome.

Audit sprints: With a story defined, the audit team can deliver their work in sprints. Each sprint is normally completed in one to four weeks. Sprints may include defined tasks and regular check-ins with stakeholders. A sprint has a planning phase and includes short daily meetings with the audit team and stakeholders. Items on the daily agenda include:

  • Yesterday’s progress
  • The game plan for today
  • Potential challenges to completing the sprint

Each sprint concludes with the delivery of preliminary results to stakeholders. Reviewing the results of each sprint gradually over the course of the audit helps reduce surprises when the final audit report is submitted to stakeholders.

Benefits Abound
Agile auditing facilitates more frequent and timelier communications between auditors and stakeholders. This can lead to more robust partnerships and improvements in the accuracy and integrity of audit team’s findings. More frequent communication also allows the audit team and the business to identify and resolve problems quickly.

Contact us for more information. We can help you decide whether you are ready to transition to a more agile auditing approach and, if so, guide your internal audit team through the implementation process.

Related Articles

Talk with the pros

Our CPAs and advisors are a great resource if you’re ready to learn even more.