UPI Study › Courses › System Analysis and Design › Free lessons › Lesson 3.6 Free with a free account

Inside JAD: Definitions, Stages, and Techniques

Name: 3.6 Inside JAD: Definitions, Stages, and Techniques — System Analysis and Design
Uploaded: 2026-09-28T09:41:02+00:00
Duration: 7 min 26 s
Description: Where it came from, who is in the room, the 4 stages, and how facilitators keep it working

System Analysis and Design · Chapter 3: Agile Methods and Rapid DevelopmentSection 3.6 · lesson 20 of 697 min · free with a free account

← Joint Application Development: Strengths and Limitations Next lesson: Rapid Application Development: Definitions, Toolkits, and Frameworks →

Earn 3 college credits for System Analysis and DesignRecommended for credit by NCCRS · Computer Science 390 · self-paced · one payment, lifetime access

Enroll in System Analysis and Design · $250 →Download the syllabus (PDF)

In this lesson

Where it came from, who is in the room, the 4 stages, and how facilitators keep it working.

Define JAD and explain why it was created
Identify the 5 roles in a JAD session and what each contributes
Describe the 4 stages of a JAD project
Explain the facilitation techniques that keep a session productive

Transcript

Everything said in the video, section by section (994 words). Read along, or search it.

Agile Methods and Rapid Development

Inside JAD

The last section weighed JAD against interviews. This one goes inside JAD itself. We will see where it came from, and the five roles that make up a session. We will walk through the four stages of a JAD project. And we will look at the facilitation techniques that keep a session from falling apart.

Origins

Why IBM Created JAD

Joint application development is a structured approach to gathering requirements. Business users, managers, and IT staff meet together in facilitated workshops, rather than through a series of separate interviews. The approach was developed by IBM in the late nineteen seventies. IBM had noticed a problem. Requirements gathered interview by interview often contradicted each other, by the time analysts tried to combine them. Bringing everyone into the same room at the same time was a direct answer to that problem. The idea behind it is straightforward. Disagreements about what a system should do surface faster, and get resolved more cheaply, when the people who disagree talk directly. The alternative is an analyst relaying each side's position back and forth, after the fact. That relay is slow, and something gets lost at every step.

Who Is in the Room

5 Participant Roles

A JAD session works only if each participant sticks to a defined role. Five roles make up a typical session. The facilitator runs the session, and keeps discussion on track. The facilitator stays neutral on the actual requirements, so no one feels the outcome was steered. The scribe documents decisions, requirements, and open issues in real time. That record is what the session's outputs will be built from. The executive sponsor opens the session with the project's purpose and authority. The sponsor also steps in to resolve disagreements that need a decision above the group's own authority. Users describe how work is actually done today, and confirm or correct requirements as they are proposed. And IT staff translate business needs into requirements that are technically feasible. They also flag constraints the business side may not be aware of.

Why Neutrality Matters

The Facilitator Does Not Decide

One of those roles deserves a closer look. The facilitator. The facilitator runs the room, but does not decide what the system should do. Why does that neutrality matter so much? Because if the facilitator steers the outcome, participants feel it was decided for them. And the buy-in that JAD exists to create is lost. So when a disagreement needs a decision beyond the group's authority, it goes to the executive sponsor. The facilitator protects the process. The sponsor holds the authority. Keeping those apart is what makes the session trusted.

Figure 1

The 4 Stages of a JAD Project

A JAD session is only one part of a larger process. The full effort runs through four stages. In planning, the project's scope and objectives are defined. The right participants and a facilitator are identified, and the session is scheduled. In preparation, the facilitator and analysts gather background information. They prepare an agenda, along with diagrams or rough prototypes, to give the session a concrete starting point. Then comes the session itself. This is the structured workshop, where requirements are proposed, discussed, and agreed on by the group. Finally, follow-up. The scribe's notes are turned into a formal requirements document. That document is circulated back to participants, for review and sign-off.

Before and After

Where JAD Projects Succeed or Fail

Notice that two of the four stages happen outside the room. That is where many JAD projects succeed or fail. Good preparation gives the session something concrete to start from. A diagram, or a rough prototype, is far easier to react to than a blank page. Good follow-up turns agreements into something durable. Without it, the decisions stay as notes. With it, they become a formal document that participants review and sign off. A great session with weak preparation, or no follow-up, can still leave the project without usable requirements.

Facilitation Techniques (1 of 2)

Generating Ideas Fairly

A JAD session can fall apart just as easily as it can succeed. Facilitators rely on a small set of techniques to keep discussion productive and fair. The first is brainstorming. It generates a wide range of ideas quickly, by deliberately withholding criticism until the ideas are on the table. The second is the nominal group technique. Participants write down their ideas silently, before discussing them aloud. That way, quieter voices and unpopular ideas get heard, before group opinion forms. The third is live whiteboarding, or prototyping. It turns an abstract requirement into something visible, such as a rough screen sketch. Then participants react to something concrete, instead of a description.

Facilitation Techniques (2 of 2)

Keeping the Session Moving

