On IT projects, the analyst becomes an intermediary between the customer and the development team - he helps the two parties to better understand each other. Usually one specialist performs two roles at once - systems and business analysts. System analysis in this case means the translation of information about the client's business into the requirements for the program that he asks to develop.
Business analyst work stages
Assessment of the customer's request
As a rule, the analyst starts working at the pre-sale stage, when the client has just contacted the company. A business analyst in a team with a sales manager and a developer helps to determine what specific solution is required in a given situation and how much work remains to be done. To do this, the analyst needs to understand what kind of problem in the customer's business the technological solution must cope with. Based on this information, the analyst creates a Vision and Scope document that captures the business goals and priorities of the project, the main functions of the solution and the stakeholders. There are various templates in this document to help analysts not miss important project details.
Extracting, or, in other words, collecting requirements is the most crucial stage in the work of a business analyst. The result of the entire project largely depends on how detailed the requirements are for the analyst.
IT requirements mean the software functions required to solve specific user problems, as well as the conditions that the program must meet according to industry standards. When starting the collection of requirements, the analyst pays attention to three aspects: what benefits the business will receive from the technology solution, what is important in the program for users, and what industry or corporate business specifics should be taken into account when executing the project.