Which approach is a sequential project lifecycle model often chosen when changes are unlikely?

Which approach is a sequential project lifecycle model often chosen when changes are unlikely?

• A. Harmonogram
• B. Dependencies
• C. Stakhanovite Movement
• D. Waterfall method

Answer: (D)

When changes are unlikely, a sequential project lifecycle emphasizes finishing each phase before starting the next, with extensive upfront planning and documentation. This makes it easier to manage scope and contracts because requirements, design, and deliverables are locked in early. The Waterfall method follows a strict sequence—requirements, design, implementation, testing, and deployment—where each stage must be completed and approved before moving on. Because revisiting earlier work can be costly and disruptive, Waterfall works best in environments with well-understood needs and stable requirements. In more flexible projects, other approaches that accommodate iteration and scope changes are used instead. The other options aren’t project lifecycle models and don’t capture this sequential, change-averse structure.

When changes are unlikely, a sequential project lifecycle emphasizes finishing each phase before starting the next, with extensive upfront planning and documentation. This makes it easier to manage scope and contracts because requirements, design, and deliverables are locked in early. The Waterfall method follows a strict sequence—requirements, design, implementation, testing, and deployment—where each stage must be completed and approved before moving on. Because revisiting earlier work can be costly and disruptive, Waterfall works best in environments with well-understood needs and stable requirements. In more flexible projects, other approaches that accommodate iteration and scope changes are used instead. The other options aren’t project lifecycle models and don’t capture this sequential, change-averse structure.