IT Project Management
Tutorial 11: Monitoring and Controlling Processes
– Project Integration Management
– Project Scope Management
– Project Time Management
– Project Cost Management
– Project Quality Management
– Project HR Management
– Project Communications Management
– Project Risk Management
– Project Procurement Management
Objectives:
1. Explain the purpose of monitoring and controlling in project management
2. Describe the tasks and outputs of monitoring and control in the 9 project
management knowledge areas
Students are encouraged to prepare their draft answer before class, as this will help
them to discuss the questions and answers during the tutorial session.
1. Using the template below, describe the key monitoring and controlling
processes and outputs of these processes for the project management
knowledge areas indicated.
Integrated change Approved change requests,
control corrective actions, preventive
actions and defect repair
Rejected change requests
Project management plan
(updates)
10608647.doc Page: 1 of 5
AY0809 October Semester
Project scope statement (updates)
Validated defect repair
Deliverables
10608647.doc Page: 2 of 5
AY0809 October Semester
Quality baseline (updates)
Recommended corrective actions,
preventive actions and defect
repairs
Requested changes
Organizational process assets
(updates)
Project management plan
Project HR Requested changes
Management Recommended corrective actions,
preventive actions and defect
repairs
Organizational process assets
(updates)
Project management plan
(updates)
Manage stakeholder Resolved issues
Approved change requests and
corrective actions
Organizational process assets
(updates)
10608647.doc Page: 3 of 5
AY0809 October Semester
2. What are the 3 main objectives of integrated change control?
3 main objectives of integrated change control are:
Influencing the factors that cause changes to ensure that changes are beneficial
Determining that a change has occurred
Managing actual changes as they occur
3. The methodology used in your organization calls for change requests to be
considered by a change control board (CCB). After some reflection and a
discussion with the programmer, you have decided to submit a change request
to the CCB to add the new features mentioned above.
In your presentation to the CCB, what reason might you give for the change
request and what things should you take into consideration?
Changes may be needed for a variety of reasons, such as an incomplete initial scope,
new legal requirements, organization changes etc
In this case, the reason given could be a desire to have the system do more than was
in the original scope agreement
Your justification should include an analysis of the impact upon the organization and
the project:
Will developing the new features adversely impact the project budget, schedule,
or quality?
What is the impact upon customer expectations?
Will it increase ongoing operational costs?
4. Why is it important to keep the risk register up to date?
10608647.doc Page: 4 of 5
AY0809 October Semester
Risks change as the project progresses
Other information in the risk register may also change e.g. probability, person
assigned to address the risk etc
It is important to keep the risk register up to date to make sure you are
addressing current risks and making good us of resources
10608647.doc Page: 5 of 5