Ba questions Flashcards
What tools did you use as a B.A
My day to day applications included Microsoft Office, Tableau, Salesforce, Google Docs, MS Visio, Jira, Slack, and SharePoint.
Can you tell me about your day to day activities at your previous job?
Absolutely! So typically each day will start off with a short stand up meeting with the team to get a quick overview of what everyone is working on and making sure we are on schedule to finish all tasks by the given deadline. After that, I am on to my day of work. That could involve anything from meeting with stakeholders to conduct requirement workshops, reviewing test cases to make sure they fully capture the project’s need and stakeholder expectations, working on Salesforce configuration changes including custom settings, approval processes, creating dashboards to display key metrics for our Sales team, remaining on high alert to answer any questions that may come in from stakeholders or the development team, designing mock-ups, creating UML diagrams, developing business case documents that outline the scope of work, benefits, estimated costs, and risks of a project, and prioritizing requirements based on impact and urgency.
What were your roles as a business analyst?
My roles as a BA, in short terms, were to develop, maintain, and configure applications to meet clients’ business needs. I was in charge of leading requirement discussions, documenting, analyzing, and translating functional and nonfunctional requirements into user stories and acceptance criteria. I communicated with clients to understand their business needs and identify their users in order to develop requirements. My role came with a range of daily responsibilities including everything from gathering requirements, creating BRDs, backlog grooming, writing test plans, and down to participating in testing with the QA team. I worked alongside a great team and we worked closely during the development and testing phases, which was wonderful because during these times I stayed in contact with the client and had to keep them up to date and informed on the progress.
How do you gather requirements?
Sure. First, I ask the client a series of questions to define the scope of the project and the goals they are trying to achieve to make sure that we both have a clear understanding of the destination we are trying to reach. Then I go through a series of Who, What, When, and Why questions to further dissect the goal and produce specific requirements. I also like to look at document sources: if there is an already existing system, I look at the previous requirements document, and documents on policy and procedures, and perform a gap analysis to see what we can improve. If we are creating a brand new system, I like to send them a questionnaire 48 hours in advance to get the ball rolling prior to the meeting.
What is a test plan?
A test plan is a document that organizes the test strategy. It includes the objectives, deadlines, schedule, criterias to be met, the scope, risks, and deliverables
Why do we need test plans?
We need a test plan to manage testing, schedule, resources, and deliverables.
What is a test case?
A test case is a set of logical detailed steps written to test a specific functionality of the software.
A test case has the following criteria:
Steps
Expected result
Actual result
Pass/fail
Sometimes additional comments for QA to add
How would you work with a difficult stakeholder?
When it comes to difficult stalk holders, I try to be as flexible, patient, clear, and understanding as possible. Being a BA, you encounter many different stakeholders with very different personalities so a difficult client can come in different shapes. For example, one time I had a client who was very indecisive and after approving all his requirements would
