How Should Your Software Be Built?
Posted in Strategy & Consulting, Web Application Development, Web Design & Development on June 30th, 2010 by The Savvy CIO – Be the first to commentThere are two major methods of developing software: waterfall and agile. If you’re considering a development project, you should consider how your software should be made.
Waterfall development goes through distinct stages, with requirements gathering in the first stage. In the waterfall method, a group of decision makers think, imagine, script and whiteboard how the system might be used. These working sessions create a set of requirements for the application. After the requirements are set, the waterfall method flows down to future stages of development, testing and deployment.
In contrast, agile development breaks a project down into small stages. Each stage tackles a small area of the application, gathering requirements, building, testing and then putting the growing application into the hands of users. This process allows requirements to emerge over time, as users and developers learn together exactly what the application needs to accomplish.
Waterfall development assumes the requirements of a system can be fully predicted and codified before any development begins. Agile development assumes requirements only fully emerge during the process.
Waterfall development aims at a stationary target. Agile development aims at a moving one.
So which method is best?





