The document discusses project monitoring and control processes. It covers monitoring schedule, scope, cost, quality, risks, and the project team. Key aspects of control include collecting performance data, comparing to the baseline plan, identifying variances, and taking corrective actions. Control aims to keep the project on track by managing changes to the schedule, budget, and scope as needed based on project performance and risk assessments. Control processes are integrated across areas like scheduling, procurement, reporting, and configuration management to maintain overall project integration.
4. Project Control
• Monitor project process
– Collect and measure information
– Compare actual process with plans
– Assess trends and forecast
• Take preventive actions
• Take corrective actions
• Provide information for status reporting
www.projektor.ee/pm/#control
7. Schedule Control
• Determine the current status of the project
• Influence the factors that cause changes
• Identify schedule changes
• Evaluate change requests
• Manage change requests
– Plan changes
– Execute changes
www.projektor.ee/pm/#control
9. Baseline
Time baseline is a fixed schedule
which is used to measure the
performance of the project
The value or condition against
which all future measurements will
be compared
www.projektor.ee/pm/#control
10. Schedule Progress Data
• Actual start dates
• Actual finish dates
• Remaining duration for unfinished activities
• Calculating:
– Percent complete
– Schedule variance (SV)
– Schedule performance index (SPI = EV/PV)
www.projektor.ee/pm/#control
12. Slack
The amount of time that a task in
a project schedule can be delayed
without causing a delay in other
tasks or in project deadline
www.projektor.ee/pm/#control
18. Scope Verification and Control
Information
distribution
Project
execution
Procurement
management
Reporting
Team
development
Schedule
control
Scope
verification
Cost
control
Quality
control
Risk
monitoring
Change
management
Planning
Closing
www.projektor.ee/pm/#control
19. Scope*
Product Scope: The features and
functionalities that describe project
outcome
Project Scope: The work that needs to
be done to deliver a project outcome
www.projektor.ee/pm/#control
20. Scope Verification
Process for obtaining stakeholder’s formal
acceptance to the project scope and
deliverables
www.projektor.ee/pm/#control
21. Scope Control
Management of scope changes
• Avoiding scope changes
• Identifying scope changes
• Evaluating change requests
• Planning and executing changes
• Communicating changes
• Archiving
www.projektor.ee/pm/#control
22. Inputs:
- Project scope
statement
- WBS
- Project plan
- Performance reports
- Deliverables
Methods:
- Inspection
- Scope Change
control system
- Variance analysis
- Configuration
management system
Outputs
- Deliverables
- Change requests
- Corrective actions
- Plan updates
Scope Verification and Control
www.projektor.ee/pm/#control
23. Scope Inspection (Review)
• Measuring
• Examining
• Verifying
Does the project work and deliverables meet
acceptance criteria?
www.projektor.ee/pm/#control
24. Scope Change Control System
Procedures how the scope can be
changed (documentation, tracking,
approval procedures)
www.projektor.ee/pm/#control
28. Cost Control System
• Comparing actual costs with baseline costs
• Reflecting schedule and scope changes in the
budget
• Avoiding non-eligible expenses
• Change communication
• Bringing cost overruns within accepted limit
www.projektor.ee/pm/#control
29. Earned Value Method*
Method that measures
performance of the project and
forecast future performance based
on past performance
work completed ratio × budget price
www.projektor.ee/pm/#control
31. Cost Forecasting Method
• CPI - Cost Performance Index (CPI= EV/AC)
• ETC - Estimate to Complete - the remaining cost of
the project
• EAC - Estimate at Completion - the total cost of the
project at the end
www.projektor.ee/pm/#control
34. Quality Control VS Scope
Control*
Scope control is about accepting
the deliverables
Quality control is about meeting
the quality requirements specified
for the deliverables
www.projektor.ee/pm/#control
35. Inputs:
- Project plan
- Quality plan
- Quality metrics
- Quality criteria
- Performance
information
- Deliverables
Methods:
- Audits
- Process analysis
- Quality control tools
and techniques
Outputs
- Change requests
- Corrective actions
- Plan updates
- Lessons learned
Quality Control
www.projektor.ee/pm/#control
36. Quality Control Tools and Techniques
• Cause and effect diagrams
• Control charts
• Flow charts
• Histograms
• Pareto charts
• Run charts - trends
• Scatter diagrams
• Statistical sampling
• Inspections
• Defect repair reviews
www.projektor.ee/pm/#control
40. Risk Monitoring and Control
Information
distribution
Project
execution
Procurement
management
Reporting
Team
development
Schedule
control
Scope
verification
Cost
control
Quality
control
Risk
monitoring
Change
management
Planning
Closing
www.projektor.ee/pm/#control
41. Purpose of Risk Monitoring and Control
• Keeping track on identified risks
• Monitor new risks
• Executing risk response plans
• Evaluating risk response effectiveness
• Variance and trend analysis
www.projektor.ee/pm/#control
42. Inputs:
- Project plan
- Risk management
plan
- Risk register
- Performance
information
Methods:
- Risk audits
- Risk reassessment
- Variance and trend
analysis
- Technical and
performance
measurement
- Reserve analysis
- Status meetings
Outputs
- Risk register updates
- Change requests
- Corrective actions
- Preventive actions
- Plan changes
- Lessons learned
Risk Monitoring and Control
www.projektor.ee/pm/#control
43. Risk Register
• List of identified risks
• Risk owners
• Risk response plans
• Symptom and warning signs
• Residual and secondary risks
• Watch list of small risks
• Time and cost
www.projektor.ee/pm/#control
46. Team Development and Management
Information
distribution
Project
execution
Procurement
management
Reporting
Team
development
Schedule
control
Scope
verification
Cost
control
Quality
control
Risk
monitoring
Change
management
Planning
Closing
www.projektor.ee/pm/#control
47. Inputs:
- Staff assignments
- Staffing plan
- Resource
availability
- Roles and
responsibilities
- Org chart
- Performance
information
Methods:
- Management skills
- Training
- Team building
- Ground rules
- Co-location
- Recognitions and
reward
- Observations and
conversations
- Conflict
management
Outputs
- Team performance
assessment
- Issue log
- Change requests
- Corrective actions
- Preventive actions
- Plan updates
- Lessons learned
Team Development and
Management
www.projektor.ee/pm/#control
52. Team Building Activity Examples
• Ice breaking social games – e.g. Name ball
• Problem solving games – e.g. Tower building
• Mapping team members’ skills
• Creating the WBS
• WP0 activities
www.projektor.ee/pm/#control
53. Conflict Prevention Examples
• Set ground rules
• Set Group norms
• Solid PM practices
• Clear communication schedule
• Clear roles
www.projektor.ee/pm/#control
54. Conflict Solving Examples
• Discussion
• Written communication
• Mediation
• Compromise
• Voting
smallbusiness.chron.com/five-types-conflict-resolution-strategies-19251.html
56. Project Integration*
• Project integration with the main organisation
• Project process and outcome integration
• Integration of project processes and stages
• Project documentation integration
www.projektor.ee/pm/#control
59. Change Management
Is needed because projects
seldom run exactly according to
the project management plan
www.projektor.ee/pm/#control
60. Change Management
• Identifying needs for changes
• Documenting change requests
• Reviewing and approving/rejecting requests, corrective and
preventive actions
• Managing approved changes and actions
• Updating the scope, quality, budget and schedule based on
approved changes
• Maintaining the integrity of baselines
• Documenting impact of changes
• Validating defect repair
• Controlling project quality
www.projektor.ee/pm/#control
61. Project Management
Methodology
Process that aids a project
management team in monitoring
and controlling the project work
according to the project plan
www.projektor.ee/pm/#control
62. Project Management
Information System
An automated system that is used
to monitor, control and forecast
the execution of project activities
www.projektor.ee/pm/#control
63. Configuration Management System
Change Control Process
• Identify changes
• Assess the effectiveness of those changes
• Continuously improve the project
• Communicate changes to the stakeholders
• Configuration identification
• Configuration status reporting
• Configuration verification and auditingwww.projektor.ee/pm/#control
64. Expert Judges
• Other departments
• Consultants
• Customers
• Sponsors
• Professional associations
• Professional networks
• Stakeholders
www.projektor.ee/pm/#control
Identifying, evaluating change requests, planning and executing changes
SOW - Statement of Work
Project has 3 baselines: Schedule, cost, scope
Approved
Investigating what is the clients opinion
AKA Review, Audit, Walkthrough
SOW - Statement of Work
Exercises based on equations:
- ETC based on new estimate
- ETC based on Atypical variance ETC = BAC - EVC
- ETC based on typical variance ETC = (BAC - EVC)/CPIC
- EAC using a new estimate EAC = ACC + ETC
- EAC using remaining budget: EAC = ACC + BAC - EV
- EAC using CPIC: EAC = ACC + (BAC – EV)/CPIC
BAC: Budget at completion
SOW - Statement of Work
SOW - Statement of Work
SOW - Statement of Work
Interpersonal skills, Soft skills.
Rules – e.g. how commands will be given?
Conflicts arise due the lack of communication
Change Control
Change Control
SOW - Statement of Work
Plans are made for changes
Different stakeholders make change proposals (requests)
Project team has to reject or accept requests according to the project scope and customer needs.