BUS 361 Study Guide - Standard Operating Procedure, Project Plan, Project Management
Chapter 12: Managing project Control and Closure
What is Project Control:
•Project Control: the process of monitoring and measuring project
process and influencing the plan to account for any discrepancies
between planned and actual progress.
What is Project Closure
•Project Closure: Involves the final implementation and training
related to the project, getting acceptance and signing off on the project
and archiving of the project results.
•Gain approval from stakeholders that delived product meets their
requirements and fulfills contract. Write end report and document
lessons learned and unresolved issues.
The importance and Philosophies of Project Control and
Why is project control important?
•Controlling processes important in : integration, scope, time, cost,
quality and risk
•Successful outcomes of any project require control at every stage of
Philosophies of controlling projects
•A philosophy of project control: management style the manager
employs in following a plan and dealing with problems or changes that
oDogmatic philosophy : little or no tolerance for deviation from
plan, autocratic to maintain adherence to plan
oLaid Back philosophy : embrace the multiple changes or
problems that arise.
oPragmatic philosophy : combination of both
•Usage depends on size of project
Levers from controlling projects
•Communication, required in successfully control a project quality of
•Participation , to offer opinions and to take responsibility when
•Analysis and Action , longer problem persists, more costly and difficult
•Commitment, from stakeholders; feel greater responsibility and
accountability for their role in project; ability of PM to get commitment
from team is related to leadership style and influence
Why is the Project Closure Important?
•Includes training end users and other organizational members on the
use of the item
•Documentation and archiving helps prevent repeated mistakes and
concentrate on other issues and provides org with knowledge transfer
on how to approach such issues in future
Techniques for Managing Project Control
Standard Operating Procedures
•Standard Operating Procedures: are activities and reporting
methods instituted during the course of the project to monitor its
progress and to provide reports for project managers and stakeholders.
•Regularly scheduled meetings, maintained logs, distributed reports
•Project log: a technique for controlling a project that includes
recording information such as changes requested by client, completion
dates and deliverables.
Monitor and Control Project Work
•Monitor and Control Project Work: the process of collecting,
measuring, and disseminating information related to performance, as
well as assessing measurements and trends in order to make many
•Inputs include the project-managing plan, work performance
information and rejected change requests.
•Project management Methodology: the process that helps the
project team monitor and control the work being performed in
accordance to the project management plan
•Objective is to establish clear guidelines and methods to ensure that
projects are being conducted in a consistent manner, such that quality
is promoted and the project deliverables are delivered on time and
•Earned value management: a technique that measures project
performance over time, and provides a way to forecast future
performances based on past performance.
•Output from the techniques listed in monitor and control project work
include recommended corrective actions, recommended preventative
actions, forecasts, recommended defective repairs and requested
•Recommended corrective actions: documented recommendations
needed to bring future project performance into conformance with the
project management plan
•Recommended preventative actions: documented
recommendations that minimize the probability of negative
consequesnces to the project
•Forecasts: estimates or predictions of conditions or events in the
Integrated Change Control
•Integrated Change Control: the process of identifying, evaluating
and managing changes that occur from project initiation through
•Approved change requests: documented and authorized changes
that are scheduled for implementation by the project team
•Rejected change requests: requested changes that were not chosen