Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I was asked to lead "JAD sessions", which I've heard of before, but never facilated before; at least in name, they appear just to be a fancy name for stakeholder workshops.

My experience has been that "group think" and "follow the leader" are common issues with this approach, but trying to stay open to the concept.

Based on what I'm able to tell the phrase has been around since the 1980s, so clearly it's no "silver bullet".

What are the key pros and cons of this approach?

share|improve this question
add comment

1 Answer

up vote 2 down vote accepted

It was popular in the pre-Agile days. It seems like it's less so today, at least judging from what you see from recruiter's listings and such.

On the pro side, it helped get input from actual users on what they wanted/needed. Unlike Agile, it doesn't require ongoing communication between developers and stakeholders which can be good in some organizations and not so good in others. Often you can get a free lunch or two from the sessions.

On the con side, users are often good at throwing in a huge laundry list of demands and making them all 'must haves'. As you noted, there can be a follow-the-leader thing going on where someone takes over the meeting. Even worse, you can have two or more wannabe leaders in attendance and a nasty political fight over the project will ensue with developers caught in the middle. In contrast to Agile, it's much easier for stakeholders to come back with a "that's not what I meant" due to the lack of ongoing communication. And, sometimes the free lunch consists of cold delivery pizza.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.