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

The primary driver for methodology selection is the nature of the project's requirements. High certainty and stability in requirements favor predictive. High uncertainty and expected evolution favor adaptive. Team preferences, PM experience, and tooling are secondary considerations that should adapt to the project's characteristics, not drive methodology selection.

**Why not A:** Team preference is a secondary consideration, not a key input to methodology selection. The methodology should be driven by project characteristics — particularly requirement certainty and stability — not by what the team prefers to use.

**Why not B:** The project manager's years of experience may influence their comfort level with a methodology but should not drive the selection. An experienced PM should be able to apply whichever methodology best fits the project's characteristics, regardless of personal experience.

**Why not D:** Whether the organization uses project management software is a tooling consideration, not a methodology selection input. Both predictive and adaptive approaches can be supported by various software tools. The tool does not determine the methodology.