The auditing of projects and interfaces workstreams
Continuing on with my monthly description of the different workstreams within the Assurance SIG; the last (but not least) two workstreams are the Auditing of Projects and Interfaces workstreams.
Some types of assurance activities tends to be well-defined (e.g. safety assurance) but many (most?) are not. Project Auditing, in particular, is not well defined generally. We know that it isnt just checking compliance against standards and procedures, but if an organisation is to audit projects consistently (and effectively), how should it go about it?
In 2010, the Auditing workstream developed a guidance paper on project auditing for the Chartered Institute of Internal Auditors (CIIA), entitled: An introduction to projects and project auditing, and this has now been published by them as their definitive guidance on the topic.
The workstream are now developing a Guide to Project Auditing, which will cover approaches, methods and the required skills, knowledge and experience of the auditor.
If you have any suggestions and/or queries or want to get involved, we would love to hear from you. Feel free to contact us directly or add a comment below.Tweet
Share this page
Login or Register to leave a comment:
Agile refuses to analyse requirements beforehand – and thus declines to provide an initial certainty. This will probably always scare any stakeholder trying to understand whether or not they can show results to the board with the budget that they are granted.
You have a choice. You can either muddle on, stand firm and fix it – or look elsewhere.