HKSM

JAD Sessions are structured, timeboxed workshops where the Product Owner, stakeholders, and the Scrum Team collaborate to elicit, clarify, and agree on requirements. In SBOK Scrum, they help decompose epics, define acceptance criteria, and build shared understanding quickly.

Key Points

• Facilitated, face-to-face or virtual workshops focused on rapid, collaborative requirements discovery.
• Used during product visioning, release planning, and backlog refinement to prepare ready user stories before Sprint Planning.
• Involves Product Owner, end users, SMEs, developers, testers, and a facilitator such as the Scrum Master.
• Strong emphasis on timeboxing, visual modeling, and fast decision making.
• Produces refined user stories, acceptance criteria, and updated priorities in the product backlog.
• Reduces rework by aligning expectations early and capturing decisions and constraints.

Purpose of Analysis

JAD Sessions aim to analyze stakeholder needs collaboratively so the team can articulate clear user stories, acceptance criteria, and constraints. The focus is to convert ambiguous ideas and epics into a shared, testable understanding that supports value-driven prioritization.

This technique also uncovers dependencies and nonfunctional requirements that often surface late, reducing risk and cycle time. The outcome enables better forecasting and smoother Sprint Planning.

Method Steps

• Set scope and objectives for the session aligned to a specific epic or product goal.
• Invite the right participants with decision authority and hands-on knowledge; assign a neutral facilitator.
• Prepare: agenda, timebox, existing epics, personas, policies, and any reference artifacts or prototypes.
• Facilitate discovery: map user journeys, identify tasks, model workflows, and brainstorm alternative approaches.
• Write user stories and capture acceptance criteria with concrete examples and boundaries.
• Discuss value, risks, and dependencies; propose initial priority and high-level size where appropriate.
• Confirm agreements, record decisions, define follow-ups, and update the product backlog promptly.

Inputs Needed

• Product vision, business goals, and release objectives.
• Epics, personas, user journey maps, and existing product backlog items.
• Business rules, regulatory constraints, and data samples.
• Definition of Ready checklist and any relevant prototypes or process diagrams.

Outputs Produced

• Refined user stories that meet INVEST and are sliced for end-to-end value.
• Clear acceptance criteria, often in example form such as Given-When-Then.
• Updated product backlog with priorities, dependencies, and initial sizing where helpful.
• Decision log, open questions, risks, and assumptions captured for follow-up.
• Optional visuals such as updated story maps, wireframes, or workflow diagrams.

Interpretation Tips

• Confirm that stories are independent, testable, and vertically sliced to deliver user-facing value.
• Check acceptance criteria for clarity, negative cases, and measurable outcomes.
• Use outcomes to validate Definition of Ready before pulling stories into Sprint Planning.
• Revisit priorities based on value, risk, and dependencies revealed during the session.
• Avoid treating JAD outcomes as fixed; continue refining as new learning emerges.

Example

The Product Owner schedules a 2-hour JAD session to refine an onboarding epic. Customer support, a security SME, developers, and testers collaborate on a user journey, write eight user stories with acceptance criteria, capture a compliance constraint, and flag two dependencies.

The backlog is updated and three stories are marked ready, enabling confident selection in the next Sprint Planning.

Pitfalls

• Inviting too many or the wrong participants, leading to scope creep or stalled decisions.
• Skipping timeboxes and agendas, which turns the session into unfocused discussion.
• Over-solutioning with deep technical design instead of clarifying user value and outcomes.
• Failing to document decisions, leaving ambiguity and rework for the team.
• Ignoring nonfunctional requirements or compliance constraints that later block delivery.

PMP/SCRUM Example Question

The Product Owner has a large epic with unclear acceptance criteria and wants to ready stories for the next Sprint. What is the best next step?

1. Ask developers to start building a prototype and gather feedback later.
2. Email stakeholders a questionnaire and wait for responses.
3. Schedule a JAD session with key users, SMEs, and the Scrum Team to refine stories and acceptance criteria.
4. Defer the epic to the next release and proceed with low-priority items.

Correct Answer: C — Schedule a JAD session with key users, SMEs, and the Scrum Team to refine stories and acceptance criteria.

Explanation: A facilitated JAD session enables rapid, collaborative clarification and agreement on requirements, producing ready user stories. The other options delay learning or avoid the problem.