How does Agile bring predictability to the Planning process?

Question

Options

• ABy allowing the customers to review the progress often.
• BBy assigning most of the responsibility to the Product Owner.
• CBy making the team self-organized and self-planning.
• DBy providing early visibility into the team's progress.

• A
  3% (1)
• D
  97% (28)

Explanation

Agile achieves predictability in planning through early visibility into the team's progress (D) - by delivering working software in short iterations (sprints), stakeholders can see actual velocity, identify risks early, and make informed forecasts about future delivery. This empirical feedback loop is what makes Agile planning reliable rather than speculative.

Why the distractors are wrong:

• A is a benefit of Agile (customer review), but it's a transparency mechanism, not the source of planning predictability - it describes what customers do, not how predictability is achieved.
• B is factually misleading; Agile distributes planning responsibility across the whole team, not primarily to the Product Owner (who owns the backlog, not the plan).
• C describes a real Agile trait, but self-organization enables adaptability, not predictability - it's about how the team works, not how forecasts are made.

Memory tip: Think of Agile planning as a GPS rerouting in real time. Predictability comes from seeing where you actually are (early visibility) - not from who's driving (C/B) or who's watching from the passenger seat (A).

No community discussion yet for this question.