My Ans
My Ans
My Ans
Ans: BA makes necessary documents and supports the Business team in legal document preparation.
Ans: Skip
Ans: He will be involved in the Project Initiation Phase. He will prepare POC and support the Business
Team.
Ans: It is important because he is the only point of contact and he should know all the in and out of the
deliverables.
6. Can we skip high level requirement gathering and go to low level requirement gathering?
7. Can we skip low level requirement gathering and only do high level requirement gathering?
8. What will Business Analysts do parallel to high level As Is business process requirement gathering?
1. R – Responsible
2. A – Accountable
3. C – Consultable
4. I – Informable
Ans:
11. What decision will BA take if the client keeps changing his requirements more frequently?
Ans:
12. What will BA do if client’s stakeholders are canceling meetings frequently due to which you cannot
achieve your timelines for documentation?
Ans:
1. Request client not to cancel meetings and tell project project manager about that and te
2. Send out appointment reminders for no shows
3. Make it easy for client to rebook
4. Open client communication equals fewer client cancellation
5. Consider appointment deposits.
Ans: Skip
Ans: Requirement gathering is a process in which we understand and identify the business’s project
technical requirements and proceed with a well-defined plan.
1. High Level Requirement Gathering (As-Is & To-Be)
2. Low Level Requirement Gathering (As-Is & To-Be)
15. What will be role of BA if he /she doesn’t complete the documentation in the timeline given by the
project manager?
Ans: He should improvise his work and needs to inform the reasons of delay to the project manager and
complete his work within the given timeline.
Ans: No. He will not interfere in payments but he will support his finance team if required
17. Give real life examples of high medium and low severity bugs.
Ans. If the company’s name is misspelled on the homepage of the website then the priority is high but
the severity is low.
18. What is the role of BA if there is any conflict while assigning priorities of bug, defect or issue between
BA, testing team and client?
Ans. He will call for a meeting between the testing team and client and resolve the issue and set the
priority.
19. What decision BA will take if UAT deployment is in next hour and tester and developer found high
priority bug due to which deployment could not be carried out and the client is already pissed off due to
previous delays?
Ans. He needs to clearly state the actual reason and explain the severity of the bug and inform us that
there is a delay in UAT deployment.
20. What is the role of BA if Bug/Defect/Issue is taking more time to fix than the given timeline?
21. What is the role of BA when client is taking more time fir UAT testing?
Ans. He will take follow up from the client about the delay, try to understand the reason and inform his
business team or Project manager.
22. Is it possible that there is one functionality that is not working on the production environment but
working perfectly on the development, testing and UAT environment and if yes, how will developers fix
it? What is the role of BA in this scenario?
Ans: Yes. In that case, all the versions of software and Hardware need to be checked thoroughly and
exact problems need to be identified.
23. Do you share a test case document with the client after testing, describe your answer.
Ans. There are 2 types of test case documents. Software based and application based. So we can share
the application based test case document to the client.
Ans. The BA will be responsible for the checking of software and hardware and if any issue is there it is
noted by BA to provide a solution and he is available for communication.
26. What is the difference between Internal deployment, UAT deployment and Production deployment?
Ans. Internal deployment is from development to testing. UAT Deployment is the testing from client side
and production deployment is making the project live on a real time basis.
Ans. He will take the feedback from the client side and discuss it with the project manager or
development and testing team and guide accordingly to the client. Also system checking and software
upgradation.
Ans.
29. What is the role of BA at client side and role of BA in third party organizations?
Ans. At client’s side BA will provide support for UAT, Production and Maintenance & support.
For 3rd parties he will ensure that the given timeline or deadline is followed by them.
30. How will the project initiation phase be different if there is no product that exists with the IT
Company?
Ans. They won’t be giving product demos but they will tell their expertise to clients and the rest of the
flow will be the same.
Ans. He will identify the Add-ons needed to add in the existing product through Requirement Gathering
Phase.
Ans. BA will know which screen to be designed for POC through the ‘Request POC’ put to them by the
Business Team of IT Company after the PSD Signoff by Client.
33. What is the role of BA if a client makes changes in POC again and again?
Ans. BA will make clients understand the reason for the change request, understand the impact for
change request, understand the effort to implement the change, and ensure that the change request
follows the approval process.
Or BA will ask to give the requirement in detail and then only he will proceed with POC.
34. How will GAP analysis be done if there is a product present with an IT Company?
Ans. If a product is already present with IT Company, GAP analysis will be on the basis of the Add-Ons
that will be required to make the existing product to To-Be or desired product.
35. What is the RACI matrix? Is it the same throughout the project or does it change from time to time?
Ans. RACI matrix is a format of saving contacts of personnel required for the Project on client’s side. It
stands for R-Responsible A-Accountable C-Consultable I-Informed. It may be the same throughout the
project or it can also change from time to time.
36. Who provides the list of the stakeholders in the RACI matrix?
Ans. Project Manager from the client side will provide the list of stakeholders.
37. Why requirement gathering will be done on High Level Low Level?
Ans. So that the requirement can be gathered on both Broader level as well as detailed level.
Ans. BA will directly start from TO-BE Business Process and will not have As-IS requirement gathering
process.
Ans.
40. How will clients signoff or approve technical requirements if their client is not technically sound?
Ans. BA will assist the client and make him understand the technical part and only after this they will
make the final document.
Ans. HI level or Functional Requirement Gathering and Low level or Detailed Requirement Gathering.
Ans. Skip
Ans. MOM is ‘Minutes of Meeting’ and they are noted throughout the meeting. Date and time name of
attendee and what has been discussed. It has a proper draft of details and accordingly it has to be filled.
45. How will you organize time if there are multiple projects assigned to you?
Ans. BA will set up priorities, assign time and day to day list
Built is the process to built the product in development and testing phase
Ans.
1. Timeline Delays.
2. Bugs or Defects or Issues
3. Hardware / Software support or their versions not working or features issues.
Ans. It is any personnel who is directly or indirectly responsible for the changes in the project.
51. How BA resolves conflicts between client’s requirement changes & IT technical Team?
Ans. He will tell the effects and impacts of changes in already documented requirements from the client,
tell the implications of such frequent changes and request the client not to change the requirements
frequently.
52. When can you expect more requirements to change? How will you handle it?
Ans. Requirement change will be more when the company doesn’t already have a similar kind of product
in their stock and have to make and deliver a completely new product as per the client’s need. We need
to start from the scratch and each and every minute requirement and detail should be properly
understood, documented and delivered.