Study guide

6.1 Agile, Traditional, Integrated, and Remote Approaches

CIA Part 2 Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CIA Part 2 Exam Orientation

1.1 Current CIA Part 2 Exam Facts 1.2 Eligibility, Fees, and Pearson VUE Scheduling 1.3 Scoring, Results Timing, and the 2025 Syllabus Map

2 Chapter 2: Engagement Objectives and Scope

2.1 Topical Requirements in Objectives and Scope 2.2 Elements Used to Build Engagement Objectives 2.3 Scope Limitations, Stakeholder Requests, and Scope Changes

3 Chapter 3: Evaluation Criteria and Planning Context

3.1 Selecting and Testing Evaluation Criteria 3.2 Applying Topical Requirements When Planning 3.3 Strategy, Risk Management, and Performance of the Activity Under Review

4 Chapter 4: Technology, Continuity, and Finance in Planning

4.1 Cybersecurity, IT General Controls, Privacy, and Data Security 4.2 Business Continuity, Disaster Recovery, and Resilience 4.3 Finance and Accounting Concepts for the Activity Under Review

5 Chapter 5: Business Process and System Risks in Planning

5.1 Asset, Supply Chain, Inventory, Payables, Procurement, and Compliance Processes 5.2 Third-Party Process Risks 5.3 CRM, ERP, and GRC System Risks

6 Chapter 6: Engagement Approach and Project Management

6.1 Agile, Traditional, Integrated, and Remote Approaches 6.2 Project Management While Planning and Conducting Engagements

7 Chapter 7: Engagement Risk Assessment

7.1 Topical Requirements and Pervasive Financial, Operational, IT, Cyber, and Regulatory Risks 7.2 Emerging Risks and the Impact of Change 7.3 Methods to Evaluate and Prioritize Risks and Controls

8 Chapter 8: Structure, Environment, and Culture

8.1 Centralized vs Decentralized, Flat vs Traditional, In-Person vs Remote 8.2 Culture, Group Behavior, and Tone at the Top

9 Chapter 9: Control Design, Effectiveness, and Efficiency Procedures

9.1 Procedures to Evaluate Control Design 9.2 Procedures to Test Operating Effectiveness 9.3 Procedures to Test Control Efficiency

10 Chapter 10: Work Programs, Testing Methodologies, and Resources

10.1 Evaluating Adequacy of the Engagement Work Program 10.2 Testing Methodologies for Accounting, Finance, IT, Operations, and Cybersecurity 10.3 Financial, Human, and Technological Resources and Limitation Implications

11 Chapter 11: Information Sources and Preliminary Survey

11.1 Interviews, Observations, and Walk-Throughs 11.2 Data Analysis as an Information Source 11.3 Policies, Checklists, Risk-and-Control Questionnaires, and Self-Assessments

12 Chapter 12: Evidence Relevance, Sufficiency, and Reliability

12.1 Criteria for Evidence Quality 12.2 Independence, Corroboration, and the Control Environment 12.3 Evidence an Informed, Competent Person Could Rely On

13 Chapter 13: Technology Options for Findings and Conclusions

13.1 Artificial Intelligence, Machine Learning, and Robotic Process Automation 13.2 Continuous Monitoring, Dashboards, and Embedded Audit Modules

14 Chapter 14: Process Mapping and Data Analytics

14.1 Workflow Segments, Process Maps, Walk-Throughs, and RACI 14.2 Structured vs Unstructured Data and the Analytics Process 14.3 Diagnostic, Prescriptive, Predictive, Anomaly, and Text Analysis

15 Chapter 15: Analytical Review and Finding Evaluation

15.1 Ratios, Variances, Trends, and Benchmarking 15.2 Selecting Analytical Techniques for Engagement Objectives 15.3 Comparing Existing Conditions to Evaluation Criteria 15.4 Root Causes, Effects, and Significance of Findings

16 Chapter 16: Workpapers and Engagement Conclusions

16.1 Organizing Complete Workpapers with Sufficient Evidence 16.2 Linking Workpapers to Results; Retention, Regulation, and Policy 16.3 Aggregating Findings and Concluding on Governance, Risk, and Control

17 Chapter 17: Engagement Supervision

17.1 Supervision Throughout Planning and Fieldwork 17.2 Coordinating Assignments and Reviewing Workpapers and Conclusions 17.3 Evaluating Auditors' Performance

18 Chapter 18: Communication During the Engagement

18.1 Formal and Informal Communication Across Planning, Fieldwork, and Reporting 18.2 Situations That Require Escalation 18.3 Selecting Appropriate Stakeholders for Engagement Communication

19 Chapter 19: Final Review and Test Day

19.1 2025 vs 2019 Traps and Part 2 vs Part 3 Boundaries 19.2 Pacing, Test-Center Rules, and Official Results

6.1 Agile, Traditional, Integrated, and Remote Approaches

Key Takeaways Explain This Topic AI

CIA Part 2 A4 requires evaluating traditional, agile, integrated, and remote approaches against this engagement's objectives, evidence needs, and disruption — not against software-development fashion

