Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
The business analysis conference was very nice and important to increase the success project!!!
The most important for business analysis is collecting and gathering all requirements. What is best way to gather all requirements for business analysis?? Are the techniques same as per PMBOK like brainstorming, Delphi technique, interview,...etc.
As you are business analyst, what is your technique to gather data and requirements?? Saving Changes...
Sort By:
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
Tamer each situation will require you to rethink the tools and techniques you use since each are better suited to specific situations. The first step should always be document analysis, the fancy word for reading up before you start. This helps you understand the context and any work done previously. It allows you to determine what types of questions you will use during subsequent sessions. This is a mandatory step because nothing annoys busy stakeholder more than somebody asking questions for which the answers are already out there, but nothing stops you from confirming.
Leading on from here you will select the tools and techniques based on the number of stakeholders (some techniques are better suited to larger groups), location, availability etc. Be the 'dumb' person - https://www.linkedin.com/pulse/dumb-ba-good-anton-oosthuizen and always keep a trace-ability matrix Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
As business analyst you NEVER gather or collect requirements. You EVER gather or collect needs/wants/desires/wishes/etc when performing Elicitation that you must convert into requirements when you perform Analysis. The only person during the conference that said that clearly was Steve Blais. On the other side, Business Analyst start working before a project exists and continue working after the project ends. Project requirements are defined from Product requirements and project manager is accountable for the first ones, not the business analyst. What tools to use for working with requirements? Take a look to PMI´s guides related to business analysis. Saving Changes...
There is no one best way to gather, analyze or document requirements. You have to pick the right requirements modeling approach based on the type of requirement.
For example, a process map is a good way to surface, distill and capture step-by-step procedural requirements whereas a wireframe diagram or screen mockup might be the right answer for user interface-related requirements.
Kiron Saving Changes...
Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
