Albert Payne
CPMGT/303
June 29, 2015
Roy Wood
Introduction
We will look at the oversight in my organizations process in project management. Although we have certain processes and procedures in which we use I will incorporation project oversight in those areas. One process that stands out for my organization is called “Post Mortem”, this is a process that the executive branch uses on closure of projects or tasks. Post Mortem is where the manager of that department would documents issues with the process, how the ball was dropped, what process needs to be modified. This is oversight for use and is also consistent with oversight and lessons learned.
Project oversight can be defined as a set of principles and processes to guide and improve the management of projects (Larson, 2014). We all look at any oversight in a process rather it is a project or just a personal situation as the lingering boss watching over and checking our work for problems. Like your mom looking over everything you do and scrutinizing your process or behavior with corrective actions. In business this is generally the same concept for oversight, although you want to look at this as not a micro-management process but a process to improve the company’s way of doing its business. Project oversight will give my organization opinions or factual information to streamline your process and improve its overall delivery. It should be welcomed and as our companies has incorporated an Oversight Committee that will align with our PMO department. We look at Project Oversight as assistance and a means to improve business process or procedure which will result in making our department’s job easier.
Project oversight helps our organization due to it enables us to look at the current processes we have in place and how there implement. When the oversight of all projects is completed we have a meeting and assess what can be changed, what department dropped the ball, how can we