Questions

Question 1

Tell me about yourself?

Answer 1

5/10

Question 2

What are the 4 agile values?

Answer 2

The four Agile values are…

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

0/10

Question 3

What are the 12 principles of agile?

Answer 3

1. Satisfy the customer through early
   and continuous delivery.
   **2. Welcome changing requirements,
   even late in development.
   **3. Deliver working software frequently
   with a preference to a shorter timescale.
2. Business people and developers must work
   together daily throughout the project.
3. Build projects around motivated individuals.
4. Convey information to and within a development team through face-to-face conversation.
5. Working software is the primary measure of progress.
6. Agile processes promote sustainable development.
7. Continuous attention to technical excellence
   and good design enhances agility.
8. Simplicity - the art of maximizing the amount
   of work not done is essential.
9. The best architectures, requirements,
   and designs emerge from self-organizing teams.
10. At regular intervals, the team reflects
    on how to become more effective.**

0/10

Question 4

How do agile scrum teams work?

Answer 4

1) 1-4 week cycles called “sprints” - to ensure teams are not planning too far ahead and they are refining their processes to ensure customer delivery. Good for projects that evolve overtime and delivery can be made in increments and where there is need for consistent customer feedback.
2) Daily standup meetings - a
3) Sprint retrospective at the end
of the cycle - a
4) Rapid feedback
5) Close collaboration with customers
and stakeholders

5/10

Question 5

What is Exploratory Testing and when should it be performed?

Answer 5

The definition of Exploratory Testing is “simultaneous test design and execution” against an application. This means that the tester uses her domain knowledge and testing experience to predict where and under what conditions the system might behave unexpectedly. As the tester starts exploring the system, new test design ideas are thought of on the fly and executed against the software under test.

In an exploratory testing session, the tester executes a chain of actions against the system, each action depends on the result of the previous action, hence the outcome of the result of the actions could influence what the tester does next, therefore the test sessions are not identical.

This is in contrast to Scripted Testing where tests are designed beforehand using the requirements or design documents, usually before the system is ready and execute those exact same steps against the system at another time.

Exploratory Testing is usually performed as the product is evolving (agile) or as a final check before the software is released. It is a complementary activity to automated regression testing.

10/10

Question 6

What is EQUIVALENCE PARTITIONING?

Answer 6

It is mainly used to reduce the number of test cases by identifying different sets of data that are not the same and only executing one test from each set of data

10/10

Question 7

How do you test the login feature of a web application?

Answer 7

Sign in with valid login, Close the browser and reopen and see whether you are still logged in or not.
Session management is important – how do we keep track of logged-in users, is it via cookies or web sessions?
Sign in, then log out and then go back to the login page to see if you are truly logged out.
Log in, then go back to the same page, do you see the login screen again?
Sign in from one browser, then open another browser to see if you need to sign in again?
Log in, change the password, and then log out, then see if you can log in again with the old password.

7/10

Question 8

What are the different phases of the software development life cycle?

Answer 8

Project initiation, requirements and specifications, design, construction, testing, installation, and post implementation review

10/10

Question 9

What is 64vb in insurance?

Answer 9

No insurer shall assume any risk in India in respect of any insurance business until the premium payable is received by him or is guaranteed to be paid by such person or unless and until deposit of such amount is made in advance.

10/10

Question 10

What is no claims bonus in vehicle Insurance?

Answer 10

No-claim bonus (NCB) is a discount in premium offered by insurance companies if a vehicle owner has not made a single claim during the term of the motor insurance policy.

5/10

Question 11

What are some of the add-on covers in vehicle insurance?

Answer 11

Consumables cover

Daily allowance cover

Engine protection cover

Key replacement cover

Loss of personal belongings

No claims bonus protection cover

Passenger cover

Roadside assistance cover

Return to invoice cover

Tyre protection cover

Zero depreciation cover

0/10

Question 12

What is the BA’s role in project time reporting, developing a communications management plan, and establishing a project status reporting process and cycle?

Question 13

During the development of a system, how do you manage frequently changing customers’ requirements?

Answer 13

It is one of the most frequently asked business analytic interview questions. The first task of a business analyst is to draft a document stating the number of changes that are allowed, and after a certain point, no amendments will be accepted. It is vital to get this document signed by the user.

In case the change required is accepted, make sure to note down all the changes and find out their overall impact on the project. Calculate the timeline, cost, and resources needed for this change.

Question 14

What is Scope creep and how can you avoid Scope creep?

Answer 14

Scope creep is a problem that can occur during the development of a project, when the scope of the project gradually expands beyond its original parameters. This can happen for a variety of reasons, such as changes in the requirements or objectives of the project, or simply due to poor planning.

