What is a project life cycle and how is the choice between waterfall and iterative approaches typically made?

What is a project life cycle and how is the choice between waterfall and iterative approaches typically made?

• A. The sequence of phases from initiation to closure; choice depends on scope stability, risk, and stakeholder needs.
• B. It determines the budget only.
• C. It is about the organizational structure.
• D. It describes only the testing phase.

Answer: (A)

A project life cycle is the sequence of phases a project goes through from start to finish, typically including initiating, planning, executing, monitoring and controlling, and closing. The choice between a waterfall and an iterative approach is guided by how stable the requirements are, the level of risk, and how much stakeholder feedback is needed. Waterfall fits well when requirements are well understood, unlikely to change, and a fixed scope, schedule, and budget are important. Iterative (or agile) suits projects where requirements may evolve, there’s higher risk or uncertainty, and delivering increments with regular feedback is valuable. The life cycle framework isn’t about budget, organizational structure, or only testing; it’s the overall path from start to finish that helps determine whether a linear, plan-driven or a flexible, iterative delivery makes the most sense.

A project life cycle is the sequence of phases a project goes through from start to finish, typically including initiating, planning, executing, monitoring and controlling, and closing. The choice between a waterfall and an iterative approach is guided by how stable the requirements are, the level of risk, and how much stakeholder feedback is needed. Waterfall fits well when requirements are well understood, unlikely to change, and a fixed scope, schedule, and budget are important. Iterative (or agile) suits projects where requirements may evolve, there’s higher risk or uncertainty, and delivering increments with regular feedback is valuable. The life cycle framework isn’t about budget, organizational structure, or only testing; it’s the overall path from start to finish that helps determine whether a linear, plan-driven or a flexible, iterative delivery makes the most sense.