CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach
Question 73 of 85 in Explain when it is appropriate to use a predictive, plan-based approach
Show answer & explanation
Correct answer: Plan quality upfront with defined standards, followed by quality assurance and control activities against those standards
Explanation
Predictive quality management follows the same front-loaded philosophy as the overall approach: quality standards are defined during planning, quality assurance activities verify adherence to processes during execution, and quality control inspects deliverables against defined standards. This structured, plan-then-execute approach mirrors the predictive project framework.
**Why not A:** Test-driven development is a software engineering practice closely associated with agile and extreme programming methodologies. While valuable, it is not a quality management approach that naturally aligns with predictive project methodology.
**Why not B:** Continuous improvement through short feedback loops and daily inspection is characteristic of agile approaches like Scrum. Predictive quality management relies on upfront quality planning rather than continuous iterative feedback.
**Why not D:** Managing quality informally based on team expertise is not a structured approach and does not align with any formal methodology. Predictive projects require documented quality standards, planned QA activities, and formal QC processes — not informal reliance on individual expertise.
Key Concept
This question covers Explain when it is appropriate to use a predictive, plan-based approach under Explain when it is appropriate to use a predictive, plan-based approach (Predictive, Plan-Based Methodologies).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free