Gurjot Singh

JAD concept is based on 4 ideas:

The users who do the job have the best understanding

of that job.

The developers have the best understanding of

technology.

The best software comes out IF all groups work as

equals and as one team with a single goal that all agree

upon.

JAD Philosophy

Gurjot Singh

JAD history

Collecting requirements is an inherently

difficult problems.

IBM developed the JAD technique in the

1980's. It is considered as the best method for

collecting requirements.

A typical JAD project is from 3 to 6 months.

For large-scale project, it is broken down into

sections with separate JAD’s for each.

Gurjot Singh

JAD ?

JAD is a technique that allows the

management, developments and customer

groups to work together to build a

product.

It is a series of highly structured

interview sessions aimed at reaching

consensus on a project’s goal and scope.

Gurjot Singh

Why JAD ?

Problem: Friction between developers and users; lack

of user inputs.

Solution: JAD actively involves users and management

in the development project as a group.

Problems: Inadequate requirement and design.

Solution: JAD helps to avoid the requirements from

being too specific and too vague, both of which cause

trouble during implementation and acceptance.

JAD reduces the amount of time required to develop

systems since it eliminates process delays and

misunderstandings.

JAD helps to overcome some people & process flaw(s) in

Software Development.

Gurjot Singh

Why JAD ? Cont.

By properly managing the management and the

appropriate users, the risk is mitigated while

cutting implementation time by 50%.

Able to gather a number of interested users to

meet together in group sessions.

This technique could result in fewer group sessions

than individual interview sessions therefore, saving

resources.

Gurjot Singh

JAD – a 5 phased approach

Project Definition

Research

Preparation

JAD sessions

Final Documentation

Gurjot Singh

JAD Participants

Executive Sponsor

Facilitator

Scribe

Full-time participants

On-call participants

observers

Gurjot Singh

Gurjot Singh

JAD Participant - Sponsor

Role :

Controlling the funding, to give full support to the

systems project by encouraging designated users to

willingly & actively participate.

Decision maker :

Sponsor makes final decisions regarding go or no-go

direction of the project.

Gurjot Singh

JAD Participant - Facilitator

Role:

Plan the JAD session, conduct the session, and to follow

through on the results.

Establish the “ground rules” that will be followed

during the meeting and ensure that the participants

abide by these rules.

Guides the team throughout the process.

Gurjot Singh

JAD Participant - Scribes

Role: Responsible for keeping records pertaining to

everything discussed in the meeting.

These records are published & disseminated to

attendees after the session in order to maintain the

momentum that has been established .

One or more scribes for a JAD sessions.

Gurjot Singh

JAD Participant - Full-time part.

Everyone involved in making decisions about the data

warehouse.

JAD Participant – On-call part.

Persons affected by project, but only in specific areas.

JAD Participant – Observers

Persons who would like to sit in on specific sessions without

participating in decision making as a member of other dept.

Gurjot Singh

Tips from JAD experts

Park it!

Write offending issues down and address them at a more appropriate time.

Get it in writing Document as much of the project as you can.

Do it together

Set time frames and deadlines jointly.

Gurjot Singh

Gurjot Singh