The Purpose of life is to go toward the freedom and drop all the fears of life. - Upanishdas
About Me
44% of pm use no software, even though PWC found that the use of commercially available PM software increases performance and satisfaction. Follow Tweet

Metrics: Leading Causes of Failed Agile Project Follow Tweet
PMLOGY

Monitoring and Controlling Process Group

Control Communications

Control Communications

×

My Message!

Click “X” to close.

Working on a story for this process
Previous Process Next Process

Control Communications: Process Table

Control Cost

Control Cost

×

My Message!

Click “X” to close.

Working on a story for this process
Previous Process Next Process

Control Cost: Process Table

Control Procurements

Control Procurements

×

My Message!

Click “X” to close.

Working on a story for this process
Previous Process Next Process

Control Procurements: Process Table

Control Quality

Quality Control

×

My Message!

Click “X” to close.

Working on a story for this process
Previous Process Next Process

Quality Control: Process Table

Control Risks

Control Risks

×

My Message!

Click “X” to close.

Working on a story for this process
Previous Process Next Process

Control Risks: Process Table

Control Schedule

Control Schedule

×

My Message!

Click “X” to close.

Once the deliverables and schedule has been promised to the stakeholders. The project team should be committed to complete the planned activities as per the schedule. Monitor the actual time taken to complete the activities, measure the schedule variation if any, compare the variation against allowed limit, analyze the reasons of variation. Prepare a detailed corrective action plan so that whatever possible time can be recovered. Prepare a detailed preventive action plan so that in future you can avoid certain activities which causes delays. If there is the variation which is causing overall delay in the deliverables or milestones or phase, then forecast the schedule which is doable.
Previous Process Next Process

Control Schedule: Process Table

Control Scope

Control Scope

×

My Message!

Click “X” to close.

Control scope is monitoring and controlling process. In any project especially large, complex, long duration, distributed team project it is possible that changes will go out of the control. If project management team is not able to manage and control the changes then no matter how good your project resources are you will never be able to complete the project successfully. This process is about managing and controlling all the scope and requirement changes. PMBOK’s focus is to emphasize that commit your deliverables and deliver whatever has been committed. It does not encourages project managers to deliver anything more or less than committed. Anything which is not committed if you are trying to deliver it is called gold-plating. Anything which is committed and you do not deliver it is called over committed or under delivery. Project managers must know how many change requests were rejected and why, how many change requests were accepted and why? What is over requirement stability and delivery status of the project. This process helps you in achieving all this.

Being a monitoring and controlling process important outputs of this process are metrics related to scope and requirements. If any course correction is required in the project then that can lead to raising change request.
Previous Process Next Process

Control Scope:Process Table

Control Stakeholder Engagement

Control Stakeholder Engagement

×

My Message!

Click “X” to close.

Working on a story for this process
Previous Process

Control Stakeholder Engagement: Process Table

Monitor and Control Project Work

Monitor and Control Project Work

PMBOK Monitor & Control Project Work

PMBOK Monitor & Control Project Work

How the management or customer or you will come to know that whether the project is going as per the approved plan? The only way is monitor the progress against the plan. Where is the plan for monitoring? In the project management plan! Project management plan includes the plan of project execution, project monitoring and controlling and project closure. So you need to prepare the performance report of the project work, perform analysis of the data collected and make decision if there is variance from the base plan. The decision is change request. Change request can lead to defect repair or preventive action or corrective action.

In nutshell the Monitor and Control Project Work process is for tracking, reviewing, and reporting the progress to meet the performance objectives defined in the project management plan. Monitoring and controlling of all project activities performed throughout project life-cycle.

Previous Process Next Process

Monitor and Control Project Work : Process Table

PMBOK Process Summary Table

Save

Save

Perform Integrated Change Control

PMBOK Perform Integrated Change Control

PMBOK Perform Integrated Change Control

Perform Integrated Change Control

Project exists to address the change. The project management is influenced heavily by the change management. It is almost impossible to complete a project successfully without taking a change request. But if you do not control the changes in a systematic way, then you will never to able to complete the project successfully. So at the heart of project management lies an art and science of managing and negotiating changes. PMBOK centralizes all the change requests through this process. Make as simple or as complicated your change request process as is the need of project but there is only one channel through which any change can be handled and that is this process called “Perform Integrated Change Control’.  Define your change management processes clearly, communicate and educate all the stakeholders and specially to the project team that how we handle changes to the approved work.

In the industries generally change request is consider increase of scope. But PMBOK gives very broad meaning to this term. If you cannot deliver a project successfully by following your approved project plan then whatever deviation you take is part of change. Change request need to be looked from two perspective a- what is changing b-what is impacting. What is changing can be process, training need, scope, availability of people, funds or time etc. What is impacting can be quality, functionality, performance, need of more funds or time. Therefore before you can a decision to work on a change or not you must know what is changing and what is the impact of the change.

Every change request may not lead to change in baseline or change of some document. Change may be as settle as we want to change our work culture so define a set of values and follow those from tomorrow morning. Change may be as gross as some work need to be re-done tomorrow because customer changed his mind. Great project managers always works with threshold limits so to approve every change they need not to go to management. Many times they themselves make the decision to implement the change and absorb the impact from the change budget. The beauty of great project management work is to address all the changes within the approved change budget.

The process of reviewing all change requests, approving changes and managing changes to the deliverables, organizational process assets, project documents , project management plan and communicating their disposition is perform integrated change control.

This process deals with influencing the factors that circumvent change request and ensure only approved changes are implemented. The responsibility of this process also includes documenting approved changes, maintaining integrity of baselines, coordinating changes across the entire project and documenting the complete impact of change request.
Previous Process Next Process

Perform Integrated Change Control : Process Table

PMBOK Process Summary Table

Save

Save

Save

Validate Scope

Validate Scope

×

My Message!

Click “X” to close.

Validate Scope process comes in picture when project’s output is shown to the customer or end-user. In this process customer validates the requirement against the baseline and his/her need. Sometime even if the feature displayed to customer is part of the scope baseline but that does not meet the need of customer then s/he can request for a change. If everythig is fine and fits the need of customer then s/he can signoff that piece of work. PMBOK does not encourage one time big demo for the customer or one big bank sign off from customer but based on the complexity of project keep customer engaged, schedule and show demo many times in project lifecycle. As and when some small deliverable is ready it is important to take feedback from customer and incorporate the change if suggested by customer. Keep in mind that any change has to managed through Perform Integrated Change Control process
Previous Process Next Process

Validate Scope:Process Table

PMBOK Process Summary Table