Agile V. Waterfall

For the system support, we will have a help desk to help customers with order processing, undelivered orders, etc. We will then need to setup a plan for maintenance tasks. Corrective maintenance will be to diagnose and correct any problems as reported by customers. Adaptive maintenance will be to make changes to the website, such as changing the design layout if needed. Perfective maintenance will be to make sure the system runs as efficiently and reliably and possible. Finally, preventative maintenance will analyze where problems may arise in the

After full implementation, the system will enter the maintenance phase. Depending on the term of the contract, Smith will be involved in the maintenance phase of the system through its live cycle. All contracts include phone support for as-designed elements of the system.

The initial and most important step of the testing phase is creating the test plan. The test plan should include what features and functionality will be tested based on the confirmed requirements. The next step is unit testing or code review. Unit testing involves the QA person testing the code on their machine. Once code has passed the unit test, it will then be released to the testing environment for system testing. The QA person can then test the integration of the different modules of the code as a program rather than separate parts as well as to find and report bugs and any data inaccuracy. The next phase of testing is the user acceptance test. In this phase the users test the program for functionality and data accuracy. The test phase isn’t a linear phase, more of a circular, back and forth between the developers and the QA people. After all phases have passed, the next step would be to open a change

In addition, defining requirements can be difficult and sometimes early assumptions are flawed. Some opponents of Waterfall argue that it is impossible to fully understand the system requirements until the development phase and that some performance issues cannot be predicted or are not evident until the testing phase. Waterfall is not well-suited for custom software projects that rely heavily on continuous customer feedback and changing needs because communication and collaboration is not always stressed; once the requirements are established, the customer may have little contact with the development team until delivery. (Chatterjee, 2010) Because Waterfall projects are not based upon small iterations that can be easily and promptly modified, occasionally critical errors are found in the late stages of a Waterfall software development project that require scrapping the project and starting over; a very costly and disappointing result. Another negative is that some programmers believe that Waterfall is out-of-date and that it does not accommodate for the unknown factors that are a constant challenge in designing leading edge technology. Developers who abide by

Agile development refers to any development process that is aligned with the concepts of the Agile Manifesto, these are: (Agilemanifesto.org, 2016)

I utilized Saint Joseph’s University Drexel Library to research the waterfall and agile software development methodologies and selected two pieces of literature to understand which method is more effective. The following articles are discussed in detail below:

Comparing articles that tackle the Waterfall Method and the Agile Management Approach: A Comparison and Contrast

To this point, one stark contrast between the Waterfall and Agile methods of software development is the degree to which they involve the customer. In this sense it is easier to think of the Waterfall model as being more “predictive” and the Agile model as being more “adaptive”. There are milestones in either case, but the changes that are a result of customer input drive the flow of development in an Agile system (Arken 2008). One can see how the “adaptive vs. predictive” differences can become more of a problem where finances are concerned.

There are various agile methodologies. The philosophy of the various agile methodologies are the same like iterative approach in managing a project but they differ in some of the practices they follow in tackling and managing the tasks.

In testing all the components are methodically verified to make sure it is error-free and make sure the requirements are met. An independent quality assurance team defines "test cases" to evaluate whether the product fully or partially satisfies the requirements in the

The waterfall technique has stages that it experiences. In the content, it says that, "no one developed the waterfall strategy" (Bowes, J.). It was acquired by big business programming engineers. There is a few advantages and disadvantages of the waterfall strategy. A few geniuses are "The advancement procedure has a tendency to be better recorded since this strategy places more prominent accentuation on documentation like necessities and outline docs. Numerous associations locate this consoling" (Bowes, J.). The waterfall procedure is one of the simpler ones to get it. A con of the waterfall strategy is "Frequently the general population we're building programming for (the customer) don't know precisely what they require in advance and don't have the foggiest idea about what's conceivable with the innovation accessible. Along these lines of working doesn't deal with this well" (Bowes, J.). This procedure doesn't have its own particular

During this phase, the formally controlled and focused testing is performed to uncover errors and bugs in the IT solution that need to be resolved.

Today’s world market is much faster. Every industry is now become the result orientated. They need results in quick time. Like any other industry IT industries also force to make the changes in concepts and techniques they were using traditionally. The traditional models like waterfall, Incremental model, RAID model are not useful for most of the current project requirement. Nowadays project requirements depend on many other unstable concepts, which make the project less predictable. Because of these entire unpredictable project, agile becomes the first choice of most of the clients. The agile software development methods are more adaptive approach, while conventional/traditional software development methods are predictive approach. In traditional method all the project development plan is created before starting the actual development. Once the designing is completed we can’t make changes. On the other hand an agile methodology has the provision to acquire such changes even after the coding is started. Agile relies more on the incremental, iterative development cycles. Agile methodology software is developed in the small periods. Agile is for the projects whose requirements are not fully discovered, projects where output is not predictable. This makes the agile methodology more suitable for the current market situation.

Agile Software Development is a set of principles that have revolutionized the software development industry. They "seek alternatives to traditional project management" acting as "an alternative to waterfall, or traditional sequential development." (The Agile Movement, agilemethodology.org) It is thought that Agile came to be with the introduction of the Agile Manifesto, but their origination dates back much further.

Understanding the Agile Methodologies in Project Management (including the scrum concepts) and help prepare the road map for Intelligrated’s transition to ‘Agile’ methodologies from the traditional waterfall approach.