[
S
/A
N
]

JAD S ESSION F ACILITATOR
’
S G UIDE
T
C
J OINT A PPLICATION D ESIGN S ESSION O VERVIEW ................................................................ 1
Meeting Input ............................................................................................................................................. 1
Meeting Deliverables ................................................................................................................................. 1
JAD Session Roles .................................................................................................................................... 1
P LANNING THE M EETING .................................................................................................... 3
JAD Room Layout ..................................................................................................................................... 3
Meeting Check List .................................................................................................................................... 4
Sample Email Invitation ............................................................................................................................. 4
F ACILITATING THE M EETING ............................................................................................... 5
Meeting Ground Rules .............................................................................................................................. 5
S AMPLE D ESIGN C ONSIDERATIONS C HECKLIST ................................................................... 6
J OINT A PPLICATION D ESIGN (JAD) S ESSION S AMPLE A GENDA ............................................ 8
I SSUES L IST ...................................................................................................................... 9
C OMMUNICATION M ATRIX ................................................................................................. 10
T RAINING P LAN ............................................................................................................... 11
S ESSION N OTES .............................................................................................................. 12

JAD S ESSION F ACILITATOR
’
S G UIDE
J
A
D
S
O
The Joint Application Design (JAD) session is designed to facilitate the basic project planning in a group environment and fast track the identification and resolution of remaining issues. The JAD session jumpstart the next phase of the effort by providing clear goals and agreement in a one meeting setting and with all key players and stakeholders, allowing each department to focus on their issues understanding the impacts to the entire program. Together, the group can define the full impact of decisions or actions, agree to the final outcome, and approve steps required for the program and the project teams to identify needs, assign resources, and address questions impacting multiple departments.

Serves as an early form of detailed design and technical planning

Establishes clear communication and consensus

Helps the team pull different perspectives into a common understanding

Identifies what the customer and key stakeholders deem essential for success.
Meeting Input
This meeting is designed to be a group brain storming session. In order for this meeting to be as productive as possible, the following needs to be completed:

Draft high-level business process diagram

Draft high-level business process (using template)
These documents will be discussed in detail at the meeting.
Meeting Deliverables
Following are the deliverables that can come from a successful JAD session:

Purpose

Scope

Objectives

Business process

Constraints


Resource requirements
Assumptions

Open issues
JAD Session Roles
Role
Facilitator
Description
 Committed to the JAD process.
 Must be impartial. It is recommended that this person is not part of the project team.
 Experienced at facilitating meetings and leading groups.
 Must be able to summarize discussions
 Must be sensitive to group dynamics and organization politics
 Must have a good understanding of data processing concepts if this is a systems development project
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 Page 1

JAD S
Role
ESSION
Scribe
Executive Sponsor
User Representative
IT Representative
Description
 Ensures comments, issues, facts, decisions, questions are recorded (verbatim when possible).
 Experienced with MS Word, Excel, etc.
 Good analytical skills
 Good working knowledge of the business area
 Active participant – seeks clarity on wording meaning.
 Must have knowledge, authority and experience on the system or process being discussed.
 Good listener
 Contributes technical information
 Good listener
 Makes final decisions on issues
F ACILITATOR
’
S GUIDE
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 Page 2

JAD S ESSION
P
M
JAD Room Layout
It is important that the room used for the JAD session has:
 Adequate room for all participants with space to write
 Whiteboard or Flip Chart
 Projector
Figure 1 - JAD Session Layout
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 Page 3
F ACILITATOR
’
S GUIDE

JAD S ESSION
Meeting Check List
Determine who should attend the meeting.
Schedule a conference room.
Arrange for any needed presentation equipment & supplies (e.g., laptop, projector, flip chart paper, markers)
Prepare agenda
Send out email invitation with agenda
Schedule and facilitate the advance team BP draft business process flow diagram and other materials to be used/distributed to session attendees.
Distribute advance reading materials at least 48 hours prior to the meeting (business process diagram and draft business process).
Send meeting reminder 24 hours before meeting. Remind attendees to do review any advance materials previously sent.
Assign a meeting scribe to take notes and manage the on-line presentation component; scribe should have workable copies of all the templates and draft materials for review.
Review room layout and audio/visual tools prior to the session.
Sample Email Invitation
You are invited to attend a joint business process review meeting for [ business process name ] on
[ date/time ]. The purpose of the Joint Business Process Review Meeting is to facilitate the development of this business process in a group environment.
You are a key player in this business process and your input is important. Please review the attached business process documentation prior to this meeting to make the session more participative. This information will be discussed in detail at this meeting.
F ACILITATOR
’
S GUIDE
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 Page 4

JAD S ESSION
F
M
M EETING G ROUND R ULES

Set cell phones to vibrate

Do not use laptops for e-mail during sessions

Participate actively throughout the sessions

Provide direct and honest feedback

Demonstrate mutual respect to all team members and differing points of view.

Ask questions if you don’t understand. No excuse for not knowing what is going on!

Provide sufficient background information when presenting or discussing a topic (i.e. issue, problem, decision or acronyms).

We will keep this flowing and informal, but limit absences to scheduled breaks

We will be open and inquisitive – there is no bad question, and all team members have the right to fully know and understand system processes.

We will be creative and flexible when looking at how we might accomplish our objectives.

We will be open to change.
 We will apply the “10 minute” rule to any discussion that is not moving forward, and use parking lots to track issues.

We will create a cooperative/supportive environment by finding way s to say “Yes”

We allow the person speaking to have the floor, no side conversations
 IF YOU DON’T AGREE WITH ANYTHING, NOW IS THE TIME TO SPEAK!
