Project Monitoring and Control Autosaved
Project Monitoring and Control Autosaved
Project Monitoring and Control Autosaved
Introduction
Once the project plan has been approved, the plan is executed. The team needs to be aware of what needs to be done and achievements for each team member agreed. The progress of the project needs to be monitored and any aspects not going as required addressed. This is the purpose of monitoring and control. Measurements are usually effected against the plan
Introduction
bases for selection dictate what to monitor plans identify elements to control
and reporting of information Control uses monitored information to align actual performance with the plan
Plan-Monitor-Control Cycle
Closed loop process Planning-monitoring-controlling effort often minimized to spend time on the real work
Identify special characteristics of performance, cost, and time that need to be controlled
performance characteristics should be set for each level of detail in the project
Formats of Data
Frequency Counts Raw Numbers Subjective Numeric Ratings Indicators and Surrogates Verbal Characterizations
Data Analysis
Aggregation Techniques Fitting Statistical Distributions Curve Fitting Quality Management Techniques
Reporting
Reports
Not all stakeholders need to receive same information Impact of Electronic Media Relationship between projects information system and overall organizations information system
Report Types
Meetings
Earned Value
Percent of tasks budget actually spent not good indicator of percent completion
50-50
50% complete when task started and other 50% added when task finished 100% complete when finished and zero percent before that
100%
PROJECT CONTROL
Background
Acts which seek to reduce differences between plan and actuality Difficult Task
Purposes of Control
Purpose is to correct errors, not punish the guilty Investments in control subject to diminishing returns Must consider impact on creativity and innovation Be careful not emphasize short-run results at the expense of long-run objectives Dangers of across the board cuts
Go/No-Go Controls
predetermined standard must be met for permission to be granted to continue done after project completed purpose is to allow future projects to learn from past project experience
Post-Control
Trend Projection
Scope Creep
Coping with changes frequently cited by PMs as the single most important problem Common Reasons for Change Requests
Review all requested changes Identify impact of change Evaluate advantages and disadvantages of requested change Install process so that individual with authority may accept or reject changes
Communicate change to concerned parties Ensure changes implemented properly Prepare reports that summarize changes made to date and their impact
Include in contract change control system Require all changes be introduced by a change order Require approval in writing by the clients agent and senior management Consult with PM prior to preparation of change order Amend master plan to reflect changes