Joint Application Development
Introduction

The chapter will address the following questions:




Can joint applications development be used as alternative factfinding technique throughout systems development, and can it
expedite the process?
What are the typical participants in a JAD session and describe
their roles?
How do you complete the planning process for conducting a JAD
session: including selecting and equipping the location, selecting
the participants, and preparing an agenda to guide the JAD
session?
What are several benefits of using JAD as a fact-finding
technique?
1
Joint Application Development
Joint Application Development

Introduction


Joint application design (JAD) is a process whereby highly
structured group meetings or mini-retreats involving system users,
system owners, and analysts occur in a single room for an extended
period of time (four to eight hours per day, anywhere from one day
to a couple weeks).
JAD-like techniques are becoming increasingly common in
systems planning and systems analysis to obtain group consensus
on problems, objectives, and requirements.
 Therefore, it is more commonly referred to as joint application
development to appropriately reflect that it includes more than
simply systems design.
2
Joint Application Development
JAD Participants

Sponsor


Any successful JAD session requires a single person, called the
sponsor, to serve as its champion.
 This person is normally an individual who is in top
management who has authority that spans the different
departments and users who are to be involved in the systems
project.
JAD Leader (or Facilitator)

JAD sessions involve a single individual who plays the role of the
leader or facilitator.
 The JAD leader is usually responsible for leading all sessions
that are held for a systems project.
3
Joint Application Development
JAD Participants

Users and Managers


These participants are normally chosen by the project sponsor.
 The project sponsor must exercise their authority and
encouragement to ensure that these individuals will be
committed to actively participate.
Scribe(s)

A JAD session also includes one or more scribes who are
responsible for keeping records pertaining to everything discussed
in the meeting.
 This need to quickly publish the records is reflected in more
and more scribes beginning to make use of CASE tools to
capture many facts (documented using data and process
models) that are communicated during a JAD session.
4
Joint Application Development
JAD Participants

IS Staff


A JAD session may also include a number of IS personnel who are
primarily in attendance to listen and take notes regarding issues
and requirements voiced by the users and managers.
 Normally, IS personnel do not speak up unless invited to do so.
 Any questions or concerns that they have are usually directed to
the JAD leader immediately after or prior to the JAD session.
The makeup of the IS staff usually consists of members of the
project team.
 These members may work closely with the scribe to develop
models and other documentation related to facts communicated
during the meeting.
5
Joint Application Development
How to Plan and Conduct JAD Sessions

Introduction


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.
6
Joint Application Development
41' - 0"
Food & Ref reshments
Flipchart
Blackboard
IS Prof essionals
&
Other Observers
Users
and
Managers
Computer
Projection
Device
30' - 0"
Overhead Projector
JAD
Leader
Scribe
Workstation
7
Printer
Joint Application Development
Organize a
JAD Team
Organize a
JAD Team
Organize a
JAD Team
Organize a
JAD Team
Organize a
JAD Team
8
Joint Application Development
How to Plan and Conduct JAD Sessions

Conducting a JAD Session

To successfully conduct the session, the leader should follow these
guidelines: (continued)
 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.
9
Joint Application Development
How to Plan and Conduct JAD Sessions

Conducting a JAD Session

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.
10
Joint Application Development
Benefits of JAD

An effectively conducted JAD session offers the following
benefits:



JAD actively involves users and management in the development
project (encouraging them to take own more an “ownership” in the
project).
JAD reduces the amount of time required to develop systems.
When JAD incorporates prototyping as a means for confirming
requirements and obtaining design approvals, the benefits of
prototyping are realized.
11
Joint Application Development
Summary



Introduction
Joint Application Development
Benefits of JAD
12