If there were a single perfect style of project management to fit every scenario, someone would have found it by now. Michelle Symonds argues at TechRepublic that neither Waterfall nor Agile is enough to get the best results out of every project, and there are cases where a thoughtful combination of the two might be a better choice. Agile is useful when dealing with less tangible products such as software systems and new business processes, where the iterative approach can really shine, but it is a method where costs are difficult to estimate. Waterfall by comparison, with its hierarchical and meticulous structure, allows a product to be fully defined early and for a schedule to be built around the product’s completion. When one method takes ideas from the other, which often happens unconsciously in the workplace, sometimes better results can be realized. There exists “iterative Waterfall” as well as Agile that incorporates document tracking processes. Consider how taking the most appropriate elements of both methods could help you improve the quality and speed of your project success.