JAD Sessions

Joint Application Design (JAD) sessions are structured, facilitator-led workshops used to elicit requirements. By convening business stakeholders and key decision makers, they speed up forming the project vision and enable consensus on project scope, objectives, and detailed specifications.

Key Points

  • Facilitated, time-boxed workshops focused on gathering and clarifying requirements.
  • Bring stakeholders and decision makers together to quickly build shared understanding and agreement.
  • Use collaborative techniques such as brainstorming, process modeling, and quick prototypes.
  • Produce tangible outputs like prioritized requirements, agreed scope, and documented decisions.

Example

A project manager organizing a new CRM implementation holds a 2-day JAD session with sales leaders, customer support, IT architects, and a UX facilitator. The group reviews current pain points, sketches key workflows, defines must-have features, and agrees on a prioritized backlog and scope for the first release.

PMP Example Question

During project initiation, the manager needs to rapidly align stakeholders on scope and high-level requirements. Which technique should be used?

  1. Monte Carlo simulation
  2. Joint Application Design sessions
  3. RACI matrix development
  4. Earned value analysis

Correct Answer: B — Joint Application Design sessions

Explanation: JAD sessions are structured, facilitator-led workshops designed to quickly gather requirements and build consensus among stakeholders.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Become an AI-First Agile Leader!

HK School of Management helps you apply AI to Agile work with practical, prompt-based workflows for real-world Scrum challenges. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More