Please login or join to subscribe to this thread
Change requests are approved for implementation. Hence approved CRs are input to the Execution process groups and more specifically the direct and manage project work process for implementation.
Once implemented, they (and their results) are input the control quality process, which in turn feeds into the monitor and control project work process.
As part of the process of approving CRs, schedule and cost baseline may be changed, which are input to the respective control processes.
Thank you Thomas !
But this gets more confusing in my head.
In the book "Head First PMP" I read that the goal of "Control scope" is to turn approved changes into document updates.
So I understand that I need to get the "approved version" of the change request inside the "Control Scope" to changed the related documents.
And I also expect that the baseline is modified BEFORE implementation. Isn't it ?
Take a look to Quality. Control Quality is about to take the deliverable and validate it conforms the requirements and approved change request has been implemented. Control Quality is performed on each projece deliverable. Taking your question, Control Scope or Control Schedule is about to take scope/schedule, take work performance data, and see any deviation. If deviation is in place a change request has to be rised. If a change is rised it has to be put under approval consideration performing Integrated Change Control. If the change has been approved it will be implemented performing Direct and Manage Project Work.
Thank you Sergio.
So does it mean that if I detect a scope change that needs to be done in "Control Scope", the update of the related documents once the change is approved is not done in the "Control Scope" process ?
Alexandre, I would argue that any potential scope change has to be analyzed before approval. A key tool for this is the requirements traceability matrix (see PMBoK page 148 bottom). From there, all(!) planning processes might be triggered. If this revised plan is presented to the CCB, they have all the information to approve or not. Only then, CR implementation is triggered.
Control (scope) is not involved, other than the baselines and other planning documents might have changed.
The changed baselines are prepared with the planning before approval and implemented after approval.
This is a great example how agile and flexible the PMBoK processes are.
And, regarding the change, it might be necessary to change the business case, which is almost never done in practice though and reason for many project failures. Business case changes are not in scope of the project manager.
Thank you Thomas.
But while you are preparing changes to all these planning documents, they are still not commited in the system right ?
These are just temporary documents sent to the change control board, until change is approved right ?
Because if the change was applied on these documents, and the change is not approved, then we would have to undo all these changes...
So I guess my question was rather when the changes are commited to the system.
Thanks for your anwsers !
@Sergio : why then do we have scope baseline / schedule baseline and cost baseline as an output of "Control Scope" ? Are they not changed by the "Control Scope" process ?
@Thomas : so do you mean that when the team receives the approved changes in the process "Direct and Manage work", the approved changes are not yet modified in the baseline included in the project management plan ?
Please login or join to reply