  Since the Agile Manifesto, many organizations have explored agile development
methods to replace traditional waterfall development. Interestingly, waterfall
remains the most widely used practice, suggesting that there is something
missing from the many "flavors" of agile methodologies. We explore seven of the
most common practices to explore this, and evaluate each against a series of
criteria centered around product quality and adherence to agile practices. We
find that no methodology entirely replaces waterfall and summarize the
strengths and weaknesses of each. From this, we conclude that agile methods
are, as a whole, unable to cope with the realities of technical debt and large
scale systems. Ultimately, no one methodology fits all projects.
