Project Scope and Quality Flashcards
7 cards from real Project Management practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Project Scope and Quality flashcards as text
A project has completed all planned work, but the customer refuses to formally accept the deliverables, citing unmet requirements. Which process failed?
Answer: Validate Scope
Validate Scope is the process of obtaining formal acceptance; if the customer rejects deliverables, this process was either skipped or not performed effectively.
The 'quality is free' philosophy, popularized by Philip Crosby, means:
Answer: The cost of preventing defects is less than the cost of fixing them
Crosby argued that investing in defect prevention is cheaper than the costs of rework, scrap, and warranty claims from poor quality.
Which tool would a project manager use to verify that the WBS captures all the work—and only the work—required to complete the project?
Answer: 100% rule
The 100% rule states that the WBS must include 100% of the work defined in the scope and no more, ensuring completeness without over-inclusion.
A project manager is conducting a quality audit. The PRIMARY goal of this audit is to:
Answer: Confirm that quality policies and procedures are being followed
Quality audits are structured reviews to determine whether project activities comply with organizational and project policies, processes, and procedures.
When scope is being controlled, work performance data is compared to the scope baseline to produce:
Answer: Change requests and work performance information
Control Scope produces work performance information (variance analysis results) and may generate change requests when deviations are found.
A project team is selecting quality standards relevant to their software project. This activity occurs during which process?
Answer: Plan Quality Management
Plan Quality Management is where the team identifies relevant quality standards and determines how to satisfy them for the project.
If a project's scope statement is vague and poorly defined, the most likely consequence is:
Answer: Frequent scope creep and stakeholder conflicts
A vague scope statement leads to differing interpretations among stakeholders, causing unauthorized additions, rework, and disputes.