Joint Application Development (JAD)

There is a specific technique (or set of techniques) for more rapidly gaining a consensus from a group of individuals. The technique is called Joint Application Development, or JAD.

Judging by its name, you might think that this technique only applies to developing software, but that is not the case.

The JAD technique can be applied to a wide variety of areas where consensus is needed. This includes gathering business requirements, creating mission and vision statements, defining a project, building a quality management plan, etc.

The purpose of the JAD session is to dramatically reduce the timeframe required to complete a deliverable where consensus is required. Notice that this definition does not state that you will dramatically reduce the cost.

Depending on how the JAD is implemented, it may, in fact, cost more that the traditional methods. This can occur if you need to gather the JAD session participants from many locations and have to pay travel expenses. However, in many cases, your management and sponsor are willing to pay more for a process that takes much less time.

How dramatic might the time savings be? They can be very dramatic. As an example, the time required to produce the key components of your requirements might be reduced from six weeks to one week, or perhaps even two days. So, you are not talking about reducing turnaround time by 10%. JAD sessions can result in dramatic improvements – maybe 75%, 80%, 90% or higher.

The key concept of a JAD session is that you get all of the major decision-makers, stakeholders and knowledge providers into one place at the same time. The dramatic reduction in time comes from removing the lag required to move information from person to person.

If a stakeholder has a question about scope, they can ask it in the context of the JAD session. The people required to answer the question are in the room and can answer the question immediately – no time delay and no misrepresenting the question. A two-week process of getting a question clarified and answered can instead take place in ten minutes, since all of the right people are together at the same time.

If possible, the JAD session should result in a consensus on the requirements and the requirements being approved. This requires that you have the right people involved for the right amount of time, you have a facilitator to guide the discussion and you have a scribe to document everything.

If everything and everyone is available to you, you should hopefully be able to create a final set of requirements and have the participants sign their approval before the JAD session ends. This cuts through the entire traditional requirements gathering cycle of validation, specification and verification.

Key Learning


Libro El Director de Proyectos Práctico -

Un Método probado de 28 Pasos para completar tu Proyecto Exitosamente

EL DIRECTOR DE PROYECTOS PRACTICO -

Por fin ─ un libro sencillo con un método paso a paso para completar tu proyecto.

¡Y sin tener conocimiento previo sobre administración de proyectos!

Toda la "paja" de la metodología de dirección de proyectos fue eliminada, dejando solo lo que es absolutamente útil para completar la tarea.

El Director de Proyectos Práctico, Project Management for Small Projects. 

Un libro pensado en el líder de proyectos empírico que salió ganador de la rifa del tigre. Pues ya tiene la responsabilidad de un proyecto, pero que no sabe ni por donde empezar. Necesita una receta ABC para seguir.

Contiene 260 páginas perfectamente detalladas con ejemplos e ilustraciones, que te llevan de la mano hasta completar tu proyecto.

Pruébalo, síguelo, ten éxito. O sigue haciendo lo mismo... :(

Disponible en Amazon

Compra aquí El Director de Proyectos Práctico en su versión electrónica─

Entrega inmediata.

BONO ADICIONAL:  El libro incluye todos los templates─plantillas─que necesitas, listos para ser usadas. No necesitas comprar nada mas.


COPYRIGHT © 2007-2012 por Hector Olvera Padilla 1853071. Reproduction in whole or in part, or translation without written permission is prohibited. "PMP®", "PMBOK®", and "PMI®" are registered marks of the Project Management Institute, Inc.