WGITA Mission Statement and Work Plan / Project Plan Templates

1. WGITAMission Statement • and • Work Plan / Project Plan • Templates

2. WGITA Background • WGITA was created at the XIII INCOSAI in Berlin in 1989 to address SAI’s interests in the area of IT Audit. SAIs of 37 countries represents the Working Group as of today (January 2010). • WGITA fulfills its mission and mandate by implementing the triennial work plan which consists of the various goals and projects. • It is the dedication and effort of individual SAIs, who lead and support projects as project leaders and members, that make the WGITA work.

3. Review of WGITA Mission and Mandate

4. Mission and Mandate

5. Aim • Create and share best practices and methods in Information Technology (IT) related audits, and to facilitate the exchange of information and experience. • Promote partnerships among SAIs, and also between SAIs and academic/research institutions and international organizations with a view to enhancing professional capacities in IT Audit. • Disseminate guidelines and tool kits for development and adoption of professional standards. • Facilitate concurrent, joint and coordinated IT audits among SAIs. • Maintaining and enhancing database of Reference Material for IT Audit.

6. Organization

7. Roles and Responsibilities

8. Working Group Assembly

9. Chair and Secretariat Key Responsibilities: • Providing overall administrative support to all aspects of the WGITA • Convening annual WGITA meeting and triennial seminar as well as deciding the location and timing, in close cooperation with the host • Notifying the agenda of the meetings to the members

10. Chair and Secretariat .... • Leading liaison and relationship building with INTOSAI bodies and external organizations • Supporting training and capacity building initiatives • Communicating with the Regional Working Groups • Managing the authoring and publication of guidance • materials and other relevant material • Leading development of triennial work plan

11. Chair and Secretariat ....

12. Project Leads Key Responsibilities: • Preparing a project approval/initiation document for approval by the chair/assembly prior to beginning work. • Conceptualizing and executing the project • Providing a reporting schedule and deliverables • Preparing project specific work plans • Undertaking research and soliciting information from SAIs as needed

13. Project Leads • Assigning roles to and organizing workload among members • Contributing to, commenting on and approving draft and final guidance materials, work plans and other key documents and initiatives • Providing technical expertise and best practices in support of various projects • Review and comment on project work plans, progress reports and draft documents

14. Members Key Responsibilities: • Participating as Project leaders or members • Supporting the development of projects by providing SAI audit reports, answering questionnaires, reviewing and commenting on documents • Contributing to information exchange at meetings and participate in seminars • Hosting WGITA meetings and seminars • Maintaining and updating of WGITA Web-site and databases

15. Templates

16. Work Plan WORKPLAN PERIOD: insert start date (month, year) and end date (month, year) here DATE OF SUBMISSION: insert month, day and year here This work plan was approved by the WGITA Assembly Chair___________________________ Signature__________________________ Date_______________________________

17. Types of Templates

18. Project Approval Document Template Name of Project: Target Group: Approach: Issues to be covered: Deliverables Time Frame: Responsible SAI: Relevant contact:

19. Work Plan Template Section 1: Description of WGITA • WGITA background • WGITA organization • C. Previous accomplishments • D. Current projects

20. Work Plan Template Section 2: Description of Current Projects Project 1 <insert name of project> A. Project Goal and Rationale: B. Project Objectives: C. Reporting Schedule: 1. First Year 2. Mid Term 3. Final D. Project Team E. Contact information of Key personnel Position Name Address Telephone # Fax # E-mail

21. Work Plan Template Section 3: Implementation Plan Project Objective Activities Time Frame SAI Responsible

22. Work Plan Template Section 4: Planned Exchange Trips Trip No. Timeframe Purpose of Trip Location No. of travellers 1 2 3 4

23. Work Plan Template Section 5: Planned Collaboration with others Name of Organization: Planned Collaboration / Activities: Position: Name: Address: Telephone No: Fax No: E-mail:

24. Feedback from MembersSAI-Bhutan Mission Statement: “To support SAIs in enhancing knowledge and skills in the field of Information Technology related audits through exchange of information, experiences and best practices and encourage bilateral and regional cooperation amongst SAIs”

25. Feedback from MembersKuwait • Roles and Responsibilities: • Members: Contributing in suggesting new projects • Project Approval Document Template: • Adding a status field to indicate the status of the project (approved, pending, denied, etc.) and a comments field to list any additional notes related to the proposed project • WGITA Work Plan Template – Section 1: • Future project (not approved yet) part can be added to point to the coming project if exist. • WGITA Work Plan Template: • Identify priority projects and prepare a program of work for the next years by the work group.

26. Feedback from MembersSAI-Netherlands • Project Team Member Key Responsibilities • Actively contributing to the conceptualizing and executing of the project • Actively contributing to project deliverables • Actively contributing to specific work plans • Actively contributing to research and soliciting information from SAIs • Providing technical expertise and best practices to the project • WGITA Work Plan Template • Add Section 4 “Progress and Proposal”

27. Feedback from MembersSAI-Australia • Australian National Audit Office has made following suggestion on proposed template for Work Plan/Project Plan: • Including items on milestones and proposed costing in the template; • Supplementing the template with an overarching process flow/decision tree for establishing, executing and managing/monitoring each Plan;

28. Summing Up • Templates were kept simple • Minimal use of jargons • Not getting too much involved with inputs • Focus on deliverables

29. THANK YOU