How do you create agile processes to manage unpredictability? A. Requirements…

Correct answer: Software increments must be delivered in short time periods.

Why this works:

• Frequent feedback from stakeholders allows quick validation and course correction.

• Early delivery of working software reduces the risk of building the wrong thing.

• Short increments make planning and estimation more accurate because teams plan with recent information.

• Frequent releases enable incremental adaptation to changing requirements, reducing the impact of unpredictability.

Why the other statements are not suitable:

• "Requirements gathering must be conducted very carefully": This suggests exhaustive upfront requirements work. Agile favors iterative discovery and continuous refinement rather than trying to define everything up front.

• "Risk analysis must be conducted before planning takes place": While identifying major risks early is useful, agile treats risk assessment as an ongoing activity integrated into planning and backlog prioritization, not a one-time pre-planning task.

• "Software processes must not adapt to changes incrementally": This contradicts agile values. Agile requires adapting processes and work incrementally based on feedback and changing conditions.

Actionable tip: Adopt short iterations (for example, 1–4 weeks), deliver a working increment each iteration, review with stakeholders, and use the feedback to adapt priorities and plans.