This qualitative study analyzed experiences of twenty software developers. The research showed that all software development methodologies are distinct from each other. While some, such as waterfall, focus on traditional, plan-driven approaches that allow software requirements and design to evolve; others facilitate ambiguity and uncertainty by accommodating and encouraging change, such as agile methods. This study disclosed each end of the methodology spectrum as having distinct characteristics. After reviewing this investigation, it should be plausible to make a software development selection based on factors that would aptly predict success. A major conclusion derived from this study revealed that there are appropriate times in which specific methodology should be used in application development. Unfortunately, many businesses do not evaluate certain factors, such as; organizational culture, the experience of the software team, and type of development project executed before indoctrinating a methodology into their software environment. This phenomenological study is significant because it addresses a gap in the scholarly literature on how software development methodology is selected. The results of this study can be used as a benchmark for those making determinations as to which methodologies should be used in relation to successful application development projects. [The dissertation citations contained here are published with the permission of ProQuest LLC. Further reproduction is prohibited without permission. Copies of dissertations may be obtained by Telephone (800) 1-800-521-0600. Web page: http://www.proquest.com/en-US/products/dissertations/individuals.shtml.]