This page is part of the ForgeSDLC knowledge base — an AI-assisted, human-directed methodology for taking product work from concept to production. For the core operating model and vocabulary, see Forge SDLC overview and What is ForgeSDLC?.
RAD (Rapid Application Development)
What it is
Rapid Application Development (RAD) is a software development methodology introduced by James Martin in 1991 that emphasizes rapid prototyping and iterative delivery over extensive upfront planning. RAD prioritizes user feedback on working prototypes over detailed specifications, and uses time-boxed development cycles (typically 60–90 days) to produce functional software quickly.
RAD was a significant departure from Waterfall thinking in the early 1990s and influenced many later Agile methods. While the specific RAD methodology is less commonly prescribed today, its core ideas — prototyping, user involvement, timeboxing, and iterative refinement — are foundational to modern iterative development.
Process diagram (handbook)
Requirements planning → User design (prototyping) → Construction (rapid build) → Cutover (deployment). User design and construction iterate based on feedback.
Authoritative sources (external)
| Resource | Executive summary (why it's linked here) |
|---|---|
| Wikipedia — Rapid application development | Stable overview of RAD — phases, tools, comparison with traditional approaches. |
Book: James Martin, Rapid Application Development (1991) — the canonical text.
Four phases
| Phase | Purpose |
|---|---|
| Requirements planning | High-level requirements through workshops; equivalent to JAD (Joint Application Development) sessions. |
| User design | Users work with developers to create prototypes; rapid iteration on UI and workflow. |
| Construction | Build, test, and integrate based on prototype feedback; code generation tools encouraged. |
| Cutover | Data conversion, testing, deployment; user training and system transition. |
Key characteristics
| Characteristic | Description |
|---|---|
| Prototyping | Working prototypes replace detailed specifications; "show, don't tell." |
| User involvement | Active, continuous user participation throughout development. |
| Timeboxing | Fixed-duration development cycles (60–90 days); scope flexes. |
| Code generation | Originally promoted CASE tools and code generators to accelerate development. |
| Small teams | Typically 2–6 developers per RAD team. |
Mapping to this blueprint's SDLC
| RAD idea | Blueprint touchpoint |
|---|---|
| Requirements planning (JAD workshops) | Phase A: discovery, stakeholder workshops. |
| User design (prototyping) | Phase B–C: specify and design through working prototypes. |
| Construction | Phase C–D: build and verify rapidly. |
| Cutover | Phase E–F: deploy, train, transition. |
| Timeboxing | Cross-phase: fixed calendar windows with variable scope. |
RAD's legacy in modern methods
| Modern concept | RAD origin |
|---|---|
| Sprints / iterations | RAD timeboxes |
| User stories and demos | RAD user involvement and prototyping |
| Low-code / no-code platforms | RAD code generation tools |
| MVP (Minimum Viable Product) | RAD's "good enough" prototype philosophy |
| Agile in general | RAD was one of the first systematic alternatives to Waterfall |
Agentic SDLC: RAD + agents
| Topic | Guidance |
|---|---|
| Prototyping | Agents excel at rapid prototype generation — RAD's core strength is amplified. Ensure prototypes remain disposable. |
| User involvement | Agents cannot replace user feedback sessions; they can prepare prototypes for user review. |
| Code generation | Modern agents are the spiritual successor to RAD's CASE tools — more capable but same risk of "generated code nobody understands." |
Further reading
- Wikipedia — Rapid application development — Overview.
- Companion: Agile umbrella, Spiral (also prototyping-oriented), Shape Up