UPI Study › Courses › System Analysis and Design › Free lessons › Lesson 3.5 Free with a free account
Joint Application Development: Strengths and Limitations
System Analysis and Design · Chapter 3: Agile Methods and Rapid DevelopmentSection 3.5 · lesson 19 of 698 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of System Analysis and Design.
Lesson complete
Earn the 3 college credits for System Analysis and Design
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Inside JAD: Definitions, Stages, and Techniques →← How Requirements Are Gathered and Analyzed in the SDLCNext lesson: Inside JAD: Definitions, Stages, and Techniques →
In this lesson
Strengths, limitations, and when a workshop beats interviews.
- Define JAD and describe how a JAD workshop is run
- Explain its benefits: speed, user buy-in, fewer misunderstandings
- Identify its limitations, and how facilitators mitigate each
- Compare JAD with one-on-one interviews for a given situation
Transcript
Everything said in the video, section by section (1,011 words). Read along, or search it.
Agile Methods and Rapid Development
Joint Application Development
In chapter two, we gathered requirements one person at a time, through interviews. This section looks at a different approach. Joint application development, usually called JAD. Instead of meeting stakeholders separately, JAD brings them together in one room. We will see how a JAD workshop runs, what it does well, where it struggles, and when it beats a series of interviews.
What JAD Is
Everyone in One Structured Workshop
Joint application development gathers requirements in a single, structured workshop. It brings together users, managers, sponsors, and subject-matter experts. Rather than collecting their input one person at a time, it collects it together. A trained facilitator runs the session. The facilitator keeps discussion on track, and makes sure every voice in the room is heard. A dedicated scribe records the decisions the group reaches. The output of a well-run session is a set of requirements the participants have already discussed, debated, and agreed to together. That last part is the point. Agreement happens during the session, not after it.
Figure 3.5
One Session vs. Many Interviews
Here is the difference in shape. On the left, a JAD session. Users, managers, the sponsor, and subject-matter experts all connect to one facilitated session. Everyone hears everyone else, at the same time. On the right, separate interviews. Each stakeholder talks only to the analyst, in a different meeting. Then the analyst has to reconcile all of those conversations afterward, alone. Every benefit and every limitation of JAD comes from that difference.
The Case for JAD
3 Benefits, One Cause
JAD's advantages come directly from putting the right people in the same room at the same time. The first is speed. JAD consolidates what could be weeks of separate interviews and follow-up emails, into one session, or a short series. That happens because conflicting answers get resolved in the room. The analyst is not left chasing clarification afterward. The second is stronger user buy-in. Users who help define a requirement are more likely to accept the system, that is eventually built from it. Participating in the decision, not just being asked for opinions afterward, is what builds that ownership. The third is fewer misunderstandings. Every participant hears the same explanation at the same time, and can correct a misreading immediately. Nothing passes through several rounds of one-on-one retelling before it reaches the analyst's notes.
Limitations (1 of 2)
Cost and Groupthink
The same structure that makes JAD fast also creates its main weaknesses. Each one has a standard mitigation a facilitator applies. The first is cost. Pulling several stakeholders away from their regular work, sometimes with travel, is expensive. The mitigation is to invite only the people whose input is essential, keep the agenda tight, and hold the shortest session that still covers the scope. The second is groupthink. Participants may quickly agree with the group, or with a senior person's view, rather than raise a real concern. The facilitator stays neutral, and uses techniques such as round-robin input, so quieter participants are asked directly. And the facilitator separates generating ideas from evaluating them, so ideas are not judged before they are heard.
Limitations (2 of 2)
Dominant Voices and Scheduling
The third limitation is dominant voices. A vocal participant, or a senior stakeholder, can take up most of the airtime and steer the outcome. The facilitator actively manages turn-taking, and redirects the discussion back to people who have not yet weighed in. The fourth is scheduling difficulty. Coordinating a shared block of time from several busy stakeholders is often the hardest logistical step. The mitigation is to book the session well in advance, and keep it as short as the scope allows. And to send pre-reading, so meeting time is spent deciding, not explaining background. Notice the pattern. Every weakness is the flip side of a strength.
Head to Head
JAD vs. One-on-One Interviews
So how does JAD compare with one-on-one interviews directly? On time, JAD concentrates gathering into one or a few sessions. Interviews spread it across many meetings. On consistency, JAD is high, because everyone present hears and agrees to the same requirement. With interviews, it is lower. The analyst must reconcile statements that were never compared against each other. On conflicting needs, JAD surfaces them in the room, where they can be resolved. With interviews, conflicts may not surface until the analyst compares notes, sometimes well after the interviews. On sensitive topics, the balance flips. A group setting can make some participants less willing to speak candidly. A private interview often makes them more comfortable. On cost, JAD has a higher upfront cost, needing several people's time at once. Interviews cost less per meeting, but demand more total analyst hours to conduct and reconcile.
Choosing
When JAD Fits - and When It Does Not
So when should you use JAD? It works best when several conditions hold at the same time. The requirement affects multiple stakeholders whose needs must align. The timeline rewards fast consensus over drawn-out back-and-forth. User buy-in matters for the system's eventual adoption. And the key people can realistically be gathered in one place, at one time. Interviews remain the better choice in three situations. When the topic is sensitive. When a single stakeholder holds deep, specialized knowledge that does not need group input. Or when getting everyone together would delay the project far longer than a series of separate meetings. JAD is a powerful tool. It is not a universal replacement for interviews.
Key Terms
The Vocabulary of This Section
Let's lock in the key terms. Joint application development, or JAD, gathers requirements through a single facilitated workshop. The facilitator runs the session, keeps discussion on track, and makes sure every voice is heard. The scribe records the decisions the group reaches. Groupthink is the tendency to agree with the group, or a senior person, instead of raising a real concern. And round-robin input means asking each participant directly, so quieter voices are heard.
Key Takeaways
What to Carry Forward
To pull this together. JAD gathers requirements through a single facilitated workshop, instead of separate one-on-one interviews. Its benefits, speed, user buy-in, and fewer misunderstandings, all come from putting stakeholders in the same room. Its limitations, cost, groupthink, dominant voices, and scheduling, each have a standard mitigation. JAD produces more consistent understanding than interviews do. But interviews can be better for sensitive topics, or for hard-to-schedule participants. And JAD fits best when requirements affect multiple stakeholders, buy-in matters, and the key people can be gathered together.
About System Analysis and Design at UPI Study
System Analysis and Design (Computer Science 390) is a self-paced online course of 69 video lessons in 9 chapters, from the analyst's role and requirements to UML modeling, interface and database design, testing, maintenance and project management. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →
Why take it here
Why students take System Analysis and Design with UPI Study
Where the credit goes
Universities that work with NCCRS
System Analysis and Design carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Joint Application Development: Strengths and Limitations
How is a joint application development (JAD) workshop run?
What are the benefits of joint application development?
What are the disadvantages of JAD sessions?
When is JAD better than one-on-one interviews?
About the System Analysis and Design course
How many college credits is System Analysis and Design?
How much does System Analysis and Design cost and what is included?
Which universities accept UPI Study credits?
How long does System Analysis and Design take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in System Analysis and Design.
69 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →