ANSWER

JAD stands for Joint Application Development. JAD is a requirements-definition and software system design methodology in which stakeholders, subject matter experts (SME), end-users, business analysts, software architects and developers attend collaborative workshops (called JAD sessions) to work out a system's details.

The JAD approach, in comparison with more traditional practices, is thought to lead to faster development times and greater client satisfaction, because the client is involved throughout the development process

The focal point of the JAD process is the series of JAD sessions that are attended by stakeholders, executives, SME’s, end-users, business analysts, software architects and developers. It is essential that the roles, responsibilities, and rules for the JAD sessions are well defined and communicated in advance to all participants.

Some typical roles found in a Joint Application Development (JAD) session include: 

• Facilitator – 1 (only one) - usually a Senior Business Analyst - facilitates discussions, enforces rules,

• Scribe – 1 or 2 – sometimes more junior BAs – take meeting notes and clearly document all decisions,

• End users – 3 to 5, attend all sessions,

• Technical Experts – 1 or 2, question for clarity and give feedback on technical constraints,

• Tie Breaker – Senior manager (executive) - breaks end user ties, usually doesn’t attend,

• SMEs - Subject Matter Experts, 

• Observers – 2 or 3 - junior BAs, testers, etc. - do not speak.