Hi Folks, just wanna start a discussion about RAD and it's prospects. In one of my application we have formed a core Team which dons all of these roles, as & when required - coders, testers, deployers & guys who works in Database. The development is divided into three different segments, which run parallely. As we are following SOA, so it's lot more easier to run work parallelt on Web-client, Web-service, and DB. RAD is followed in the way of requirement gathering->developing->deploying->testing on core modules+component bulidings+Db handling. It's as quick as in weekly fashion. Just wanna share so that, some can give more input on "I think RAD is agile. Do you think so?" [ January 18, 2007: Message edited by: Subhadip Chatterjee ]
To be "agile", to me it at least also had to be *sustainable* (as far as I can tell, many RAD approaches produced messes of code that weren't maintainable in the long run) and produce high quality results.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
I was with you back at the definition problem for RAD. The version I recall was: Build a flashy but empty prototype and then gradually fill in the missing bits until you have a flashy production app. We tried that ... it was horrific. We now almost forbid prototyping in the target technology to be sure that none of the prototype makes it into the system. [ January 19, 2007: Message edited by: Stan James ]
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi