Under what circumstances is an iterative lifecycle preferred over a waterfall approach?

Under what circumstances is an iterative lifecycle preferred over a waterfall approach?

• A. When the schedule is fixed and there is no need for flexibility.
• B. When scope stability is low and you expect frequent stakeholder feedback.
• C. When requirements are fully known and unlikely to change.
• D. When the project has no risk.

Answer: (B)

Iterative lifecycles shine when what you’re building isn’t fully known yet and you expect to learn and adjust through ongoing stakeholder feedback. By delivering in small increments, you quickly validate what matters, incorporate new insights, and refine requirements as the project progresses. This approach reduces the risk of delivering the wrong thing and keeps the work aligned with real needs, which is exactly what you want when scope stability is low. If requirements were fully known and unlikely to change, a plan-driven, waterfall path makes more sense because you can lock everything in up front and execute in a straightforward sequence. A fixed schedule with no need for flexibility signals you won’t gain from feedback loops. And risk is not a reason to avoid iteration—iterative methods actively address risk by exposing assumptions early and correcting course often.

Iterative lifecycles shine when what you’re building isn’t fully known yet and you expect to learn and adjust through ongoing stakeholder feedback. By delivering in small increments, you quickly validate what matters, incorporate new insights, and refine requirements as the project progresses. This approach reduces the risk of delivering the wrong thing and keeps the work aligned with real needs, which is exactly what you want when scope stability is low.

If requirements were fully known and unlikely to change, a plan-driven, waterfall path makes more sense because you can lock everything in up front and execute in a straightforward sequence. A fixed schedule with no need for flexibility signals you won’t gain from feedback loops. And risk is not a reason to avoid iteration—iterative methods actively address risk by exposing assumptions early and correcting course often.