Agile Governance and Audit: An overview for auditors and agile teams

By Christopher Wright

Written in an engaging and entertaining style, Agile Governance and Audit serves as an ideal introduction for auditors and risk managers. 

Many auditors are now encountering Agile management methodologies for the first time. This can cause problems for the audit process because the methodology is very different from traditional project approaches. Aside from the difficulties faced by the auditor, an ineffective audit can have a negative effect on an Agile project and might even harm the final outcome. 

What you’ll find inside this book: 

• Hints and tips for auditors 


• A selection of case studies illustrating the practical issues involved in auditing Agile projects 


• Helpful and practical guidance for Agile teams preparing for forthcoming project audits 

An ideal book for auditors encountering Agile and Agile teams preparing for a management audit.

• Language: English
• Publisher: itgovernance
• Release date: Jun 19, 2014
• ISBN: 9781849285896

Christopher Wright

Chris Wright is a qualified accountant and Certified Information Systems Auditor (CISA) with over 30 years’ experience providing financial and IT advisory and risk management services. He worked for 16 years at KPMG, where he managed a number of IT due diligence reviews and was head of information risk training in the UK. He has also worked in a wide range of industry sectors including oil and gas, small and medium enterprises, public sector, aviation and travel. 

Book preview

Resources

CHAPTER 1: INTRODUCTION TO AGILE

Overview

Before we consider Agile governance and audit we need a common understanding of the history of Agile and how it is defined. The dictionary definition of Agile is ‘nimble, mentally quick or acute’. The thesaurus adds words such as active, lively, prompt, quick, sharp and sprightly. These are not words usually associated with IT programmes and projects!

Many organisations have their own terminology and definitions – of varying accuracy and validity. This also causes some confusion, so throughout this book I rely upon the following widely accepted structures:

Agile definition

Agile Manifesto

Agile