Project Management Central

Please login or join to subscribe to this thread

Topics: Change Management, Quality
Why approved change requests are inputs of Control quality process ?
Network:38



Why approved change requests are inputs of Control quality process ? As of my understanding approved CR's gets implemented in the manage and direct project work and then the resulting deliverables go through control quality to get verified. At this point the Approved CR's are already implemented and no need to specify them as inputs to control quality.
Sort By:
Network:299



Quality control is process driven. Changes to the quality control process require approval, just like changes to a project.
Network:113802



Hakim,

To control quality you need to do it again the latest change to the project requirements. You probably prefer to receive the approved change instead of searching for them in an updated document.
Network:62



It's very logical if you think it logically. Approved CR's changes the deliverables. You have to validate deliverables based on the quality premises then logically Approved CR's is an input of QC process.
Network:1851



It was a hugh debate in the past about this topic. If you modify a deliverable then you have to send it to Control Quality process. To see if the change was made as defined you need the deliverable and the approved change because the approved change is the document or the artifact where the description of the change was stated so is the source to assure that the change was made in the deliverable as needed.
...
1 reply by Hakim Mentagui
Jul 25, 2019 2:22 PM
Hakim Mentagui
...
Hi Sergio,

I'm curious to know what was the debate about and the different point of views that were shared.

Thanks
Network:23657



Because you have to check the result/product with the latest design/plan.
Network:210



"The implementation of approved changes should be verified, confirmed for completeness, retested, and certified as correct." PMBOKĀ® Guide, p. 301
Network:38



Thank you all for your inputs. Relying on the approved CR's to do Control Quality in my opinion is not a best practice. That could lead to deliverables specs scattered accross project documents and all approved CR's.

The PMBOK mention the configuration management plan which defines how to manage effectively the changes to the deliverables among other components of the project.

In my opinion using the configuration management plan is better than relying on the approved CR's. The configuration management plan is an input to 2 processes : Perform Integrated Change Control and Control Scope. It is however not used in the Control Quality process.
...
1 reply by Eric Isom
Jul 26, 2019 8:31 PM
Eric Isom
...
You're right that you shouldn't rely on just the CR.

But you do need the CR in order to apply the Control Quality process to ensure that what was agreed to be changed actually gets changed. That starts with making the appropriate changes to the scope, schedule, and cost baselines, and the quality plan, and the quality control process, and whatever else needs to be changed so that the deliverables specs are NOT scattered across project documents and approved CRs.

Control Quality is needed to keep this mess from happening. That's why it's an input to Control Quality.
Network:38



Jul 23, 2019 6:25 AM
Replying to Sergio Luis Conte
...
It was a hugh debate in the past about this topic. If you modify a deliverable then you have to send it to Control Quality process. To see if the change was made as defined you need the deliverable and the approved change because the approved change is the document or the artifact where the description of the change was stated so is the source to assure that the change was made in the deliverable as needed.
Hi Sergio,

I'm curious to know what was the debate about and the different point of views that were shared.

Thanks
Network:210



Jul 25, 2019 12:35 PM
Replying to Hakim Mentagui
...
Thank you all for your inputs. Relying on the approved CR's to do Control Quality in my opinion is not a best practice. That could lead to deliverables specs scattered accross project documents and all approved CR's.

The PMBOK mention the configuration management plan which defines how to manage effectively the changes to the deliverables among other components of the project.

In my opinion using the configuration management plan is better than relying on the approved CR's. The configuration management plan is an input to 2 processes : Perform Integrated Change Control and Control Scope. It is however not used in the Control Quality process.
You're right that you shouldn't rely on just the CR.

But you do need the CR in order to apply the Control Quality process to ensure that what was agreed to be changed actually gets changed. That starts with making the appropriate changes to the scope, schedule, and cost baselines, and the quality plan, and the quality control process, and whatever else needs to be changed so that the deliverables specs are NOT scattered across project documents and approved CRs.

Control Quality is needed to keep this mess from happening. That's why it's an input to Control Quality.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"It is better to have a permanent income than to be fascinating."

- Oscar Wilde

ADVERTISEMENT

Sponsors