Avoiding scope creep can be difficult, but it is essential in order to keep a project on track. One way to do this is to have a clear and concise definition of the project’s scope from the outset, and to make sure that all stakeholders agree on this definition. It is also important to have a well-defined change management process in place, so that any changes to the scope are carefully considered and approved by all relevant parties. Finally, regular communication with all stakeholders can help to ensure that everyone is aware of the project’s current parameters and objectives.

If you are experiencing scope creep in your own project, it is important to take action to address the problem as soon as possible. Allowing the scope to continue to expand unchecked can lead to significant delays and cost overruns, and can ultimately jeopardize the success of the project.

Question 15

What is requirement prioritization? What are the different techniques used for it?

Answer 15

Prioritizing requirements is a critical part of the requirements gathering process. It helps ensure that the most important requirements are addressed first, and that resources are used efficiently. There are a variety of techniques that can be used to prioritize requirements, including cost-benefit analysis, value-based prioritization, and stakeholder analysis.

Cost-benefit analysis is a technique that assesses the costs and benefits of each requirement. This can be used to identify which requirements are most important in terms of cost-effectiveness. Value-based prioritization is a technique that assesses the value of each requirement, based on factors such as how important the requirement is to the user, how likely it is to be used, and how complex it is to implement. Stakeholder analysis is a technique that assesses the importance of each requirement based on who will be affected by it. This can help identify which requirements are most important to the stakeholders involved.

No matter which technique is used, it is important to involve all stakeholders in the decision-making process. This will help ensure that the requirements that are prioritized are those that are most important to the project.

Question 16

What is the fundamental difference between a requirement and need in a business analysis perspective?

Answer 16

There is a fundamental difference between requirements and needs in a business analysis perspective. Requirements are specific, measurable, attainable, relevant, and time-bound statements that describe what the business wants to achieve. On the other hand, needs are broader statements that describe the general problem or opportunity that the business is trying to address. In order to create effective requirements, the business analyst must understand the needs of the business and then translate them into specific, measurable, attainable, relevant, and time-bound requirements.

Question 17

What are non-functional requirements and how do you capture them?

Answer 17

Non-functional requirements are those that specify conditions that a system must meet in order to be successful. They are often contrasted with functional requirements, which detail the specific behaviors that a system must exhibit.

There are many different types of non-functional requirements, but some common ones include performance, security, scalability, and usability. Capturing these requirements can be challenging, as they are often less well-defined than functional requirements.

One way to approach this is to think about the different types of users that will be using the system, and what their specific needs are. For example, if you are building a website, you will need to consider the needs of users with different levels of internet access speed, as well as those with different levels of computer literacy.

Another way to capture non-functional requirements is to use scenarios. Scenarios are stories that describe how a system will be used in a real-world setting. They can be useful for uncovering unanticipated requirements, as well as for helping to define the acceptable limits of system performance.

Overall, non-functional requirements are an important part of any system development project. By taking the time to think about the different types of users that will be using the system, and by using scenarios to capture real-world usage, you can ensure that your system meets the needs of all its users.

Question 18

At the end of a project l, suppose a customer is not happy with the outcome of the project. How do you handle such a situation?

Answer 18

1) Such a situation should not arise as the development work itself is started only after requirements document is signed-off by the customer.
2) Inspite of this, if this situation arises, then the impact of the change needs to be assessed. a) If it is a small change, then the same can be developed and delivered. b) if it is a big change, then the customer is to be told that this change will be taken up subsequently after go-live. c) If it is a pre-requisite for go-live, then the go-live date is to be postponed after discussing with the client. d) if the project team is being dispersed, the new team taking over will be taking this change up.

Question 19

You are hired as a BA and there is no documentation available. What do you do in those kind of situations?

Answer 19

It is surely a difficult circumstance. 1) bring all scattered documents to one place. 2) documents to be organized into sub-folders. 3) documents to be reviewed by team members and updated. 4) gather any additional documents available from the team. 5) create a document repository and share the link with the team. 6) customer can be contacted and missing documents can be sought from them.

Question 20

How do you handle a requirement that is not feasible?

Answer 20

1) it has to be communicated to to the customer to either exclude the requirement or the project itself has to be stopped. If not clearly communicated upfront, this will cause issues with customer satisfaction at a later stage.
2) if the requirement is included development team will also be not happy.

Question 21

How do you deal with situations where you have to extract information from people over whom you do not have any authority?

Answer 21

1) i once dealt with a team member who will not reply to my emails. We will have to go and meet him in person and he would only reply after two days.
2) I gave a very good feedback for him in a team meeting. After this he became very cooperative.

Question 22

Suppose you have to start working on a domain that you are not familiar with. How do you handle that situation?

Answer 22

1) refer to domain documents available in the project.
2) learn from more experienced people in the project who are familiar with that domain
3) learn from resources available online.
4) learn from actual work.

Question 23

What is the BA’s role in each cycle?