Is the Waterfall methodology currently used in any projects?

Yes, it is used, but significantly less often than before, and in specific fields.

Examples of projects where Waterfall can be applied:

• Projects with strict requirements and minimal uncertainty: For example, development of critical safety systems, medical equipment, aerospace software.
• Projects with clearly defined scope and fixed budget: When project requirements are well known and not expected to change significantly during the process.
• Projects with a sequential development process: Where each stage must be fully completed and documented before moving to the next.

Main advantages of Waterfall in such cases:

• Predictability: Clear planning and sequential execution of stages simplify forecasting timelines and budgets.
• Documentation: The process is actively oriented towards creating detailed documentation at each stage.
• Strict control: Easier to monitor compliance with requirements at each step.

Disadvantages (often the reason for abandoning Waterfall):

• Low flexibility: Difficult to make changes after development has started.
• Risk of late defect detection: Main testing is conducted at the final stages.
• Long feedback cycle: The customer sees the product only at the end.

Thus, although agile methodologies predominate, Waterfall retains its application in niche projects with special characteristics.