CAPM Practice: Explain the components of an adaptive plan

Adaptive projects excel with fixed deadlines by varying scope rather than quality or time. Prioritizing highest-value features ensures the most important items are delivered even if the full backlog isn't completed. 'Good enough' shipped beats 'perfect' not shipped.

**Why not A:** Adding extra iterations to guarantee full delivery conflates time with capacity — more sprints do not exist if the regulatory deadline is fixed. This option also assumes that all 200 story points of backlog must be delivered, which ignores the adaptive principle that scope is variable when time is fixed. The correct response is to prioritize ruthlessly, not to create imaginary capacity.

**Why not B:** Ignoring a fixed regulatory deadline is not an option in a professional or legal context. Regulatory requirements carry real consequences for non-compliance, and adaptive methodologies do not grant permission to disregard contractual or legal constraints. Adaptive projects are designed to operate within real-world constraints, including hard deadlines, by managing scope accordingly.

**Why not C:** Adaptive approaches are fully compatible with fixed deadlines — they are actually better suited to them than predictive approaches because scope can flex while time and quality remain constant. Converting to predictive methodology would sacrifice the team's ability to reprioritize based on new information and would not guarantee delivery any more reliably. The problem is not the methodology; it is the need for explicit prioritization.