During requirements sessions, it’s your job as the BA to not only capture the requirements you’re being given, but to facilitate discussion about those requirements and taking the conversation to a deeper level.
Here are some things you can do to help with that process:
In order to foster expanded discussion, you should ask silly or frivolous questions. Put yourself in the position of being “clueless” about the process you’re discussing so that others will correct you and explain the options, the true nature of those options, and why they chose the direction they did.
This will help teams to re-examine their drivers for a decision and often help them look for simpler approaches. It sort of shocks their nervous systems into reconsideration. You need a thick skin and self-confidence to take this approach.
Make debatable statements
A variation on the silly question approach is to make debatable statements. Let me give you an example. In your business domain, sox compliancy is an important criteria.
So in a requirement planning session you state that you’ve seen little to no information around sox compliancy and testing — knowing that there is a reasonable level. You’re looking for the team to respond with the facts and you’re also looking for realization across the team of any sox compliancy or testing gaps that might still exist.