What I learned during my IT business analyst training

March 14, 2026

From October 2025 to March 2026, I completed an IT-oriented business analyst training program. I was drawn to the role of functional analyst, but I quickly realized that there were very few training programs specifically for that role. That initially surprised me because I come from the programming field, where training materials are easy to come by.

Why are there so few training programs in functional analysis? The profession is often seen as a progression role; it depends heavily on the business, organizational, and project context, and is therefore much less standardized than other IT roles.

Of course, it is possible to train in some of the technical skills that appear in job postings. But there are still aspects of the profession that are much harder to acquire without practicing it within a real life environment.

I eventually found a training program that covered quite a few of the skills I had identified in job offers. It was far from where I live (a five-hour commute three times a week), but I was genuinely motivated to follow it.

Data modelling

I learned how to model data based on requirements gathered beforehand using Entity-Relationship diagrams, class diagrams (UML), and relational schemas. I had already had the opportunity to modify existing databases, but never to define one from scratch.

Querying SQL databases

I was also able to refresh my SQL knowledge by creating database schemas from relational schemas, and by inserting and manipulating data through SQL queries (joins, correlated queries, etc.).

Writing functional specifications with UML

We learned how to create the most commonly used UML diagrams:

use case diagrams activity diagrams sequence diagrams state-transition diagrams

I had already started learning these diagrams before the training, once I realized that this was one of the skills required for the functional analyst role.

The training gave me more practical cases, as well as experience with Visual Paradigm and Rational Software Architect.

I also took the initiative to learn Sparx Enterprise Architect when I noticed that it appeared in many job postings.

Modelling business processes with BPMN

As with the UML module, I had already started learning BPMN before the training. I was able to practise it further, particularly through the Camunda software, and benefit from the trainers’ expertise on the subject.

I noticed that I was sometimes too focused on making a BPMN diagram syntactically correct, and that I was losing sight of the main purpose of diagrams: communication.

Gathering requirements

We covered the fundamentals of business analysis. What I particularly remember are the different requirements gathering techniques. It is a skill that develops through experience, and I am looking forward to putting it into practice.

SCRUM

I was able to look in more detail at how the Scrum method works, particularly through practical workshops. I had already worked in a Scrum environment in the past, but the implementation was quite far from the official method.

Overall, the program was intensive and gave me the opportunity to strengthen both my technical foundation and my understanding of the business analyst role.