PRESENTED BY MICHAEL PREMUZAK Project Governance – A Simple Secret to Providing it, Managing it, and Delivering it…..Every Time PRESENTED BY MICHAEL PREMUZAK

The Key Definition Project Governance The simple task of performing the critical tasks that make a project successful This is an Information Systems and Information Technology term because: 50 +% of Information Technology Projects Fail Unregulated project approval and sign-off processes seem to abound here Lack of focus on Risk Management and Security Lax attention to financial controls for the project and outcome Documentation, more specifically, the lack of it

Why Do You Need Project Governance? Sarbanes Oxley – C-SOX and generally good business practices Approvals and sign-offs Security Application or change meets management intentions Risk assessment to minimize impacts Fiscal controls Documentation and training Coordination of Resources Scheduling of resources, equipment, training, etc to make it go Control unplanned projects No more wildcard cowboy projects that do not follow protocols, scheduling activities and respect peoples lives Ensure Project go through a formal business case protocol with formal reviews, approvals, budgetary review, etc.

Why Do You Need Project Governance? Communication Leverage opportunities within the team Accountability becomes crystal clear Clearly defined project roles, expectations and timelines Standardized documentation of projects Common format for all project related activities Leverage older projects that fit your project The ability to look-back Project Control Projects are evaluated and run from a different perspectives, ROI model, cost, timing and political sensitivities

Key Components for Project Governance to be Relevant 1) Project Charter Clearly defined Scope Clear Accountabilities Clear Stakeholders, Sponsors and Chain of Reporting Defines how, the project will be reported and evaluated issues will be reported, escalated and ultimately resolved approvals will be created, performed and gathered project documents will be managed 2) Properly Staff the Project

Additional Definitions – can we ever agree ??!! Task – activities, both routine and non-routine that may have an impact on the environment, users or other business analysts and technical staff areas of responsibility. Task List – a tool that should be used to capture all items that affect other areas (Business and Technical), any outstanding vendor issues such as software development/enhancement, bug fixes, support requests, etc. Project - A process of tasks that produce something new or different that affects IS and the business by requiring: $$$ Resources Infrastructure and hardware changes Application training Process changes The above for a specified period of time. Change – the process of planning and communicating updates of the I.T. environment including hardware, software, applications and / or data. A change may be triggered by a task, it may also be from a project. “Project management is simply the process of planning for a change”

The Big Process

What is the Secret to Project Governance during the Project ? Identifying and paying close attention to the critical path – that is, what tasks do you absolutely “ have to do “ to have the project go –live ? ( This is what you internally focus on when reporting the status of a project to your stakeholders, steering committees, sponsors, champions, etc.) Lets go over an example: Something we can all relate too…or may have had some experience with Then once the project is live , simply retracing the non-critical incomplete steps and creating another critical path until complete “This is the simple secret of Project Management and Project governance and clearly differentiates the good project managers from the exceptional.”

Thank you Personal Contact Information Michael Premuzak premuzam@telus.net Currently contracting at Pengrowth and can be reached at 403-806-3292