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

Defense contracting presents classic predictive indicators: exhaustive specifications, joint change approval (Change Control Board equivalent), contractual obligations, documentation requirements, and regulatory compliance. Defense acquisition processes evolved alongside (and helped develop) predictive project management — they are deeply aligned.

**Why not B:** While electronic equipment development can sometimes benefit from iteration, the exhaustive military specifications and joint change approval requirements are strong predictive indicators. Scrum's iterative approach conflicts with the rigid, documentation-heavy nature of defense contracting.

**Why not C:** A hybrid approach implies flexibility within the contract structure, but the scenario describes exhaustive specifications with formal joint change approval — leaving little room for adaptive elements. The defense contracting environment is thoroughly aligned with predictive methodology without needing hybrid accommodations.

**Why not D:** Kanban's continuous flow model is designed for ongoing work management, not for a defined project with exhaustive specifications and formal change control. Defense contracting requires structured phase gates and documentation that Kanban does not inherently provide.