JAD is an iterative approach to requirements gathering. The Joint Application Developer Process is one that enables the collaboration of the IT communication and the business community in order to empower the requirements collection process. The use of JAD for requirements specification gathering were seen to lead to decreased development time and end user changes, hence it also has an impact on the costs and errors, too (Matthews, 2007). Usually the JAD is applied in the early stage of the project development cycle being a part of the requirements specification collections. The advantage of using the JAD approach was that it enabled the better divisions of the application into smaller versions, although I believe in this project we could have still worked on a more modular approach. The application work was divided between the team as is the usual case with JAD. The work was so divided that the risks were also identified and presented to each of the team members. Usually a typical JAD work meeting is conducted with that of a JAD Facilitator, who acts as a guide for the meet, a JAD documentor, business experts, technical support, the project manager and executive sponsor. The meet we held was more informal in respect. JAD uses an iterative method which enables all the team members to understand the concerns of SRS and also the requirements in a more thorough way. The project deliverables were identified earlier on and the role of participants, the role of the meetings, the schedule of the meetings and more were decided earlier on too. This helped in prioritizing tasks and getting the whole project setup read in an efficient way. JAD focus groups should have been used but given the time, we only worked with general level meetings (Matthews, 2007).
Agile Methodologies: The agile methodology is also an iterative methodology where the focus is on the requirements gathering process with more priority given to the communication processes. This form of a requirements gathering process holds benefits similar to the JAD, however could turn into a very lengthy process soon (as much as a year or more based on the system model being considered for implementation. Agile in contrast with the JAD however presents a high level requirements view that is more useful for more experienced developers. However, the JAD is more suited for developers in the making. Furthermore, there are chances of greater risks when using the Agile methodology if the developer does not understand its proper use (PwC, 2014). There are not much issues like that in JAD. So given an option to use the Agile method of requirements gathering and the specification development, I would say I would use JAD once again.