5 What are the different types of Agile methodologies?
There are several types of Agile methodologies, each with its own unique approach to software development. The most popular Agile frameworks include Scrum, Kanban, and Extreme Programming (XP).
Also Read: Benefits of Agile Methodology
6 What are various core competencies of a Business Analyst?
During the development of a system, how do you manage frequently changing customers’ requirements?
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.
1 What do you understand by Gap Analysis, and what are the types of gaps that can occur during an analysis?
Gap Analysis means the analysis of the differences between the functionalities of an existing and the targeted system. The gap means changes that are required to accomplish the proposed result.
1 What do you understand by requirement? Can you differentiate between requirements and needs?
A requirement is a targeted solution and representation to achieve specific business objectives. Stakeholders evaluate the project based on set conditions/requirements before its implementation. All the elements are correctly documented for reference purposes. Needs are the high-level representation of theÂ termsÂ and the result.
For example, you need to get a business analyst job, and the requirements to apply for this job are resume, educational background, and interview practice.
2 What is the exception and alternate flow in a use-case diagram? How are they different from basic flow?
3 What are non-functional requirements and how do you capture them?
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.