F ACILITATOR
’
S GUIDE
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 Page 5

JAD S ESSION
S
D
C
C
This checklist captures common elements that should be present in any design. It is presented during the
Design Review process to stimulate thought, guide brainstorming, and to ensure the design being outlined contains all proper design considerations. As the project architecture, system, and application design is being reviewed, assess the design considerations that apply to your subject matter expertise and business/technical needs:
General
Does the design support both product and project goals?
Is the design feasible from a technology, cost, and schedule standpoint?
Have known design risks been identified, analyzed, and planned for or mitigated?
Are the methodologies, notations, etc. used to create and capture the design appropriate?
If possible, were proven past designs reused?
Does the design support proceeding to the next development step?
Have proper fallback consideration been made?
Design Considerations
Does the design have conceptual integrity (i.e., does the whole design tie together)?
Can the design be implemented within technology and environmental constraints?
Does the design use standard techniques and avoid exotic, hard-to-understand elements?
Is the design unjustifiably complex?
Is the design lean (i.e., are all of its parts strictly necessary)?
Does the design create reusable components if appropriate?
Will the design be easy to port to another environment if appropriate?
Does the design allow for scalability?
Are all time-critical functions identified, and timing criteria specified for them?
Are the hardware environment completely defined, including engineering change levels and constraints?
Are the pre-requisite and co-requisite software and firmware clearly identified, including release levels and constraints?
Is each event/activity verifiable by testing, demonstration, review, or analysis?
Requirements Traceability
Does the design address all issues from the requirements?
Does the design add features or functionality, which was not specified by the requirements
(i.e., are all parts of the design traceable back to requirements)?
If appropriate, has requirements coverage been documented with a completed requirements traceability matrix?
Completeness
Are all of the assumptions, constraints, design decisions, and dependencies documented?
Have all reasonable alternative designs been considered, including not automating some processes in software?
Have all goals, tradeoffs, and decisions been described?
Has the Risk Plan been modified with any new risks posed by the design?
Have all interfacing systems been identified?
Are the error recovery and backup requirements completely defined?
Have the infrastructure e.g. backup, recovery, checkpoints been addressed?
Consistency
Is the design consistent with its upstream and downstream artifacts?
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 Page 6
F ACILITATOR
’
S GUIDE

JAD S ESSION
Does the design adequately address issues that were identified and deferred at previous upstream levels?
Is the design consistent with related artifacts (i.e., other modules, designs, etc.)?
Is the design consistent with the development and operating environments?
Performance/Reliability
Are all performance attributes, assumptions, and constraints clearly defined?
If appropriate, are there justifications for design performance (i.e., prototyping critical areas or reusing an existing design proven in the same context)?
Capacity Planning
Does the design improve productivity?
Is scalability development into the plan and is maintainable?
Is Total Cost of Ownership (TCO) controlled or reduced?
Maintainability
Does the design allow for ease of maintenance?
If reusable parts of other designs are being used, has their effect on design and integration been stated?
Does the design resist erosion in the correctness of its content over time?
Compliance
Does the design follow all standards necessary for the system? (i.e., date standards)
Have legal/regulatory requirements been assessed and accounted for?
Security
Are all security considerations properly specified?
Modeling and Design Views
When appropriate, are there multiple, consistent, models and/or views that represent the design (i.e., static vs. dynamic)?
Where there are multiple models of the software (i.e., static and dynamic) are those models consistent with each other?
Comments/Notes:
F ACILITATOR
’
S GUIDE
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 Page 7

JAD S ESSION
J
A
D
(JAD) S
S
A
Agenda and Meeting Report
Meeting Purpose:
Facilitator:
Scribe:
Meeting Details: Date:
Time:
Location:
Attendees:
 = present,  = planned absence, ○ = not present,  = conference call; use bold for names of Decision Makers


Meeting Topics Reference Led By Time
Facilitator Introduction
 Introductions of everyone in attendance
 Introduction to the JAD process
Project Overview Facilitator
All Design and Planning Brainstorming:

Review and recap issues and action items:
 Assign action items as appropriate
Summarize and Close
Facilitator
F ACILITATOR
’
S GUIDE
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 Page 8

JAD S ESSION
I
L
Business Process:
Process Owner:
Category
Issue
ID Issue Name Description of Issue
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020
F ACILITATOR
’
S GUIDE
Priority Assigned
(H/M/L) To
Facilitator:
Last Updated:
Date
Needed
Action
Taken
Entered
Date
Entered
By
Date
Status Closed
P a g e 9

JAD S ESSION F ACILITATOR
’
S GUIDE
C
M
Document When How Recipient Recipient Recipient Recipient Recipient Recipient
Use this template to identify any communications that need to occur as a result of review session. Examples could be:
 A stakeholder was missed that has critical input; they should be sent the completed BP document via e-mail and asked to review and comment,

A business function was identified as being reliant on output of the BP; the function owner should be walked through the process flow diagram in a meeting so that they see changes due to updated BP to get confirmation no additional impacts exist.
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 P a g e 1 0

JAD S ESSION F ACILITATOR
’
S GUIDE
T
P
Training Goal and Purpose:
Training
Components
Budget
Target
Audience &
Size
Message Content
Distribution
Method
Timing Location Requirements Owner/s
Use this template to record any impacts to training/training materials that are identified as a result of review session. Examples could be:
 New stakeholders or involved parties are identified as a result of the process flow diagramming
 Screen shots will change for known training materials
Status 1
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 P a g e 1 1

JAD S ESSION
S
N
F ACILITATOR
’
S G UIDE
© 2012 Regents of the University of Minnesota. All rights reserved. Revised April 11, 2020 Page 12