WATERFALL AND AGILE

Waterfall and Agile
Student’s Name
Institution
Abstract
Software development has become popular in recent times with more and more software coming up each year. There is, therefore, need to know about the different software processes before any purchase. The waterfall and agile methodologies are one of the most common in software development. Waterfall methodology is a process that follows a step by step design, i.e., the developers complete one stage before moving on to the next, and when one stage is completed. Agile methodologies, on the other hand, can be referred to as those that are guided by the Agile Manifesto, which is some principles that guide the development process and include response to change, collaboration, a working software, and interactions before other things. Extreme programming has various advantages over other methodologies which include better satisfaction, resilience, and robustness among others. Developers can also respond faster to changing customer requirements even in later development stages. Some of the factors to consider while choosing the best methodology include communication, organizational structure, training, and culture.
Keywords: Waterfall methodology, Agile methodology, Extreme programming, Software
1.
Waterfall methodology is a process that follows a step by step design, i.e., the developers complete one stage before moving on to the next, and when one stage is completed, there is no going back. The various stages of the methodology include Requirements capture, Design, Construction, Integration, Testing and debugging, installation, and maintenance (Johnson, 2010).

There are usually clear gates to define when one stage is complete and when another can start. It is therefore right to say that the waterfall methodology is a basic development roadmap while PMBOK is the tool that gives a number of techniques to ensure better management of that development process. Each phase of an item’s lifecycle as per this model is sequential such that the progress flows steadily down the stages like water in a waterfall (Bowes, 2014).
2.
Agile methodologies can be referred to as those that are guided by the Agile Manifesto, which is some principles that guide the development process (Johnson, 2010). The manifesto values normally include:
• Responding to change over sticking to plans
• Customer collaboration as opposed to contract negotiation
• Working software as opposed to extensive documentation
The methodology helps reduce unpredictability through iterative work cadences. Project management lays emphasis on the project manager’s skills in coordination and communication (Waters, 2007).
3.
The developers of the methodology aimed at creating a sustainable development process that would lead to software that meets the business needs. There are many pros associated with this software. To start with, the methodology process is quite easy even for those with little development know-how. The working software can be delivered at faster pace, and new versions can be delivered consistently and frequently. Modifications can also be integrated at almost any point even in the later development stages (Bowes, 2014). The methodologies also assist in simplifying the software development process.
4.
XP’s advantages include lesser risks, cost savings, resilience, robustness, and better overall satisfaction (Nayab, 2010). It also empowers developers to respond easily to changing customer requirements even in later development stages. XP also ensures that the developers complete their duties on time through various schedules and plans.
5.
The Extreme Programming is good in that it allows you to receive everything you need in your software as there is an opportunity of making changes even in later stages as opposed to receiving everything in future. The process also relies to a great extent on customer involvement.
6.
No project management methodology can be said to be perfect or extremely useless. Each has its weakness and strengths, so one has to decide about what they need carefully. When selecting a methodology, one should consider culture and organizational structure among other factors. Cockburn (2000) proposes some principles to consider when selecting an organization’s management methodology. These include:
• The most effective communication form is face-to-face and interactive
• A larger methodology is the most suitable for a large group
• A large amount of the total cost may result from a small increase in the size of the methodology
• The construction of a critical system should be more visibly correct.
References
Bowes, J. (2014). Agile vs Waterfall – Comparing project management methods. Manifesto. Retrieved 20 January 2018, from https://manifesto.co.uk/agile-vs-waterfall-comparing-project-management-methodologies/
Cockburn, A. (2000). Selecting a Project’s Methodology. IEEE Software, 17(4), 64-71. http://dx.doi.org/https://doi.org/10.1109/52.854070
Johnson, D. (2010). Waterfall or Agile? Differences between predictive and adaptive software methodologies. SearchSoftwareQuality. Retrieved 20 January 2018, from http://searchsoftwarequality.techtarget.com/tip/Waterfall-or-Agile-Differences-between-predictive-and-adaptive-software-methodologies
Nayab, N. (2010). What Are the Advantages of Extreme Programming?. Brighthub Project Management. Retrieved 20 January 2018, from http://www.brighthubpm.com/methods-strategies/87839-advantages-of-extreme-programming/
Waters, K. (2007). What Is Agile? (10 Key Principles of Agile) | 101 Ways. 101 Ways. Retrieved 20 January 2018, from https://www.101ways.com/what-is-agile-10-key-principles/