Sei sulla pagina 1di 5

Name:Martand Dev

Roll no:501415

SOFTWARE PROJECT MANAGEMENT METHODOLOGY

JOINT APPLICATION DEVELOPMENT

1. INTRODUCTION
Joint Application Development (JAD) is a process that accelerates the design of information
technology solutions. JAD uses customer involvement and group dynamics to accurately depict
the user's view of the business need and to jointly develop a solution. Before the advent of JAD,
requirements were identified by interviewing stakeholders individually. The ineffectiveness of this
interviewing technique, which focused on individual input rather than group consensus, led to the
development of the JAD approach.

2. HISTORY
Chuck Morris of IBM conceived JAD in 1977 as a method for gathering the requirements for
geographically distributed systems. In 1980, IBM Canada adopted and refined the approach. In
1984, IBM formalized JAD by publishing the JAD Overview pamphlet. By the late 1980s, many
companies were implementing facilitated JAD workshops for analysis and design.
Because JAD has evolved over the years to include such elements as prototyping, CASE, and I
CASE, some people consider it a complete development methodology and have begun to call it
"joint application development."

3. PROJECT TYPES
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
4.JAD PARTICIPANTS
i.Executive Sponsor:The executive sponsor is the person from the customer's organization who
has the ultimate authority to make decisions about the project. The sponsor may be the
customer's project leader, the CIO, or, in some cases, the CEO.

ii.Facilitator: The success or failure of the JAD process is closely tied to how well the facilitator
handles the session. This person must be highly trained as a facilitator and must have an
excellent working knowledge of the tools and techniques to be used for capturing requirements
in the JAD sessions.

iii.User:Users have the following responsibilities in the JAD process:


Serve as the main focus of JAD (users make up 65 percent to 75 percent of the total group).
Provide business expertise.
Represent the strategic, tactical, or operational direction of the business.
Represent multiple levels of the organization.

iv.IT Representative: IT representatives lend technical advice when it is required, help develop
logical models and specifications, and build the prototype. To perform these tasks, they must be
knowledgeable about the JAD process and the tools and methods being used. IT representatives
are typically some of the key developers of the system.

v.Scribe
The scribe participates in JAD discussions to clarify points and capture them correctly. The
scribe may ask the facilitator to stop the process whenever necessary to review, obtain
clarifications, or offer rephrasing.

5.JAD LIFE CYCLE


Planning/Definition:
To complete the Planning stage, perform the following tasks:

Designate the executive sponsor.

Establish the need for the system.


Select team members for the definition component.
Define the scope of the session.

Preparation:
To complete the Preparation stage, you must perform the following tasks:
Schedule design sessions.
Conduct orientation and training for design session participants.
Prepare the materials, room, and software aids.
Customize the design session agenda.
Conduct the kickoff meeting.

Design Sessions:
To complete the Design Session component of JAD, you must perform the following tasks:
Review the project scope, objectives, and definition document.
Identify data, process, and system requirements.
Identify system interfaces.
Develop a prototype.
Document decisions, issues, assumptions, and definitions of terms.
Assign someone to resolve all issues.

The session objectives determine which techniques are used in the design session and what
deliverables are created. A good starting point, however, is to review the definition document
that was prepared during the definition phase. This document outlines the project's scope,
expected benefits, and high level requirements.

Finalization:
To complete the Finalization component, you must perform the following tasks:
Complete the design documents.
Sign off on the design documents.
Make a presentation to the executive sponsor.
Demonstrate the prototype.
Obtain the executive sponsor's approval to proceed.
Evaluate the JAD process.

The first goal of the Finalization component is to obtain closure on the deliverables by reaching a
team consensus that all necessary elements have been incorporated to fit the project's scope. The
second goal is to produce a high quality presentation that includes a prototype demonstration (if
appropriate). The third goal is to prepare a document that includes all of the deliverables that will
be referenced in the future development effort.

6.BENEFITS OF JAD:
Benefits:
The JAD approach provides the following benefits:
Accelerates design
Enhances quality
Promotes teamwork with the customer
Creates a design from the customer's perspective
Lowers development and maintenance costs

JAD achieves these benefits because of the following factors:


The decision makers are all present.
The facilitator keeps the group focused on the goals.
Differing views are handled immediately.
Most errors are caught in the Analysis and Design stages.
The system design reflects the user's desires.
Issues are resolved quickly.
Assumptions are documented and understood.
The process tends to gain momentum, not lose it.