The business analyst is the person who first determines where the client's business is and where it needs to be. Then, together with the customer and the team, he prescribes a route to bring the maximum benefit to the business at the minimum cost.
A business analyst is needed in all three phases of a project.
1. Pre-project analysis. The task of the analyst is to identify the current state of the business, its needs and determine the boundaries of decisions: what to do and what not to do. This is a high-level analysis.
The main difficulty at this stage is to form a unified vision for the customer and the developer: where we go, what we do and what we don't do.
2. analysis within the project. The business analyst works with detailed requirements: identifies, describes, models and agrees. Manages change requests if new business tasks have emerged in the process, the law governing the client has changed, the wishes of stakeholders have appeared or changed.
3. Post-project analysis. After the release, the analyst evaluates how well the solution meets the plans, what prevents it from bringing the declared value, what improvements can be made. Updates the knowledge base of the product, if further maintenance/development of the system is planned, or it is stipulated by the contract.
As an international business intelligence firm, Devox Software https://devoxsoftware.com/services/business-intelligence-services/ helps enterprises synchronize business processes and make decisions based on real-time metrics.
A business analyst is sometimes said to be a translator between business and IT. I believe it is the person who organizes the collaborative work. This is an equal participant of the round table, where developers, testers, project managers, the customer, its suppliers and customers, the regulator represented by the quality control department, the government, and international organizations sit. That's actually the business analyst working with them, in one way or another.
From a bird's eye view, all business analysts do the same thing. They examine how the customer's organization works and suggest ways to achieve business goals. This can be done in a variety of ways, such as by redistributing responsibilities in the team, changing business processes, and outsourcing some work.
The difference of a business analyst in IT is that his main tool for achieving the goals is the software. His project requires the development, refinement or implementation of a boxed solution.
This is what distinguishes a good business analyst.
- Broad outlook. Knowledge of subject areas and the specifics of different business activities allows them to immerse themselves into a project quicker and speak the same language with a customer.
- Well-developed communication skills. If you have a hard time communicating with people and delivering information in an understandable way, perhaps this job is not for you. There is, however, a classification according to which there are business analysts and system analysts. It is believed that the former communicate more with people, and the latter work with documents, and they can be non-human introverts. In fact, this division is rare. At any rate, in large outsourced companies, a business analyst and a systems analyst are one and the same person.
- Analytical mindset. In practice this means that the analyst is able to generate different variants of solving a problem.
- Developed empathy. The ability to look at a problem from different points of view. Understand how the customer and the end user feel. To look at a task formulation through the eyes of a team: developers, testers. This helps to take into account many potential difficulties, questions, and requests.
- The main result is a decrease in the uncertainty of the customer and the team, i.e. an understanding of where and how to move.
- In more down-to-earth terms, the result is documents: a list of functional and non-functional requirements, user stories, models - they become the basis of the backlog. The team sees what to do in what order. And the customer can confirm, "Yes, this is exactly what I want."
- Another result is the knowledge base, which is needed to understand the requirements on which the system was built. It comes in handy for maintaining the system and re-using it in other projects.