Two more techniques keep the session moving. The parking lot captures an important but off-topic issue in writing. It gets addressed later, without derailing the current discussion. And nobody feels their concern was dismissed. It is on the list. Timeboxing assigns a fixed amount of time to each agenda item. That way, one topic cannot consume the entire session, at the expense of the rest of the agenda. Look back at the limitations from the last section. Groupthink, dominant voices, and lost time. Each of these techniques is aimed squarely at one of them.

Key Terms

The Vocabulary of This Section

Let's lock in the key terms. Joint application development is a structured approach to gathering requirements, through facilitated workshops with business users, managers, and IT staff together. The facilitator is the neutral participant who runs the session, without steering the requirements decided. A parking lot is a running list of off-topic but important issues, set aside to be addressed later. Timeboxing means assigning a fixed amount of time to a topic, to keep the session moving through its full agenda. And the nominal group technique has participants write ideas silently, before group discussion.

Key Takeaways

What to Carry Forward

To pull this together. JAD replaces a series of separate interviews with facilitated workshops, bringing business and technical stakeholders together. Five roles, the facilitator, scribe, executive sponsor, users, and IT staff, each contribute something the session cannot function without. A JAD project runs through four stages. Planning, preparation, the session itself, and follow-up. And facilitation techniques keep a session productive, and fair to everyone in the room. Brainstorming, the nominal group technique, live prototyping, a parking lot, and timeboxing.

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 →

Compare: Software Engineering vs Systems Analysis

Why take it here

Why students take System Analysis and Design with UPI Study

From business problem to working systemSystem Analysis and Design teaches how analysts study a business need and turn it into a system design: requirements, UML and data-flow models, interface and database design, implementation and project management. It is a core course in information systems and IT degrees.

Credit at a fraction of the priceThe same 3 credits can cost $750 or more at a US college. Here it is one payment, self-paced, with lifetime access.

Finish your degree soonerTransfer credits reduce the courses you still owe, so you can graduate earlier or lighten a heavy semester.

Strengthen an applicationA completed college-level course on an official transcript shows admissions and scholarship committees you can do the work.

Study on your own scheduleNo start dates, no deadlines. Watch the lessons, practice, and take the final when you are ready.

130,000+students helped with college creditsACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

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 Inside JAD: Definitions, Stages, and Techniques

Who created joint application development, and why?

Joint application development was developed by IBM in the late 1970s to fix a problem with interview-based requirements gathering. Requirements collected one interview at a time often contradicted each other by the time analysts tried to combine them. Bringing business users, managers, and IT staff into the same facilitated workshop lets disagreements surface and get resolved directly, rather than through an analyst relaying positions back and forth.

What are the roles in a JAD session?

A typical JAD session has five roles: facilitator, scribe, executive sponsor, users, and IT staff. The facilitator runs the session and stays neutral on the requirements. The scribe records decisions and open issues in real time. The executive sponsor sets purpose and authority and resolves disputes beyond the group's authority. Users describe how work is done today, and IT staff check technical feasibility and flag constraints.

What are the stages of a JAD project?

A JAD project runs through four stages: planning, preparation, the session, and follow-up. Planning defines scope and objectives and picks participants and a facilitator. Preparation gathers background and produces an agenda plus diagrams or rough prototypes. The session is the workshop where requirements are agreed. Follow-up turns the scribe's notes into a formal requirements document that participants review and sign off.

What facilitation techniques keep a JAD session productive?

Common techniques include brainstorming, the nominal group technique, live whiteboarding or prototyping, a parking lot, and timeboxing. Brainstorming withholds criticism until ideas are out. In the nominal group technique, participants write ideas silently before discussing them, so quieter voices are heard. Prototyping makes requirements concrete. A parking lot records off-topic issues for later, and timeboxing limits the time spent on each agenda item.

About the System Analysis and Design course

How many college credits is System Analysis and Design?

System Analysis and Design (Computer Science 390) carries a NCCRS credit recommendation for 3 semester credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.

How much does System Analysis and Design cost and what is included?

$250, paid once, with lifetime access: all 69 video lessons, a practice quiz after each, the graded work and final exam, and an official transcript when you finish. Students who want several courses choose UPI Study PRO instead.

Which universities accept UPI Study credits?

UPI Study has signed partner agreements with universities such as Thomas Edison State University, University of the People and Charter Oak State College, and works with universities such as Penn State, SNHU and SUNY. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities. Use "Find my college" on this page to check yours.

How long does System Analysis and Design take?

It is self-paced with no deadlines. The 69 lessons total about 9 hours of video; most students add reading and practice time and finish in a few weeks to a few months, on their own schedule.

How are the exams done?

Quizzes and assignments are online in the course. The final exam is taken online with proctoring; a person on the UPI Study team checks assignments, usually within two days.

How do my credits reach my college?

When the course shows 100% complete, request the official transcript from your dashboard. It is sent to the college you name, and you can send it to more than one. Check your college first with "Find my college" on this page, or ask Athena.

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.

Enroll in System Analysis and Design →Download the syllabus Every course with PRO →

System Analysis and Design
3 credits · NCCRSEnroll →