Joint Application Development (JAD)

Joint Application Development, or JAD, is a process originally developed for designing a computer-based system. It brings together business area people (end users) and it (information technology) professionals in a highly focused workshop. The advantages of JAD include a dramatic shortening of the time it takes to complete a project.

Uploaded by

swamijee_kakarl8261

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

100% found this document useful (1 vote)

979 views

Joint Application Development (JAD)

Uploaded by

swamijee_kakarl8261

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 12

Joint Application Development

1
Agenda: Joint Application
Development
 Introduction
 Origin
 Evolution
 Other Names
 Basic Components of a JAD Session
 Guidelines for a Successful JAD
 Summary

2
Introduction
 What is Joint Application Development?

 Joint Application Development, or JAD, is a process originally

developed for designing a computer-based system. It brings
together business area people (end users) and IT
(Information Technology) professionals in a highly focused
workshop. The advantages of JAD include a dramatic
shortening of the time it takes to complete a project. It also
improves the quality of the final product by focusing on the
up-front portion of the development lifecycle, thus reducing
the likelihood of errors that are expensive to correct later
on.

3
Introduction (Cont.)
 JAD Scope
1. The JAD should cover the complete development life cycle of a
system.
2. The JAD is usually a 3 to 6 month well-defined project.
3. For large-scale projects, it is recommended that the project be
approached incrementally, and that separate JAD's be used for
each increment.

4
Origins
 JAD was developed by Chuck Morris and Tony Crawford of IBM
 Crawford led several workshops to prove the concept
 JAD became widely accepted in many companies, including the data
processing industry
 JAD definition according to Crawford: an interactive systems
design concept involving discussion groups in a workshop setting

5
Evolution
 As JAD attained popularity in the 80's, people started to use the
term to describe different things.
 Workshop Techniques
 Brainstorming Sessions
 Motivational Meetings

 As the popularity of JAD grew, its usage expanded to functions

other than the requirement gathering in the system development
life cycle(SDLC). It is now used in all phases of SDLC and is
defined as a system development method.

6
Evolution (Cont.)
 Who uses JAD?
 Today, JAD is commonly used in several areas
1. Project Management
2. IS Architecture Definition
3. Strategic Business Planning
4. Re-engineering Business Processes

7
Other Names
1. Accelerated Design
2. Facilitated Meetings
3. Facilitated Sessions
4. Facilitated Team Techniques
5. Facilitated Work Sessions
6. Group Design
7. Interactive Design
8. Interactive JAD
9. Joint Sessions
10. User Centered Design
8
Basic Components of a JAD
Session
 JAD participants typically include:
– Project sponsor
– Project lead
– Facilitator
– Scribe
– Participants
– Observers

 Key Steps:
– Identify Project Objectives and limitations
– Identify critical success factors
– Define project deliverables
– Define the schedule of workshop activities
– Select the participants

9
Basic Components of a JAD
Session (Cont.)
Key Steps:
–Prepare the workshop material
–Organize workshop activities
and exercises
–Prepare, inform, educate the
workshop participants
–Coordinate workshop logistics

10
Guidelines for a Successful
JAD
 A clear purpose shared by all team members - the
project charter
 A diverse team, representative of all areas effected
by this project.
 Every person in the group has equal responsibility
and decision making power.
 Every idea is valuable.
 Participation by everyone is very important.

11
Benefits Of JAD
– Reduced system development time
– Improved system quality and productivity
– Reduced system cost
– Enhanced communication and relationship
between business end-users and IT personnel
– Enhanced education for participants and
observers