Agile methods are all the rage these days. The new guy in ch

Agile methods are all the rage these days. The new guy in charge at IBM want them to move everything to agile development. Does that work for all kinds of projects? Let’s do a little research into the different agile methods as well as the more traditional approaches. We want to point out the similarities and differences as well as strengths and weaknesses. If possible, try to identify the kinds of projects that would work best with one approach versus the other. this is a discussion and my classmates already posted somthing as examples: 1. At my current job we are developingan application using Agile methodology. So far, I have found this methodto be superior to waterfall methodologies. The most important strengthof using Agile is the ability to adapt to new requirements and issuesthat arise during development. We have already experienced requests fornew requirements from the product owners. With other methodologies thiswould be an issue, but with Agile we are able to simply incorporate thenew tasks in the next sprint. I believe one of the main weakness ofAgile would be the amount of meetings that are required. Before eachsprint, task creation, delegation, and estimation takes up quite a bitof time. Also, sprint retrospectives are conducted afterwards and helpthe developers share what worked and didn’t work during the sprint. Attimes, it becomes hard to be productive when there are meetingsthroughout the day. However, I would say that the meetings are necessaryin order to keep communication strong between developers so thateveryone is on the same page.On the other hand, waterfall methodology has its own strengths andweaknesses. With waterfall, requirements are gathered at the beginningof the project, and there is not much room for change. Because waterfallrelies so heavily on having the requirements upfront, it can beconsidered both a strength and a weakness. It is a strength because with all of the project milestones clearly planned, thedevelopers are on the same page and know what needs to be done. Thiscan also be considered a weakness due to the lack of flexibility. Ifthere needs to be new functionality, or if the product owner simplydoesn’t like the final outcome, there is not much that can be donethroughout development. While the learning curve to working with Agileis a little steeper than Waterfall, I believe it is the best choice fordeveloping complex systems. 2. Whena project is capable of responding to changing requirements andpriorities by using incremental work processes we place them under theumbrella term of “Agile”. There are however; many different types ofAgile methodologies. Although, they share common characteristics, theyalso have unique processes that make each one of them different. “AgileMethodologies are people-oriented more than process-oriented. “ Someagile methodologies are Scrum, Extreme Programming (XP) which is one ofthe most used agile methodologies, and Adaptive Software Development (ASD)that emerged from Rapid Application Development (RAD) and occurs infour phases. All projects handled under the agile methodology requireconstant, regular feedback. Agile project management is usually idealfor smaller software projects and/or those with accelerated developmentschedules. They are perfect for and commonly used for in-house teams.If your team is self-motivated and work well together, team members canrapidly adjust things as needed. One problem with the agile method isthat they are often times so flexible; your ending product does notresemble your initial vision. Software products or applications that are not set in stone are best served by a flexible agile methodology. Maybe JointApplication Development (JAD) could be considered Agile, it is adevelopment process that once was all the rave and then began to die outin the late 1990’s. The JAD approach used customer involvementand group sessions to accurately identify the user’s requirements of thebusiness need and to jointly develop a solution. JAD was provensuccessful when applied to newsystems, Enhancements to existing systems, System conversions, andPurchase of a system. When the school where I work decided to change thecourse material for an introductory computer course, I was one of theindividuals who sat on the JAD team which reviewed and tested the newsoftware applications that would replace the existing application. Initially processes were geared towards creating aflawless, perfect product in compliance with software qualitystandards. The waterfall method is possibly the most popular and theone thought of first when traditional approaches are mentioned.Although rigid and linear, this methodology does have its place andserve its purpose. This methodology has specific goals for each phaseof development and each phase must be completed prior to the next phasebeginning. Once a phase is completed, there is no turning back. If therequirements for the finished project are complete, clear and stable,the effort required to complete the project can be easily predicted, andyou have successfully completed previous projects similar to the oneyou’re about to start, this is the methodology that you may want to usefor your project. Waterfall method usually leads to the project beingdelivered on time because each phase has been planned in detail. Thedownside to this is that it does not leave any room for changes and/orrevisions that often become necessary with any project. Physicalobjects such as buildings or household products with very clearrequirements and very clear stakeholder expectations benefit best from amore traditional methodology such as Waterfall. Still,It is always a good idea to review each methodology to be sure it fits well with your project, look at your requirements, project goals, and objectives. Know what your deliverable needs to look like and the benefits it should provide, and then decide which methodology suits your project needs. please write a discussion like them and give two seperate responds to those two discussions. thanks