There are many ways to gather requirements, in our opinion it boils down to what kind of medium they are in, to define how and what and when.

Let’s first discuss the different mediums through which you could gather requirements –

  1. Whiteboarding Sessions – This is literally when you have the key stakeholders in the same room, with a whiteboard and pen. And scribble through the requirements. Having it all in black and white is how you can make sure that everyone’s input is recorded in real-time.
  2. Conference Calls – This can happen when logistics prove a hurdle in getting everyone in the same room. One easily surmounted by having them dial into a conference number.
  3. Combination of 1 & 2 – sometimes it could be that you end up having to deal with some folks on the phone and a bunch of them in the room.

The most important part of dissecting a requirement gathering session is to be able to ask three questions before penning down a stakeholder’s requirement (Remember, business users love to keep giving you those requirements.Trust us they love to give you more than what might actually be required) –

  1. What is the Business Problem?
  2. Why is the current system not performing what is required? Or causing the business problem.
  3. Does the proposed business requirement resolve the business problem?


What to keep in mind when gathering requirements –

  1. Remembering the scope of the project under discussion – Here’s a practical example – When you go to the grocery store, sometimes you end up buying a bunch of stuff that you do not need. Likewise, as a Business Analyst, you need to be able to discern what requires attention. A business can have multiple requirements but it is key to filter them and reiterate what the scope of the conversation might be; this helps you get the requirements needed by the end of the call.
  2. Maintaining meeting minutes – After every meeting, critical information should be emailed ‘Just the way you understood it’ to the team that you met with, to make sure all participants are aware of the discussion & nothing was misunderstood during the session. This also helps participants that missed out on sessions catch up with the information that is needed.
  3. Articulate Communicator – It is vitally important that you are a clear and direct communicator. If you do not communicate clearly it could cause a lot of confusion and chaos during the calls. Misunderstood directions, and miscommunicated ideas could lead to the loss of your most valuable resource – Time.
  4. Know your stuff – It is important for a Business Analyst to go to a meeting knowing what is expected of them, what they need to be aware of, what they need to speak about. Research, Research, Research.

Staffigo Technical Services, LLC is an IT Consulting & Staffing firm specializing in IT Consulting services, Staffigo Technical Services, LLC has customers in various industries in the fortune 500 lists of companies all over the US, our consultants perform top notch work. If you are interested in a career in Business Analysis or if you have any other questions, please contact us at or dial to 7737706037.