diligent_sprinting-ahead-with-agile-auditing
diligent_sprinting-ahead-with-agile-auditing
Conclusion 21
A lot has changed for internal auditors over the past couple of
decades.
Before the Sarbanes-Oxley Act (SOX), internal auditors could be less visible in an organization. However, once SOX came
into play in 2002, they needed to stand up, speak up, and provide more insight into audits.
Now, there’s no shortage of expectations from regulators, executives, boards, and audit committees. Organizations are
looking beyond simple assurance that controls are effective. The bar has been raised and internal audit is now expected
to be more strategic and forward-thinking.
A global survey of chief audit executives2 found that those internal audit groups with the most impact and influence in
their organizations also tend to be the most innovative. (Deloitte analyzed the digital fitness of internal audit functions
by looking at five dimensions: vision and roadmap, ways of working, operations, services model, and stakeholder
engagement.) Similarly, PwC’s 2019 survey3 of the audit profession revealed that organizations who are more “digitally fit”
better support their stakeholders when it comes to taking risks and making decisions.
2 Deloitte, 2018, The innovation imperative: Forging internal audit’s path to greater impact and influence
3 PwC, 2019, State of the internal audit profession study
Traditionally, auditors have taken a controls-based approach to audit. The risk-based method of auditing starts
with business objectives and elevates the questioning of control effectiveness to strategy, process design,
implementation—and the validity of policy and procedures.
This means that organizations can be more insightful and holistic rather than just proactive, reactive, or linear in
their work. But to successfully implement risk-based auditing, an organization must have a solid risk management
framework in place.
Internal auditors now have huge amounts of data at their fingertips—they’re no longer limited to basing conclusions
only on manual controls and limited datasets. It’s easier to provide insights based on multiple data sources and
enhance sampling techniques to ensure statistical confirmation of exceptions.
From planning to fieldwork to reporting, a data-driven audit practice provides several benefits, including:
• Continuous monitoring of assessments, risk indicators, and process performance
Gaining stakeholder trust is paramount in your journey from assurance provider to advisor. Richard Chambers,
President and CEO of the Institute of Internal Auditors (IIA), states that trusted advisors must “provide insight and
foresight, not just hindsight.”4
According to PwC’s Internal Audit Advisory report, becoming a trusted advisor means “Providing value-added
services and proactive strategic advice to the business well beyond the effective and efficient execution of the
audit plan.” 5
By following a risk-based, data-driven path, internal auditors are already well on their way to becoming trusted
advisors. Add agile audit into the mix, and think of the possibilities!
4 Richard Chambers, 2017, Trusted advisors: Key attributes of outstanding internal auditors
5 PwC, 2017, Internal Audit Advisory: Confident and informed decision making for your third line of defense
Back in the early 2000s, software development teams were getting frustrated by the rigid methodologies available to
them. The waterfall approach was the most common, which is a sequential process that divides work into linear phases.
Using the waterfall method, developers would identify a problem and plan a solution, which could take months or even
years. As the team completed each step before moving on to the next, they would stick tightly to the project scope and
requirements.
As a result, products were being completed and delivered after long developments, but they no longer met customer
needs. There were also many unfinished projects, as teams would often abandon limping initiatives rather than see them
through to the end.
Business leaders recognized that the software industry wasn’t keeping up with the quick pace of technology and market
change, but what was the answer? It arrived in 2001, when a group of 17 developers met at a ski resort in Utah and
created what’s now known as the Agile Manifesto6 (see next page).
Following the manifesto’s creation, these thought leaders created the Agile Alliance, a non-profit organization with more
than 60,000 global members and subscribers who share agile-related resources and events.
Although the agile approach was originally created for software and IT, its framework is relevant and translatable across
every industry, including audit.
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development. Agile processes harness change for the
customer’s competitive advantage.
Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the
shorter timescale.
Business people and developers must work together daily throughout the project.
Build projects around motivated individuals. Give them the environment and support they need, and trust
them to get the job done.
The most efficient and effective method of conveying information to and within a development team is face-
to-face conversation.
Agile processes promote sustainable development. The sponsors, developers, and users should be able to
maintain a constant pace indefinitely.
Simplicity — the art of maximizing the amount of work not done — is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior
accordingly.
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
While audit quality is always a key consideration, the priority is on speed and efficiency over delivering a perfectly
polished project at the end.
This “try fast, fail fast” design accounts for the unexpected in case the team needs to suddenly shift gears. And while
everyone has a different role, the team is trusted to be self-organizing and cross-functional.
People- Predictable
driven OVER process and
insight procedure
Client Audit
OVER
collaboration mandate
Responding “Not in
OVER
to change the scope”
Process
Flexibility OVER rigidity
This common agile methodology has small cross-functional teams work on audit projects for short periods of time
(usually two-week sprints). Teams track the progress of audit tasks using the following categories: backlog, to do, in
progress, done, and complete. The Scrum team is self-governing and determines what to tackle within each sprint.
Sprints
MoSCoW
An acronym for “Must have, Should have, Could have, and Will not have.” This approach helps stakeholders prioritize
tasks to determine which audit activities will add the most value. It can be a challenge to use MoSCoW when auditors
are set in their ways of covering everything on a specific audit. ⁸
Kanban
A Kanban board is often used in scrum to visualize the team’s progress at various stages and to promote transparent
communication. A Kanban board displays cards and columns to help teams commit to and complete tasks.
Shu Ha Ri
This is a Japanese martial art concept that describes the progression of learning. Because the “student” first starts
learning and then gradually moves toward mastering a skill and letting go of old habits, it can be a good introductory
method for inexperienced agile audit teams. In a highly regulated industry (e.g., financial services or healthcare), this
method also means minimal to no changes in auditing methodology.
1 Enhanced flexibility
The elastic planning cycle of agile audit allows teams to prioritize tasks based on risks and company needs.
Instead of following a rigid internal audit plan, there’s a continually updated backlog of audits and projects.
Communication is more frequent and informal.
8 Real-time assurance
Because you’re working with accelerated delivery cycles, you can reassess your work every two to three
weeks. This means that results and insights are realized more quickly, feedback is faster, and teams can
immediately incorporate their findings into ongoing development phases.
“Chains of habit are too light to be felt until they are too
heavy to be broken.”
— Warren Buffet
Inexperience is to be expected
There’s going to be a learning curve any time an organization introduces something new, and agile auditing is
no different. It’s going to take time for everyone to become fluent in the language of agile audit.
9 Protiviti, 2019, Internal audit leaders adopt agile methods to meet next-gen audit expectations
Self-assess your own process to see where and how to tailor agile for fit.
Review the pilot, adjust the process, update your implementation plan
and go for it!
We hope that this eBook has given you an integrated look at how agile auditing might make sense for your
organization.
3 WAYS INTERNAL AUDIT CAN STRIKE A BALANCE BETWEEN PRODUCTIVITY & CONTROL
Internal audit must know how to respond when business process owners want to go faster and document less.
https://www.corporatecomplianceinsights.com/audit-business-process-documentation/
© 2022 Diligent Corporation. “Diligent” is a trademark of Diligent Corporation, registered in the US Patent and Trademark Office.
“Diligent Boards” and the Diligent logo are trademarks of Diligent Corporation. All third-party trademarks are the property of their
respective owners. All rights reserved.