Project Management

Please login or join to subscribe to this thread

What is the most effective way to gather requirements during business analysis?

linkedin twitter facebook   Artificial Intelligence   Business Analysis   Business Intelligence  
avatar
Syed Ashir Riaz
Community Champion
AI-Powered Social Media Strategist

I believe combining stakeholder interviews with real-world observations gives the clearest picture. This approach ensures solutions truly meet business needs and reduces rework later.

Sort By:
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
Those are good starting points. Document review can help fill in gaps in knowledge. Prototypes are great for visualizing the final product, which can inform requirements. Requirements workshops give you an opportunity to present and update the "big picture". If you're dealing with external stakeholders, focus groups are helpful. If you have a large, dispersed audience, surveys and questionnaires can prove helpful.

The "most effective" requirements elicitation tools are going to vary based on several variables, like what is being produced, who the stakeholders are, and where the stakeholders are located.
avatar
Jacob Vu Co-Founder| Run By Ideas Canada, Canada
Something I'd consider when thinking about requirements gathering is understanding the problems that we're trying to solve with this project and tying data to those problems.

It helps uncover requirements that might seem obvious to stakeholders so it doesn't come up, edge cases that need to be considered or even different requirements that no one thought of because we weren't thinking about the root cause problems.
avatar
VerĂ³nica Elizabeth Pozo Ruiz RYLAI Access Control Quito, Pichincha, Ecuador
Some methods of gathering requirements at the beginning of the project are:
  • Brainstorming: Conduct a session where stakeholders share their ideas, and process them to elevate or not to requirements.
  • Workshops: Structured sessions to work on the scope of the project establishing the requirements.
  • One-on-one interviews: Good to work with important stakeholders, to gather their specific and detailed requirements.
  • Surveys: Create a survey that clarifies the requirements for the project, and distribute it to the stakeholders
  • Another important form of gathering requirements is observation, to discover unattended needs.
avatar
Maria Hrabikova
Community Champion
Ricany U Prahy, Prague, Czechia
Additionally, I would like to highlight the following resources:
  • Insightful webinars by Cheryl Lee that explore the value of business analysis (you can find it on our PMI platform)
  • The website https://knowledgeadapters.com/ offers courses like the PMI-PBA Boot Camp, which I highly recommend. It provides real-life examples, analogies, and creative explanations of business analysis techniques and tools.
avatar
Michael King
Community Champion
Senior IS Project Manager| Baycare Health Systems Clearwater, Fl, United States
Everyone has shared some great suggestions regarding project requirements gathering, and I agree with them all! One more thing that I find helpful is future state analysis, where the project team and stakeholders can see, and document, what they want the project to deliver. They can then determine what needs to be build and develop a plan and budget to get the job done.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If you think you've hit a false note, sing loud. When in doubt, sing loud."

- Robert Merrill

ADVERTISEMENT

Sponsors