Traditional engagements are sequential (planning → fieldwork → reporting) with relatively stable scope and a heavier work program written before substantive testing

Agile uses sprints, a backlog of audit questions, and frequent checkpoints, but GIAS still requires documented objectives, criteria, a work program, and retainable evidence

Integrated work combines operational, financial, IT, and/or compliance objectives and specialists in one engagement to cut duplicate client burden and catch interface risks

Remote client auditing (video walk-throughs, data extracts, screen-shares) is a valid engagement approach with limits on physical observation; it is not IIA exam remote testing, which is not offered

Last updated: October 2026

6.1 Agile, Traditional, Integrated, and Remote Approaches

Quick Answer: CIA Part 2 A4 asks you to evaluate agile, traditional, integrated, and remote approaches and pick the one that can produce sufficient, reliable evidence for this engagement's objectives. These are internal audit engagement designs, not software-development religions. Agile does not waive a work program or evaluation criteria. Remote auditing of a client remains valid; the CIA exam itself is Pearson VUE test-center only (there is no OnVUE remote testing).

CIA Part 2 Section A is Engagement Planning (50%) . Official objective A4 is: evaluate various approaches such as agile, traditional, integrated, and remote auditing to determine the most suitable approach. That is a Global Internal Audit Standards (GIAS) Domain V skill — Principle 13, Plan Engagements Effectively — especially Standard 13.6 Work Program and the evidence duties in Principle 14, Conduct Engagement Work . It is not a Part 3 item about how the chief audit executive (CAE) builds the annual plan, and it is not a question about where you sit the CIA.

The exam trap is treating “approach” as a branding choice. Approach is a planning control . It decides how you sequence work, who sits in the room, how you obtain evidence, and how much you disrupt the activity under review. If the approach cannot support the objectives and criteria you already set (Chapters 2–3), it is the wrong approach — even if it is fashionable.

Why approach selection is a planning decision

You do not pick agile because the shop bought a Kanban board, or remote because travel is expensive, and then reverse-engineer objectives. The testable sequence is:

Objectives, scope, and criteria — what must be true, and how you will know.

Risks of the activity and of the engagement itself — who, where, what evidence.

Approach that can gather that evidence with acceptable disruption and specialist mix.

Work program, hours, and a supervision path that match the approach.

Every approach still requires documented objectives, evaluation criteria, a work program that can achieve the objectives, evidence that is relevant, sufficient, and reliable, and supervision that starts in planning. The approach changes how you satisfy GIAS. It does not change whether you satisfy GIAS.

Traditional (sequential) engagements

Traditional internal audit engagements are sequential: planning → fieldwork → reporting . Scope is relatively stable . The work program is written up front in more detail: populations, samples, tests, and evidence requests are designed before you spend significant time in the activity.

Use traditional when the process is mature and criteria are known (policy, statute, signed service-level agreement), when you need a complete, comparable sample before you conclude (for example, a full-period three-way-match test), when stakeholders expect a single, well-scoped visit rather than a series of sprints, or when this is first-time coverage and you must map the process before testing. Traditional is not “old-fashioned.” It is the right tool when stability of scope and completeness of a planned sample matter more than early, partial insight.

The cost of the design is real. Issues found late in fieldwork can force rework, and a frozen program is slow when the activity is changing underneath you.

Traditional feature What it looks like on an engagement When it fails

Sequential phases Kickoff and program approved before substantive testing The ERP cutover happens in week two and the program still tests the retired system

Stable scope In-scope period, locations, and systems named in planning Management keeps adding “while you are here” requests without change control

Heavy upfront program Tests, samples, and request lists designed before fieldwork You cannot design tests yet because the process is still being redesigned

Single reporting cycle Findings discussed near the end, then one engagement communication Stakeholders needed a control gap raised in week one, not week six

Agile engagements

Agile internal auditing uses iterative sprints , a backlog of audit questions , and frequent stakeholder checkpoints . A sprint might be one or two weeks: pull a slice of the backlog, perform tests, share interim results with the process owner and the supervisor, and refine the next slice. The backlog is a prioritized list of audit questions and tests mapped to engagement objectives — not a software product-development story list, and not a parking lot of stakeholder complaints.

What agile is not : an excuse to skip a work program, criteria, or documentation; a plan to “figure out objectives after we see what we find”; daily stand-ups instead of supervision; or permission to issue findings against unagreed criteria because a sprint ended.

GIAS still applies. Standard 13.6 requires a work program that achieves the engagement objectives. In an agile engagement the program is living : you update tests as sprints reveal process reality, and you document those updates . You still lock objectives and criteria at the start (they change only through the Chapter 2 change-control path). You still retain evidence a competent person could re-perform. You still have a supervisor who reviews planning, not only the last sprint demo.

Agile fits when uncertainty is high: a digital product that changes every release, a shared-service migration, a control environment you cannot map from last year’s walk-through. Early checkpoints reduce the risk that you spend six weeks testing a process that no longer exists. Agile does not fit when a regulator or statute requires a complete, pre-defined sample over a closed period and partial sprint results would be misleading as a conclusion.

  • Agile practice GIAS-safe version Exam trap version
  • Sprints Time-boxed slices of the approved program Random tests with no link to objectives
  • Backlog Prioritized audit questions mapped to criteria A parking lot of stakeholder complaints

