Thursday, March 24, 2011


Joint Application Development - How to handle JAD Efficiently ?

Chuck Morris and Tony Crawford, both of IBM, developed JAD in the late 1970s and began teaching the approach through workshops in 1980.

JAD Philosophy
JAD Concept
What is JAD?
JAD is a technique that involves the client or end user in the design and development of an application, through a succession of collaborative workshops called JAD sessions.

In contrast to the traditional approach, JAD leads to shorter development period and better client satisfaction, both of which stem from the constant involvement of the client throughout the development process. JAD sessions are structured and focused and participants of these sessions would typically include a facilitator, end users, developers, observers, mediators and experts.

JAD process generally used in the prototyping life cycle area of the Dynamic Systems Development Method (DSDM) to collect business requirements while developing new application for a client.

When to use JAD?
JAD can be successfully applied to a wide range of projects, including the following:
  • New systems
  • Enhancements to existing systems
  • System conversions
  • Purchase of a system
Key participants
Participants of a JAD Session

How to Plan and Conduct an efficient JAD Session
  • Most JAD sessions span a three- to five-day time period and occasionally last up to two weeks.
  • The success of any JAD session is dependent upon proper planning and effectively carrying out that plan.
  • To successfully conduct the session, the leader should follow these guidelines:
  • Avoid the use of technical jargon.
  • Apply conflict resolution skills.
  • Allow for ample breaks.
  • Encourage group consensus.
  • Encourage user and management participation without allowing individuals to dominate the session.
  • Make sure that attendees abide by the established ground rules for the session.

How to handle JAD Sessions Efficiently

Handling a JAD Session Efficiently

The end product of a JAD session is typically a Formal written document:
  • This document is essential in confirming the specifications agreed upon during the session(s) to all participants.
  • The content and organization of the specification is obviously dependent on the objectives of the JAD session.
  • The analyst may choose to provide a different set of specifications to different participants based upon their role.


nishideep said...

This topic gives me a very clear picture of JAD.
Thanks Abhijeet

birkin bag hermes said...

Learning to be a blogger is much more difficult than I ever expect it to be.

Anonymous said...

Sometimes I poop

idle said...

got a lot of help, thx

KPL Tech said...

This is really a good source of information, I will often follow it to know more information and expand my knowledge, I think everyone should know it, thanks. Get more info about business intelligence reporting

Post a Comment