30 minutes introduction to Project Auditing Project Management & Project Audits.

Slides:



Advertisements
Similar presentations
Program Management Office (PMO) Design
Advertisements

Roadmap for Sourcing Decision Review Board (DRB)
Project Managing a PH D And surviving the process Paul Hyland.
Project Management Framework May 2010 Ciaran Whyte Risk Administrator Planning & Strategic Projects Unit.
1 LaCrosse PMI Chapter Meeting A discussion about the Introduction of PM within your business 4/20/2011 Jim Strong Mayo Clinic DLMP PMO Director.
W5HH Principle As applied to Software Projects
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Introduction to Project Management Avneet Mathur
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Author:Prof.Dr.Tomas Ganiron Jr1 CHAPTER 7 PROJECT EXECUTION, MONITOR & CONTROL PROCESS 7-1 Project Executing process 7-2What is Project monitor & control.
10.5 Report Performance The process of collecting and distributing performance information, including status reports, progress measurements and forecasts.
Project Management Basics
Lesson 10: IT Project and Program Management. Lesson 10 Objectives  Identify resources for technical data  Identify project management fundamentals.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
Project Closeout and Termination Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 14 Learning Objectives After completing.
System Analysis and Project Management Key terms and definitions Presentation.
Project Management: Madness or Mayhem
PMP® Exam Preparation Course
HIT241 - RISK MANAGEMENT Introduction
Process for Analysis  Choose a standard / type  Qualitative / Quantitative Or  Formal / Informal  Select access controls  Match outcome to project.
Week 6: Project Management E1102 – Design Fundamental Using Advanced Computer Technologies Spring 2010.
Lecture 4 Title: The Scope Management Plan
Information Technology Project Management by Jack T. Marchewka Power Point Slides by Jack T. Marchewka, Northern Illinois University Copyright 2006 John.
Basic of Project and Project Management Presentation.
SacProNet An Overview of Project Management Techniques.
Project Management: Tips and Tools ITS Project Management Office/K. Kyzer, A. Shoop Nov. 15, 2012.
Pre-Project Components
Core Banking Transformation: A Roadmap to a Successful Core Banking Product Implementation - PMI Virtual Library | | © 2008 Kannan S. Ramakrishnan.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
Project Management Process
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
ITS PMO Framework Enhancing Stakeholder Engagement & Cross Functional Transparency Jimmy Goyal June
Chapter 11 Project Management.
Project Management for Treasury Professionals
Managing and Defining Scope
IF 3507 Manajemen Proyek Perangkat Lunak
Scope Planning.
Unit 1 What is Project Management
Systems Analysis and Design in a Changing World, 4th Edition
Gap Analysis Continuing the development of the strategy
Project Management Processes
Presented To: 3rd Annual CMMI Technology Conference and User Group
Chapter 5: Project Scope Management
Project Management.
PROJECT SCOPE MANAGEMENT
Introduction to Project Management Avneet Mathur
Description of Revision
Defining the Activities
CMMI – Staged Representation
Project success and failure factors
Engineering Processes
Scope management Chapter 5 Copyright ©2016 Pearson Education, Inc.
[Project Name] STEERING COMMITTEE UPDATE [Date]
Information Technology Project Management
CIS12-3 IT Project Management
Project closeout and termination
Project Management Process Groups
Project Management Processes
Project Management Chapter 11.
PROJECT SCOPE MANAGEMENT
Project Management Group
Lesson 10: IT Project and Program Management
Project Overview.
Executive Project Kickoff
{Project Name} Organizational Chart, Roles and Responsibilities
Data Security and Protection Toolkit Assurance 2018/19
KEC Dhapakhel Lalitpur
Risk Analysis Objectives Discuss the importance of Risk Analysis
Presentation transcript:

30 minutes introduction to Project Auditing Project Management & Project Audits.

2 PRINCE 2 : Directing a Project

3 Agenda for today :  How do we define an Audit?  What we don’t Audit  Common Project Failures  Tools and Techniques  SAMARA  Conclusion

4 How do we define an Audit  A project management Audit is a formal health check and report on the state of an identified project at a particular point in time. It consists of:  WBS verification and integrity  Risk identification and mitigation  Measurement of Risk impact  Compliancy check against accepted norms.  The Audit should also verify the usage of PM tools and techniques.  Note that it is the project that is being Audited, not the Company!

5 How do we define an Audit (2) We will Audit the project on (1):  The project Work Breakdown Structure and it’s relevance  Risk identification, costs, levels and severity  The mitigation measures and costs  The impact of the risk and remanance  Progress vs. Objectives (independent appraisal using MS project) We will Audit the project on (2):  A 300-point “key Criteria” questionnaire on project compliance  Individual questionnaires at detail level  Work Package / major Task budgets and Costs  Project Governance  Management Deliverables.

6 Not included in the Audit - Business appraisals Financial Audit Technical appraisals of the work itself People - although could be identified as risks, etc. Vendor control – other than at a project level Activity outside of the project scope.

7 Common Project Failures No project governance or systemic management of the project No or inadequate risk assessment or analysis Poor budgeting and contingency planning Resource shortages, or inadequate project resourcing No project stage definitions, with closures and sign off No or inadequate issue identification, tracking, escalation and resolution Quality definitions, IKOs, KPIs, milestones and deliverables not clear Customer expectations not established or managed Actions not managed, logged, tracked, and escalated to resolution No or inadequate financial incentives on the project team Business cases, Project Mandates, management demands badly expressed Return on Investment (ROI) not compared with TCO – Total Cost of Ownership Suppliers not subject to adequate vendor control And many more !

8 Reasons to have Audits. Audits may be one-off events or regular occurrences. They can be called for a variety of reasons, such as; Project already “in the red” Dead-lines missed, budget over-runs, high material losses, staff issues. Independent appraisals of true project status – “benchmarking” Assist the Project Manager or sponsor to get objective clarity Determine contingency requirements Analysis of risk and plan the mitigation of the risk Present the project status to Management in a clear and non-technical manner.

9 Tools and Techniques of the Audit. PRINCE II – the chosen methodology SAMARA – System for Audit Management and Risk Assessment MS project – for typical project plans – CPA, achievement v deadlines Interviews with key staff. Issue Log, Risk Log, Action Log – create or verify. Project Walk-throughs. Application of experience Powerpoint Presentation software.

10 Samara Screen Dumps - Project Information -

11 Samara Screen Dumps - WBS Levels -

12 Samara Screen Dumps - WBS Entries -

13 Samara Screen Dumps - Risks -

14 Samara Screen Dumps - Mitigations -

15 Samara Screen Dumps - Stages -

16 Contacts - For further information, call Quantum Business Partners Or