The document contains frequently asked questions in business analyst interviews and their answers. It discusses techniques for project estimation like work breakdown structures and bottom-up estimating. It defines high-level and low-level use cases, and explains the differences between V-model and fishbone model project management approaches. Additional topics covered include the 100-point prioritization method, the Agile Manifesto, what an RFP contains, a typical BA workday, dealing with different stakeholders, and how stakeholder analysis benefits a business analyst.
The document contains frequently asked questions in business analyst interviews and their answers. It discusses techniques for project estimation like work breakdown structures and bottom-up estimating. It defines high-level and low-level use cases, and explains the differences between V-model and fishbone model project management approaches. Additional topics covered include the 100-point prioritization method, the Agile Manifesto, what an RFP contains, a typical BA workday, dealing with different stakeholders, and how stakeholder analysis benefits a business analyst.
The document contains frequently asked questions in business analyst interviews and their answers. It discusses techniques for project estimation like work breakdown structures and bottom-up estimating. It defines high-level and low-level use cases, and explains the differences between V-model and fishbone model project management approaches. Additional topics covered include the 100-point prioritization method, the Agile Manifesto, what an RFP contains, a typical BA workday, dealing with different stakeholders, and how stakeholder analysis benefits a business analyst.
1. What techniques are used for estimating a project??
Ans: Work Breakdown Structure - is the process which will be used for to get the estimation on the project. WBS - This method uses a detailed work breakdown structure, and is best for projects you’re committed to. Each task is estimated individually and thorough estimation of the project will be done. it is said as "Bottom-up estimating". Usually the estimation of the projects will also be done on Tools by PM. 2. How does a BA know his requirement gathering phase is over? Ans: The requirement gathering phase is said to complete when you get Sign off by Client on BRD document. 3. What does u mean by high level & low-level use case? Ans: A broad view of a business process is called a high-level use case. And if we divide the big view into different small sub use cases, then it is called low level use case. 4. What is the difference between fish model and V model? Ans: V model requires less time and cost whereas fish model is comparatively very costly and time consuming and Fish model is used when there is no ambiguities in the customers’ requirements. 5. What is a 100- point method? Ans: This method is used to assign prioritize the steps in a process. Each participant has to assign points for steps. In the end, all the points are calculated and the idea/ steps with the highest are considered as Priority. 6. Do you have any idea about Agile Manifesto? Ans: Agile Manifesto is a guide for software developers about the development principles to deploy iterative solution. 7. What does RFP Stands for and what is the information available in the RFP? Ans: RFP – Request for proposal, it consists of Company introduction, Background and business overview, Specifications that is needs of company, Terms and conditions for selection criteria, Contact details, Deadlines, Mail Address of Admin. 8. What is the typical day of your BA job like? Ans: It depends on the SDLC phase (Refer -Workbook 67 & 68 pages), but as a BA we should start a day with a meeting and end up our day with a meeting. 9. How do you deal with different stakeholders? Ans: It depends on case to case - Stubborn Stakeholders – preferable technique is Mind Mapping. 10. Why stakeholder analysis? How does it benefit to a BA? Ans: Project requirements is basically given by an individual and based on his behavioral traits. Stakeholder Analysis will help BA to understand the project in the right context.