PMGT5820 Chap.6 Integrated Change and Quality Control
Integrated Change and Quality Control
Change and quality are integrated control systems. This chapter distinguishes clarification, defect correction, process improvement and new requirements; traces requests through impact analysis and delegated authority; and connects approved changes to configuration and verification. It also separates quality planning, process management and output control so inspection is not mistaken for prevention or client acceptance.
The original baseline remains visible while a proposal is analysed because a likely future is not yet an authorised commitment. Impact analysis follows the request into requirements, schedule, cost, resources, procurement, risk, documentation and acceptance. After a delegated decision, configuration records identify the effective version and the team verifies whether implementation achieved its purpose.
Quality planning defines standards and methods, managing quality improves the production process, and quality control inspects results. A technically conforming output may still await client acceptance, while a repeated defect may demand both immediate correction and a separate response to the underlying process cause.
What this chapter covers
- 01
Sources of change and the importance of clear communication
- 02
Change requests, boards, delegated authority and decision records
- 03
Impact analysis across scope, time, cost, quality and risk
- 04
Configuration control and linked document updates
- 05
Quality planning, managing quality and controlling quality
- 06
Defects, root causes, process improvement and verification
Worked example · free
Classify a stronger-material request
- +1Compare the request and current output with the authorised requirement.
- +1Classify it as change because the original output conforms to the approved specification.
- +1Assess value, cost, schedule, quality, risk and procurement effects.
- +1Obtain a decision from delegated authority and update linked records.
- +1Verify the implemented material and obtain acceptance against revised criteria.
Key terms
- Change request
- A documented proposal to modify a project baseline, requirement, deliverable or control.
- Change authority
- The delegated person or body permitted to approve a defined class of project change.
- Configuration control
- The discipline of identifying, versioning and reconciling the authorised product and project records.
- Quality control
- Inspection or testing of outputs against stated requirements and acceptance evidence.
Integrated Change and Quality Control FAQ
How can I distinguish a defect from a change?
Compare the current output or request with the authorised requirement. Failure to meet that requirement is a defect. Added or altered capability is a change. Ambiguous wording needs documented interpretation and escalation if the interpretation changes the committed boundary.
Why should the old baseline remain visible?
The old reference preserves variance and governance history. Teams can analyse and forecast a likely change, but only delegated approval creates a revised baseline. Silent replanning hides performance and makes later decisions impossible to audit.
How do quality management and quality control differ?
Managing quality improves the processes used to create the result, while quality control inspects or tests outputs. More inspection may detect defects without preventing them. Repeated failure should trigger root-cause analysis and a verified process response.
Assessment move
Take one observed condition and classify it four ways: defect, clarification, change request or process weakness. Explain which evidence would decide. Then run an approved change through requirements, schedule, cost, procurement, risk, quality tests and communication. Finish by comparing verification with formal client acceptance. Use a two-column exercise that preserves the approved state beside the proposed state.
Begin with the request, reason, affected configuration and decision deadline. Trace direct and secondary impacts without changing the baseline during analysis. Identify options, assumptions, recommendation and the role with delegated authority. If the request is urgent, state the emergency governance route rather than allowing urgency to substitute for approval.
After a decision, list every artefact whose version must change and the stakeholder who needs the new instruction. Add a verification method, criterion, evidence owner and review date. In a separate quality exercise, sort examples into planning, process management and output control. For a failed test, describe containment and correction first, then use repeated patterns to investigate a systemic cause.
Do not prescribe training or more inspection until the evidence indicates why the failure occurred. Compare a defect correction with a requested enhancement so the cost and authority routes remain distinct. Conclude with a configuration audit across the physical result, approved changes, drawings, manuals, training and acceptance records.
The aim is to explain not only what changed, but which future became authorised and how the project proved it was delivered. Preserve a rejected option and its reason in the exercise so later analysis can distinguish deliberate choice from an idea that was never assessed.
Working through Integrated Change and Quality Control in PMGT5820? Sia is AskSia’s AI Project Management tutor — ask any PMGT5820 Integrated Change and Quality Control question and get a clear, step-by-step explanation grounded in how PMGT5820 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
