{"id":204,"date":"2009-12-07T18:59:00","date_gmt":"2009-12-07T18:59:00","guid":{"rendered":"http:\/\/joapen.com\/blog\/2009\/12\/07\/rad-or-waterfall\/"},"modified":"2009-12-07T18:59:00","modified_gmt":"2009-12-07T18:59:00","slug":"rad-or-waterfall","status":"publish","type":"post","link":"https:\/\/joapen.com\/blog\/2009\/12\/07\/rad-or-waterfall\/","title":{"rendered":"RAD or Waterfall?"},"content":{"rendered":"

Dynamic Systems Development<\/span><\/em><\/strong> (or DSDM) is a method based on the assumption that nothing is perfect first time, but that 80% of the solution can be produced in 20% of the time it would take to produce the whole solution.<\/p>\n

It is highly iterative, all steps can be re-visited, therefore the current step need be completed only enough to move to the next step. It builds on the best practices of traditional waterfall development approaches, and includes the controlled use of new techniques without allowing RAD to revert back to hacking out code and documenting it on the back of a cigarette packet!
\"\"<\/a><\/p>\n

The DSDM Consortium, launched in January 1994, is creating an industry-standard, public domain method for Rapid Application Development<\/span><\/em><\/strong> (RAD). It has over 50 members including corporate users such as: British Airways, Allied Domecq, American Express and J P Morgan Investment Management and software houses\/tools vendors such as: Logica, Data Sciences, Cognos, Sapiens.<\/div>\n
In the early 1990s<\/u> a new term \u2018Rapid Application Development\u2019 (or RAD) was launched upon an unsuspecting IT industry. RAD was intended to be different from the classical, sequential (or \u2018Waterfall\u2019) methods for application development.<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
<\/div>\n
RAD grew as a movement in a very unstructured way; there was no commonly agreed definition of a RAD process, and many different vendors and consultants came up with their own interpretation and approach.<\/div>\n
<\/div>\n
<\/div>\n