While the development process is ongoing, the marketing team generates u0022buzzu0022 in anticipation of the product while the sales team demonstrates why the product is a solution for the customer's issues. Generally, Agile methodology is used more frequently, but it is not always the most preferred or suitable option. When the requirements are clear from the start and highly unlikely to change, Waterfall is the best solution. Also, if the customer prefers not to be involved in the development on an ongoing basis or at all before the review phase and final presentation, Waterfall might be a better fit for you. Besides the system education that's the same regardless of the method used, which can also be altered to fewer educations ahead of a larger release, the Waterfall approach only requires the customer to receive and install the product. If the project is small and the speed of delivery is irrelevant, Waterfall might be better suited for you. If the delivery is to be applied to a legacy system that's not prone to change, and you have similar projects in the future that allow reuse of the project plan and can draw from the previous documentation, Waterfall can elevate your project while saving time and resources for your team. Finally, if you are dealing with more complex dependencies, Waterfall is the way to go.