Rapid Application Development Utilizes An Iterative Approach

1745 Words7 Pages
Rapid application development utilizes an iterative approach to quickly get functional software deployed to end-users and repeats this process to fine tune the product to meet the needs of the user. It relies heavily on interaction and communication with stakeholders to ensure that what is being designed meets the needs of those individuals. Development cycles are timeboxed into small pre-defined periods where development provides stakeholders with a demonstration of useable software at the end of the period. RAD shortens the phases of software development to be able to more quickly react to changing priorities. What is delivered to stakeholders are fully functional parts of a larger system which allows users to provide feedback which is…show more content…
As the project progressed, there were growing pains as developers and stakeholders found that a lack of communication caused issues in what was being delivered. After some environmental changes caused a major revision of the project, the agency found that the use of RAD was slowing being accepted by more workers. Overall the large project, which would typically be considered a bad area to apply RAD, had some initial growing pains but the flexibleness of RAD helped in adjusting course when major changes needed to happen. As stakeholders became more familiar with the RAD processes, some of the growing pains began to subside and employees began to see the benefits of utilizing this methodology. Agile methodologies provide businesses with a way to quickly react to changes in their environment. By delivering small portions of code over the course of a few weeks, developers can provide end-users with useable functionality on an ongoing basis as they move closer to the goal of providing the complete software. By being more reactive to changes, such as new requirements or changes in priority, agile allows development teams to be able to be more responsive and to provide customers with revised applications that are based on feedback that they have previously provided. Agile models, such as XP, are geared towards cost savings
Open Document