Professional Documents
Culture Documents
Definition
To evaluate a project is to attempt to determine if the overall status of the work is acceptable in terms of intended value to the client once the job is finished. Project evaluation appraises the progress and performance of a job and compares it to what was originally planned. That evaluation provides the basis for management decisions on how to proceed with the project.
Resource Control
Resource Control is the process of managing all program resources, and their associated cost, according to the program management plan. It is the process of monitoring human resources to ensure that committed resources are made available to the program consistent with commitments, resources are allocated within the program according to the plan, and resources are released from the program as dictated by the plan.
Scope Control
Scope Control is the process for controlling changes to the program scope. This is a formal process for accomplishing the following tasks: Capturing requested changes Evaluating each requested change Deciding the disposition of each requested change Communicating a decision to impacted stakeholders Archiving the change request and its supporting detail When a request is accepted, initiating the activities required to have the change incorporated into the program management plan.
Schedule Control
Schedule Control is the process of ensuring that the program will produce its required deliverables and solutions on time. The activities in this process include tracking the actual start and finish of activities and milestones against the planned timeline, and updating the plan so that the comparison to the plan is always current. Schedule Control must work closely with the other program and portfolio control processes. It involves identifying not only slippages, but also opportunities.
Cost Control
Cost Control is the process of controlling changes to, and producing information from, the program budget. It is proactive, analyzing actual cost as incurred against the plan to identify variance from the plan, and, where possible, doing trend analysis to predict problem areas early. It is also reactive, dealing with unanticipated events or necessary but unplanned activities that affect the budget either negatively or positively. It is frequently thought of as merely holding down cost so that the program remains on budget, or bringing it back to budget when there is an overrun
Quality Control
It is the process of monitoring specific program deliverables and results to determine if they fulfill quality requirements. It identifies faulty outcomes and allows the elimination of causes of unsatisfactory performance at all stages of the quality loop, from the identification of needs to the assessment of whether the identified needs have been satisfied or not. It ensures that quality plans are executed at project levels, via quality reviews and project management health checks. it is performed throughout the program. Program results include both products and services, such as deliverables, management results, and cost and schedule performance
Communications Control
Communications Control is the process of managing communications to inform the stakeholders about the program and resolve issues of interest to them. The Communications Control Process ensures that policies and procedures are received, recorded, and routed to the intended recipients (through the Information Distribution Process). The scope and extent of this process is much wider at the program level than at the project level. Apart from the program sponsor, the other stakeholders involved in a program could include product managers, financial managers, and senior management personnel, especially those involved in strategic planning.
Performance Reporting
It is the process of consolidating performance data to provide stakeholders with information about how resources are being used to deliver program benefits. It aggregates all performance information across projects and non-project activity to provide a clear picture of the program performance as a whole. This information is conveyed to the stakeholders by means of the Information Distribution process to provide them with needed status and deliverable information. Additionally, this information is provided to stakeholders of the program and its constituent projects for the purpose of providing them with general and background information about the programs performance.
Close Program
Close Program is the process of formalizing the acceptance of the programs outcome by the sponsor or customer. However, administrative closure should not wait until the program has completed the execution process. Projects under the program need to be closed before the program is closed. As each project or each non-project activity closes, the Close Program Process should be performed to capture information and records, archive them, communicate the closure event and status, and obtain sponsor or customer sign-off.
Component Closure
Component Closure is the process of performing program management activities to close out a project or other non-project activity within the program. Program component closure deals with these closure issues at the program level, that is, it is informed by and performed at a higher level than normal project closure occurring at the project level. This process involves validating and ensuring that the project closure has indeed taken place at the project level.
Contract Closure
Contract Closure is the process of closing out a contract executed during the program and on behalf of the program, in accordance with the contracts terms and conditions. This process also applies to cases of premature contract termination. Contract Closure involves both product verification (i.e., verifying that the work was done) and the updating of all contract records. In the case of premature termination, it involves documentation of actual work performed plus work not performed, the circumstances that caused termination, and the updating of all contract records. Contract records are important and include the contract itself and other relevant documentation, such as progress reports, financial records, invoices, and payment records. These are often kept in a contract file, which should be part of the complete program file.
Project closure
All projects eventually end. Some end successfully, others end in disasters.
Some common reasons why projects end poorly are:
changing market conditions, lack of cooperation from clients, lack of management support, lack of resources, politics, technical problems, and poor management.