discussion

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 developing an application using Agile methodology. So far, I have found this method to be superior to waterfall methodologies. The most important strength of using Agile is the ability to adapt to new requirements and issues that arise during development. We have already experienced requests for new requirements from the product owners. With other methodologies this would be an issue, but with Agile we are able to simply incorporate the new tasks in the next sprint. I believe one of the main weakness of Agile would be the amount of meetings that are required. Before each sprint, task creation, delegation, and estimation takes up quite a bit of time. Also, sprint retrospectives are conducted afterwards and help the developers share what worked and didn't work during the sprint. At times, it becomes hard to be productive when there are meetings throughout the day. However, I would say that the meetings are necessary in order to keep communication strong between developers so that everyone is on the same page.

On the other hand, waterfall methodology has its own strengths and weaknesses. With waterfall, requirements are gathered at the beginning of the project, and there is not much room for change. Because waterfall relies so heavily on having the requirements upfront, it can be considered both a strength and a weakness. It is a strength because with all of the project milestones clearly planned, the developers are on the same page and know what needs to be done. This can also be considered a weakness due to the lack of flexibility. If there needs to be new functionality, or if the product owner simply doesn't like the final outcome, there is not much that can be done throughout development. While the learning curve to working with Agile is a little steeper than Waterfall, I believe it is the best choice for developing complex systems. 2.

When a project is capable of responding to changing requirements and priorities by using incremental work processes we place them under the umbrella term of âAgileâ. There are however; many different types of Agile methodologies. Although, they share common characteristics, they also have unique processes that make each one of them different. âAgile Methodologies are people-oriented more than process-oriented. â Some agile methodologies are Scrum, Extreme Programming (XP) which is one of the most used agile methodologies, and Adaptive Software Development (ASD) that emerged from Rapid Application Development (RAD) and occurs in four phases. All projects handled under the agile methodology require constant, regular feedback. Agile project management is usually ideal for smaller software projects and/or those with accelerated development schedules. They are perfect for and commonly used for in-house teams. If your team is self-motivated and work well together, team members can rapidly adjust things as needed. One problem with the agile method is that they are often times so flexible; your ending product does not resemble your initial vision. Software products or applications that are not set in stone are best served by a flexible agile methodology.

Maybe Joint Application Development (JAD) could be considered Agile, it is a development process that once was all the rave and then began to die out in the late 1990âs. The JAD approach used customer involvement and group sessions to accurately identify the user's requirements of the business need and to jointly develop a solution. JAD was proven successful when applied to new systems, Enhancements to existing systems, System conversions, and Purchase of a system. When the school where I work decided to change the course material for an introductory computer course, I was one of the individuals who sat on the JAD team which reviewed and tested the new software applications that would replace the existing application.

Initially processes were geared towards creating a flawless, perfect product in compliance with software quality standards. The waterfall method is possibly the most popular and the one thought of first when traditional approaches are mentioned. Although rigid and linear, this methodology does have its place and serve its purpose. This methodology has specific goals for each phase of development and each phase must be completed prior to the next phase beginning. Once a phase is completed, there is no turning back. If the requirements for the finished project are complete, clear and stable, the effort required to complete the project can be easily predicted, and you have successfully completed previous projects similar to the one youâre about to start, this is the methodology that you may want to use for your project. Waterfall method usually leads to the project being delivered on time because each phase has been planned in detail. The downside to this is that it does not leave any room for changes and/or revisions that often become necessary with any project. Physical objects such as buildings or household products with very clear requirements and very clear stakeholder expectations benefit best from a more 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