The two literatures agree that the Joint Application Development (JAD) seeks to involve customers and group dynamics to accurately depict users’ views about the product of a business by obtaining a joint solution between the business and the customer. In this way, the JAD helps the management and consumers to avoid cases whereby a too vague or too specific product is produced. In both cases, an event can occur whereby a well-made product is rejected by a customer, simply because of lack of thoroughness, accuracy and consistency with the functional requirements of the so determined use. The two literatures also note that although the JAD technique has been appreciated since its inception in 1970s and formalization in 1984 by the IBM, it can be hampered by certain challenges. For instance, Duggan and Thachenkary (2003) have indicated that conforming behaviors, search behaviors, destructive dominance, elective participation, group think among other problems could hinder the needed independent solution proposals from various parties before a consensus is reached. The book concur that some members of the groups of JAD could make the project suffer traditional problems of having some people dominating the discussion while others becoming reluctant to forward their challenges and objections(Dennis, Wixom & Roth, 2014; Thachenkary, 2003).
Although the book has explicitly illustrated cases in which the JAD becomes much needed, the Duggan and Thachenkary (2003)’s article has not explicitly done so. The book indicates that the JAD technique is most appropriate when the system is still new, need to be converted into another or purchased, and if products are to be enhanced(Dennis, Wixom & Roth, 2014). On participants, there seem to be agreement that four major groups of participants should be involved: facilitators, note takers (scribes), professionals and managers in business and information system, and customers. Managers usually approve or disapprove the results of the meeting. Professionals are needed to answer any query that may result in the course of the meeting. Facilitators are needed in that they plan and conduct the sessions, following through the results so that executives can be thoroughly informed. The scribes are needed to take and keep records of the meeting proceeding so that the executives can be informed well. Customers or product users are needed to communicate their product requirements, prototype designs and acceptance modalities (Dennis, Wixom & Roth, 2014; Thachenkary, 2003). However, the book has added that for a typical JAD session to be sufficient in participants, sponsors and observers have to be included (Dennis, Wixom & Roth, 2014).
References
Dennis, A., Wixom, B.M. & Roth, R.M. (2014).Systems Analysis and Design. New York: John
Wiley & Sons.
Duggan, E.W. & Thachenkary, C.S. (2003). Higher quality requirements: supporting joint
application development with the nominal group technique. Information Technology and Management, 4, pp. 391-408.
