JAD

an approach to user-driven development

jad.ppt

OVERVIEW

What is JAD? What are its advantages? What are its risks? What are the major interactions and trade-offs?

What is JAD?
Requirements Definition and User Interface design methodology Intensive off-site meetings of clients, executives and developers Focus on business problems NOT technical details Key purpose is to work out system details Suitable for what kinds of projects?

Advantages of JAD

Shortens elapsed time to gather requirements Gathers requirements better because it involves the clients clients buy-in; commitment to success improved product functionality Reduces the number of downstream, costly rework Leverages group dynamics and specialized skills

JAD Risks

Unrealistic productivity expectations

use part of JAD session to set realistic expectations about time choose an incremental development approach

Premature inaccurate estimates of remaining work following JAD session

revise schedule during the 2nd JAD session

Key Interactions & Trade-offs

Works best with incremental development lifecycle model (spiral)

Evolutionary prototyping - develop system concept as you move through project Evolutionary delivery - keep redefining system but deliver to dates (deliver portions of the system up front, final product not delivered faster than evolutionary prototyping) Staged delivery - deliver system in stages (but designed up front) -- most important functions first

Can be combined with rapid-development languages & prototyping tools

JAD produces savings

Commits top management to softwareplanning process from the start Shortens requirements definition stage Eliminates features of questionable value Get requirements right the first time! Get user interface right the first time! May reduce organizational infighting

Side Effects of JAD (positives)

Higher quality GUI for end user Higher end-user satisfaction Systems with greater business value Developers appreciate business needs Reduces effects of politics Educates end users about software development process through concrete involvement in the process

Objectives of a JAD session

Verify project objectives, constraints and scope Redesign process (if necessary) Identify requirements and open issues Outcome of each JAD session is input to the subsequent session

JAD Workshops

Help to overcome the communication gap between users and designers Structured sessions
conducted by a trained JAD facilitator employ brainstorming and collaboration techniques planned in advance employ advanced tools focus on business needs

JAD Workshop types

Joint Requirements Planning (JRP)

purpose
verify developers understanding of a current system id reqs for a new one

deliverable
enterprise models detailing the functional req. confirmation of project scope, system objectives, constraints list of implementation issues raised during the workshop

JAD Workshop types

JAD Analysis
purpose
analyze requirements more fully outline design for the new system

inputs
open issues raised during JRP problem definition report preliminary requirements from JRP

deliverables
detailed system models

JAD Workshop types

JAD Design
purpose
design procedures, reports, screens use prototyping tools plan for construction and installation stages

JAD Review and Confirmation

may be scheduled throughout the development for RAD, conduct these sessions after each iteration of the prototyping stage

JAD Roles

User Sponsor
high-ranking executive; champion of the project selects and motivates users to participate makes go/no-go decisions

JAD Roles

Facilitator
business or IS specialist business knowledge, diplomacy, communication, group dynamics and org skills plans/ conducts / summarizes impartial referee ensures agenda is covered

JAD Roles

Scribe
Presentation scribe
records minutes generates summary

Technical scribe
documents requirements using advanced tools

JAD Roles

End-Users/ Managers
functional-area experts clarify business rules

IS professionals
silent observers LISTEN to users description of business process and data req. comment on technical and economic feasibility user is the king of the JAD session; ISP listens and learns users needs

Planning a JAD Workshop

Determine location and duration

off-site (?) 2 - 3 hour workshops for a small to medium project

Select and prepare participants

roles briefings

Conducting a JAD workshop

Rules of operation
everyone is equal criticize ideas not people

Open issues list

record of issues raised, but not solved

Scribing
recording all workshop activities

Workshop evaluation
participant feedback

JAD Deliverables

List of objectives System Scope Functional Requirements Benefits Priority of requirements Process/data/object models GUI Interfaces Screen/report designs; menus, Open Issues list and assignments Project action plans and dates for completion

JAD Process
Focuses on business concerns Two phases

JAD I -- Planning / Initial Design Phase that emphasizes

systems goals systems scope (I.e. context diagram -- what does your system include?) data models decision about whether to continue

JAD Process

Two phases (continued):

JAD II -- Detailed Design Phase
more detailed requirements common GUI across subprojects database modifications and integration menus, transactions, security features