JAD should be combined with an incremental lifecycle model—such as Evolutionary Delivery, Evolutionary Prototyping, or Staged Delivery (Chapters Chapter 7, Chapter 20, Chapter 21, and Chapter 36)—that delivers part of the software relatively soon after the JAD-design session.
JAD and prototyping (Chapters Chapter 21, Chapter 38, and Chapter 42) appear to be synergistic practices, and the combination can drop creeping requirements below 5 percent (Jones 1994).
If the technical environment supports it, do the prototyping and design work during the JAD-design session in such a way that you can transfer it to the implementation stage. This is easier to do in IS development than in many other kinds of development. JAD is an integral part of James Martin's RAD methodology, and some organizations integrate JAD into a RAD lifecycle supported by ICASE tools. If it makes sense to do that within your environment, plan for that integration during JAD-planning customization.
18.118.20.156