1. What is the role of BA in the Project initiation phase?

Ans: BA makes necessary documents and supports the Business team in legal document preparation.

2. Is there any document BA prepares in the project Initiation phase?

Ans: Yes. It is POC – Proof of concept.

3. What are the artifacts of Project Initiation Phase?

Ans: Skip

4. What is the role of BA before allocation on a Project?

Ans: He will be involved in the Project Initiation Phase. He will prepare POC and support the Business
Team.

5. What is the significance of the Product Training given to the BA?

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?

Ans: No. Both have to be done simultaneously.

7. Can we skip low level requirement gathering and only do high level requirement gathering?

Ans: No. Both have to be done simultaneously.

8. What will Business Analysts do parallel to high level As Is business process requirement gathering?

Ans: He will prepare HRD parallel to high level requirement gathering.

9. How will you categorize Change Requests?

Ans. It will be categorized into RACI

1. R – Responsible
2. A – Accountable
 3. C – Consultable
4. I – Informable

10. What is the process to implement a change request?

Ans:

1. Understand what is scope change

2. Determine the impact of incorporating the change
3. Seek approval or disapproval of the change request
4. Communicate and implement the approved change request.

11. What decision will BA take if the client keeps changing his requirements more frequently?

Ans:

1. Identify and describe the requirement.

2. Analyze its impact on project (time, budget)
3. Analyze its impact on the solution architecture / enterprise architecture.
4. Recommend how to handle it (reject, approve) to Product Owner, Sponsor, team or whomever
needs to decide.
5. Keep a record of changes – Documentation of the changes.

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.

13. Pre and Post customization real life examples.

Ans: Skip

14. What are the artifacts of the requirement gathering phase?

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.

16. Is there any BA Role in payment follow up?

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?

Ans. BA will inform the Project Manager about the delay.

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.

24. Does the client prepare a test case document?

Ans. Yes, clients prepare UAT or Functionality test case documents.

25. What is the role of BA in the deployment process?

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.

27. What is the role of BA in the maintenance and support phase?

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.

28. What is the role of BA in each phase of SDLC?

Ans.

1. Project Initiation Phase: BA will make Proof of Concept

2. Project Planning Phase: BA will get Product training and will get introduced to the client team by
Project manager
 3. Requirement Gathering Phase: BA will gather both types of requirement gathering i.e High Level
& Low Level and prepare various documents regarding the same.
4. Development Phase: BA will pass the requirement to development team and assist in case any
query arises
5. Testing Phase: BA will pass the testing points to testing team and assist in case any query arises
6. UAT Phase: BA will show and explain the product to clients so that they can also test it and get
hands on it.
7. Production Phase: BA will see that the project goes live and any issues will be dealt with.
8. Maintenance & Support Phase: Normal communication for the M&S and inform if any version
needs to be upgraded.

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.

31. What is the role of BA in GAP Analysis?

Ans. He will identify the Add-ons needed to add in the existing product through Requirement Gathering
Phase.

32. How will BA know which screens to be designed for POC?

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.

38. How will BA gather requirements if there is no existing Business?

Ans. BA will directly start from TO-BE Business Process and will not have As-IS requirement gathering
process.

39. What challenges BA face in requirement gathering?

Ans.

1. To take exact requirements in detail

2. To convey these requirements to respective teams
3. Any changes to past versions
4. Delays from client.

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.

41. What are the types of Requirements?

Ans. HI level or Functional Requirement Gathering and Low level or Detailed Requirement Gathering.

42. Which documentation BA prepares?

Ans. HI Level Documents:

1. Business Req. Doc. (BRD) / High Level Document (HLD)

Low Level Documents:

1. Software Requirement Specification (SRS)

2. Functional Specifications (FS)
3. Functional Requirement Specifications (FRS)
4. Use Case Specifications (UCS)
5. Low Level Document (LLD)
6. Technical Document (TD)
7. Functional Requirement Document (FRD)
8. Functional Document (FD)

43. Which documentation client prepares?

Ans. Skip

44. What is MOM? How to document MOM?

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

46. What is Version / Release / Built?

Ans. Version is the number of releases according to the addition of features.

Built is the process to built the product in development and testing phase

Release is making the product live for users.

47. What are different deployments?

Ans. Internal Deployment: Development to testing

UAT Deployment: Testing to Client

Production deployment: Ready to go live.

48. What challenges BA face in deployment?

Ans.

1. Timeline Delays.
2. Bugs or Defects or Issues
3. Hardware / Software support or their versions not working or features issues.

49. What is a stakeholder?

Ans. It is any personnel who is directly or indirectly responsible for the changes in the project.

50. How BA performs testing?

Ans. He will test according to the document of requirement gathering.

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.