What is the job of a Business Analyst (IT)?
The job of an IT business analyst consists of linking the parts of an organization that need a tool or a technology change with the team that builds or configures it. This person finds out what problem has to be solved, writes it down in a clear and testable way, and makes sure the proposed solution answers that need and not only what was asked for at first.
A typical day mixes meetings and work with documents. In the morning there may be an interview with the people who use a system, to understand how they work now, and in the afternoon a meeting with the technical team to explain a requirement or clear up questions. The rest of the time goes to writing user stories, drawing process diagrams, checking data in a spreadsheet, testing that what was built meets what was agreed, and giving notice when something changes or is delayed.
Typical tasks
- Interviewing users and heads of departments to understand how a process works now and what makes it difficult.
- Writing requirements, user stories and acceptance criteria in language that both the business side and the technical team can understand.
- Drawing process and information flow diagrams to show what the current work looks like and how it would change.
- Analyzing data and reports to support a proposal or to find the cause of a problem.
- Taking part in acceptance testing and checking that the result meets what was requested.
- Comparing solution options, with their advantages, limits and costs, so that other people can decide.
- Keeping stakeholders informed about progress, changes in scope and open questions.
Subjects and content usually covered
- Fundamentals of information systems and of how a company is organized.
- Business process analysis and modeling.
- Gathering and documenting requirements.
- Databases and SQL queries at a basic or intermediate level.
- Agile methods and project management.
- Spreadsheets, basic statistics and data visualization.
- Software testing and quality control.
Usual duration and type of training
There is no single length, because this is a job people reach by several paths. Technical training in information systems, computing or administration usually lasts 2 to 3 years, and a related university degree (information systems engineering, computer science, business administration, industrial engineering) takes 4 to 5 years. There are also courses and certification programs in business analysis, lasting 2 to 12 months, which are usually taken as a complement. The length and the type of qualification vary by country.
How you get there and what is usually required to practice
The most common routes are studying a degree or technical program related to information systems, computing or administration, or starting in another position inside a company, such as technical support, software testing, user service or an administrative area, and moving into analysis once the business and its systems are well known. Some people also come from fields such as finance, logistics or health and approach technology from their knowledge of their own sector.
There is usually no mandatory license to practice. Many employers value demonstrable experience, command of SQL and of documentation tools, and sometimes certifications in business analysis or agile methods. The first position is often as a junior analyst or assistant, and getting it is not always quick.
Skills that help
- Asking questions in an orderly way and listening closely to understand a problem before proposing a solution.
- Writing clear requirements, without ambiguity, that other people can review and test.
- Explaining technical ideas to people outside the field, and business needs to the people who program.
- Reviewing data with spreadsheets or queries and drawing conclusions that can be defended.
- Negotiating priorities when different departments ask for different things.
- Organizing their own work and keeping a record of changes and agreements.
Career paths and job opportunities
- Banks, insurance companies and other firms in the financial sector.
- Software development companies and technology consultancies.
- Hospitals, clinics and other health organizations that run information systems.
- Retail, e-commerce and logistics companies.
- Public bodies and agencies that are updating their procedures and systems.
- In-house technology departments in industry, telecommunications and education.
What you are not always told
- Much of the work is talking, writing and reaching agreement, rather than using technology directly.
- The analyst ends up in the middle of different interests: one department wants speed, another wants control and another does not want to change how it works.
- Requirements change halfway through, and the documents have to be redone, people notified and points renegotiated.
- A person can be responsible for something working well without having authority over the people who do the work.
- At the start, getting the first position may mean passing through other technical or support roles first.
How the field is changing
Data analysis tools, dashboards and artificial intelligence assistants already help to summarize meetings, draft requirements and review information, which reduces some of the repetitive work. In return, more weight is placed on understanding the problem well, checking what those tools produce and protecting the privacy of data. In addition, teams increasingly work in short cycles and remotely, and this calls for clearer documentation and communication.
Want to know if this is the right career for you?
Take the free vocational test with 5 scientific methods — CHASIDE, Holland, Big Five, MMMG and VAK — to get your personalized profile. You can also explore all university careers or learn about the scientific methodology.