How do you create agile processes to manage unpredictability?
(A) Requirements gathering must be conducted very carefully
(B) Risk analysis must be conducted before planning takes place
(C) Software increments must be delivered in short time periods
(D) Software processes must not adapt to changes incrementally

Explanation

Agility copes with unpredictability by shortening the feedback loop, so the essential practice is that software increments must be delivered in short time periods — short iterations let the customer see working software early and let the plan be adjusted from real evidence. Statement (A) reflects the heavyweight, plan-driven belief that requirements can be pinned down up front, which agile explicitly rejects. Statement (B) puts risk analysis before planning as a one-off gate, whereas agile re-assesses risk every iteration. Statement (D) is the exact opposite of agility, since adapting incrementally to change is the core agile principle, so (C) only is correct.