How I run a requirements workshop

A requirements workshop goes wrong when it turns into a wish list. Everyone names the features they'd like, someone takes notes, and the team leaves with fifty items, no priorities and no idea which ones actually solve the problem. Two weeks later the same people meet again to argue about what was agreed.

I'm Prachit Parikh, a business analyst, and requirements workshops are one of the parts of the job where preparation makes the biggest difference. This is the structure I use, from the invitation to the follow-up email.

Before the workshop

Send a one-page problem statement

A few days before, I send a single page covering the problem we're solving, who it affects, what happens today, and what success looks like. If people disagree about the problem itself, it's much better to find out by email than forty minutes into a meeting.

Invite the right people, and not too many

I want the people who do the work, the person who owns the outcome, and someone from the delivery team who can say what's realistic. Six to eight people is about the limit before the session turns into a presentation.

Pull the data in advance

If the workshop is about invoices, I run a quick SQL query beforehand to know the basics: how many per month, how many are exceptions, what the common error types are. Real numbers end a lot of debates quickly. I describe the checks I use in check the data before anyone trusts the report.

A 90-minute agenda that works

  • 10 minutes: confirm the problem and the goal
  • 25 minutes: walk through the current process
  • 25 minutes: exceptions and "what happens when..."
  • 20 minutes: draft requirements and acceptance criteria
  • 10 minutes: prioritize and agree next steps

Start with how the work happens today

I ask someone who does the work to walk through the current process step by step, sharing their screen if possible. Workarounds included. The spreadsheet someone keeps on the side, the email they send every Friday, the field they always overwrite: that's where the real requirements hide.

Ask "what happens when..."

Most requirements come out of exceptions, not the happy path. What happens when the approver is on leave? When the invoice is in another currency? When the data arrives late? When two people edit the same record? Each answer usually becomes a requirement, and often the most important one.

Write acceptance criteria live

When a requirement comes up, I write how we'd test it right there on the screen, in plain language. "Approvers see all pending invoices on one screen, sorted by due date." If the group can't agree on the acceptance criteria, the requirement isn't ready, and it's better to know that now. This is the habit behind writing requirements people can actually test.

End with priorities

I use three buckets: must-have for go-live, should-have, and later. Ten minutes spent here saves weeks of scope arguments. If everything is a must-have, I ask what would happen if each item slipped by one release.

After the workshop

Notes go out the same day while everyone still remembers. Every requirement gets a number, so people can reply about REQ-07 instead of "that thing about approvals." Each one goes straight into the traceability matrix, so it's linked to a test from day one, and later into the UAT plan.

Workshop checklist

  • One-page problem statement sent in advance
  • Six to eight of the right people
  • Basic data pulled with SQL beforehand
  • Current process walked through, workarounds included
  • Exceptions explored with "what happens when..."
  • Acceptance criteria written live
  • Priorities agreed before leaving
  • Numbered notes sent the same day

About the author

I'm Prachit Parikh, a business analyst working on requirements, SQL data validation, Power BI reporting and UAT. I write about practical business analysis on Substack and here on Blogger, and answer questions on Quora. Connect with me on LinkedIn, see my projects on GitHub, or find everything on my website.

What's the best question you've ever asked in a requirements workshop? Share it in the comments.

Comments

Popular posts from this blog

Prachit Parikh: what a business analyst actually does all day

A traceability matrix people will actually use