CAPMMedium

CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach

Question 67 of 85 in Explain when it is appropriate to use a predictive, plan-based approach

Pick an answer below — you'll get the explanation instantly, no signup.

A government project requires that all project decisions be traceable to specific requirements. This traceability requirement MOST directly supports using:

Show answer & explanation

Correct answer: A predictive approach where requirements are formally documented and traced through deliverables

Explanation

Requirements traceability — the ability to trace decisions and deliverables back to specific documented requirements — is a key practice in predictive projects. Requirements traceability matrices link requirements to design decisions, to deliverables, and to test cases, providing the audit trail that government and regulated projects require.

**Why not A:** An adaptive approach with continuous stakeholder feedback emphasizes responsiveness to change, not formal requirements traceability. While adaptive approaches can incorporate feedback, they do not inherently provide the formal documentation and audit trails that traceability demands.

**Why not C:** A kanban approach focuses on workflow visualization and work-in-progress limits. While useful for managing flow, kanban does not inherently provide the formal requirements documentation and traceability matrices that government projects require for audit compliance.

**Why not D:** Extreme programming with test-driven development is a software-specific agile practice. While tests can verify requirements, XP does not provide the formal documentation structure and requirements traceability matrices needed for government audit trails.

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