Checkpoints Interim findings and program updates with the supervisor and process owner Informal chats that never hit the file

  • Flexibility Documented program changes Silent scope creep or silent scope shrink
  • Integrated engagements

An integrated engagement combines operational, financial, IT, and compliance objectives — and the specialists who can test them — in one engagement of the same activity. The point is not a longer report. The point is to avoid duplicate client burden (three opening meetings, three request lists, three weeks of the same accounts-payable manager walking through the same invoice) and to catch interface risks that single-domain audits miss.

Interface examples the exam likes:

IT access provisioning versus financial close: a terminated user still posts journals.

Third-party service-level agreement versus operational performance versus privacy: the vendor meets uptime and leaks data.

Procurement compliance versus inventory existence versus ERP three-way match: a clean match on a receipt that never hit the dock.

Integration is a team and objective design , not a slogan. If the IT specialist runs a separate project with a separate scope and never reads the operational tests, you have four audits wearing one kickoff slide. Plan a single request list, a shared process map, joint walk-throughs, and tests that explicitly address hand-offs. Specialist mix is a decision factor here. Hours and competency gaps you cannot cover are a Chapter 10 resource issue — raise them in planning rather than pretending the “integrated” label supplies a missing skill.

Integrated work is usually the right default for ERP-centric processes (order-to-cash, procure-to-pay, hire-to-retire) where financial, operational, and IT general-control risks share the same system. It is the wrong default when combining topics would dilute a required deep dive — for example, a cybersecurity Topical Requirement engagement that needs dedicated scope, not a few IT questions tacked onto an accounts-payable audit.

Remote and hybrid engagements

Remote auditing obtains evidence without the team sitting in the client’s facility: video walk-throughs , data extracts , screen-shares , secure file transfer, and interviews by video or phone. Hybrid means some procedures on-site and some remote — counts and culture on-site; configuration extracts remote.

Remote is a valid engagement approach for clients in 2026. Do not confuse it with how you sit the CIA . The IIA does not offer OnVUE / online testing . Part 2 is delivered at a Pearson VUE test center only . A question about “remote” on this exam is about auditing the activity , not about your appointment.

Remote strengths: multi-site coverage without travel days, faster access to ERP logs and data warehouses, less disruption of a busy operations floor, and the ability to involve a specialist who cannot fly. Remote limitations you must plan around:

Physical observation — you cannot watch the dock, the cage, or the cash drawer the same way.

Inventory and existence — screen-share of a spreadsheet is not a floor-to-sheet count.

Site culture and tone — cameras show the meeting, not the hallway.

Unannounced procedures — hard to surprise a count you scheduled on a video call.

Evidence authenticity — confirm extract source, completeness (row counts, control totals), and that the screen-share is the production system, not a demo company.

If existence, physical access, or culture is essential to the objective, remote-only is the wrong approach. Hybrid is often the adult answer: travel for the count; pull the logs from home.

Decision factors

The syllabus wants a reasoned choice , not a favorite methodology. Walk the same six factors every time.

Decision factor Pushes toward… Pushes away from…

Risk (what could be wrong, and how you must prove it) On-site or hybrid when existence or physical control is in scope; integrated when interface failure is the story Remote-only inventory; single-domain testing of an ERP process

Location Remote or hybrid for many sites or restricted facilities A six-week traditional stay at headquarters when the risk is in three plants

System access Remote extracts when production access and logging are mature Remote when you cannot obtain complete, attributable data

Specialist mix Integrated team with IT or compliance in the same kickoff Agile sprints that assume a specialist who is not allocated

Client disruption Agile checkpoints or remote extracts instead of a long on-site occupation Three sequential audits of the same manager

Evidence quality Whatever approach can make evidence relevant, sufficient, and reliable Any label that cannot support Principle 14

Worked pattern. A three-plant inventory existence review with a weak warehouse culture and an ERP that can dump complete perpetual records. Risk and evidence quality demand on-site counts . Location argues hybrid (travel to plants; extracts for perpetual-to-floor reconciling items). Specialist mix may add an IT auditor for perpetual-record completeness. Disruption argues a short, well-notified count window — not a six-week traditional occupancy, and not a remote-only “count.” Agile sprints could sequence plant 1 then plant 2 if you update the program, but you still need a complete count program, not a backlog of optional visits.

Combining approaches and the documentation bar

Real engagements mix labels: integrated + hybrid + traditional program , or integrated + agile sprints on a transformation. The file must still answer four questions: What is in scope? What criteria will we use? What approach will obtain the evidence? What work program implements that approach? If those four sentences are missing, the methodology brand will not save the engagement — or the exam item.

The testable rule is always: objectives and criteria first, approach second, GIAS documentation in every case. Fashion is not a planning control.

Loading diagram... Selecting an engagement approach (CIA Part 2 A4)

Illustrative evidence-quality concern if the approach is a poor fit (higher = more residual concern)